Closed ShahryarShabani closed 4 months ago
This is not a bug. Your server probably just doesn't support IPv6
When I check IP addresses on my server :
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq state UP group default qlen 1000
link/ether 52:54:00:8d:4d:1f brd ff:ff:ff:ff:ff:ff
inet **** brd **** scope global ens3
valid_lft forever preferred_lft forever
inet6 ****/64 scope link
valid_lft forever preferred_lft forever
also when I use trojan+grpc+nginx it works without any errors
would you please help me to fix this issue?
is there any way to route all reqaddr with IPv6 to warp ?
Please check whether prefer_ipv6 is turned on in the client's routing settings.
When I check IP addresses on my server :
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq state UP group default qlen 1000 link/ether 52:54:00:8d:4d:1f brd ff:ff:ff:ff:ff:ff inet **** brd **** scope global ens3 valid_lft forever preferred_lft forever inet6 ****/64 scope link valid_lft forever preferred_lft forever
also when I use trojan+grpc+nginx it works without any errors
would you please help me to fix this issue?
As you can see, there is a scope link
in the line of your IPv6 address.
The address you saw here is a link-local address, which is in fe80::/10
. It is automatically generated from the hardware address of the interface using the EUI-64 rule, and is only used in the link layer.
If you don't understand IPv6 or link-local addresses, let's assume you are connecting a PC to a switch that is not connected to a router. Windows will assign the Ethernet interface an IPv4 address in 169.254.0.0/16
. This is an IPv4 link-local address, and connecting to the IPv4 Internet is impossible in this case.
Describe the bug whenever request addresses are IPv6s get rejected or can not be resolved
Client Apps Streisand Nekobox
Logs
Device and Operating System Ubuntu 20.04
Server Config