Closed aparcar closed 7 years ago
mkresin:
Just google is not a valid full qualified domain name to ping. ping -6 does only DNS resolution via IPv6. Might work this way but what you are looking for is ping6 google.com.
Which LEDE revision do you use? On which device? What kind of network setup do you have? What routes are set for your system (route -A inet6)?
I can perfect fine ping google.com via IPv6 with LEDE 17.01.2.
ssn17x:
Add fd10::1/64 to br-lan to replicate the problem
If i use 'ping -6 -I 2001:x' it works
" Just a divagation Ipv6 is perfect as global address fe80 and fd prefix has strange bugs on general "
root@talitas:~# ifconfig br-lan br-lan Link encap:Ethernet HWaddr 18:A6:F7:C5:AB:0A inet addr:10.1.0.1 Bcast:10.1.0.255 Mask:255.255.255.0 inet6 addr: fe80::1aa6:f7ff:fec5:ab0a/64 Scope:Link inet6 addr: fd10::1/64 Scope:Global inet6 addr: 2001:470:x:x::1/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6246898 errors:0 dropped:106 overruns:0 frame:0 TX packets:14248722 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
root@talitas:~# route -A inet6 Kernel IPv6 routing table Destination Next Hop Flags Metric Ref Use Iface ::/0 :: U 1024 1 2 6in4-henet ::/0 :: U 1024 1 703220 6in4-henet 2001:470:x:x::/64 :: Un 256 0 0 6in4-henet 2001:470:x:x::/64 :: U 1024 1 1322496 br-lan 2001:470:x:x::/64 :: !n 2147483647 0 0 lo fd10::/64 :: U 1024 1 16367 br-lan fd10::/48 :: !n 2147483647 0 0 lo fe80::/64 :: U 256 1 177 br-lan fe80::/64 :: U 256 0 0 eth1 fe80::/64 :: Un 256 0 0 6in4-henet fe80::/64 :: U 256 0 0 wlan0 ::/0 :: U 256 1 3286 eth1 ...
jow-:
Please report this upstream at https://bugs.busybox.net/
ssn17x:
Ping tool use my fd10::1 as ip source to contact outside
ping -6 google, fail
ping -6 -I 2001::x google, works
traceroute -6 google, works
from another device works ip fd10::2 ip 2001::x route ::/0 gateway fd10::1