Ping and traceroute failing for eth0.3 on IPv6

Installing and Using OpenWrt
22

Not the same issue, this issue is related to multiple WANs and IPv6 in relation to mwan3.

Possibly you are hitting the same source address scenario but it's not the same, confirm you have working IPv6 connectivity and open a new topic if you'd like help with IPv6 and PPPoE.

1 Like
23

Hello. At that time I just got tired of trying and gave up, sorry for no reply.

I'm trying to get back and get this working. I just used opkg to upgrade everything possible and hope that new versions would fix this error.

Unfortunately, it didn't. I redid original tests and got same results.

I checked on my OpenWrt with the routing configuration as close to yours as possible and it still works, so the problem might not be related to routing directly.

@vgaetera I tried to stop firewall, and whole internet went down. Starting it didn't work, I had to reboot router :-x

@yousong tnx a lot for your work, I'm unable to understand what you said. I'm gonna test your code and update the post with results.

root@EdgeOpenWrt:/home/hikari# ping -c 2 -I eth0.3 2804:14c:658b:1000:45d7:3d14:cfdc:66cd
PING 2804:14c:658b:1000:45d7:3d14:cfdc:66cd (2804:14c:658b:1000:45d7:3d14:cfdc:66cd): 56 data bytes

--- 2804:14c:658b:1000:45d7:3d14:cfdc:66cd ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
root@EdgeOpenWrt:/home/hikari# ping -c 2 -I pppoe-wan 2804:14c:658b:1000:45d7:3d14:cfdc:66cd
PING 2804:14c:658b:1000:45d7:3d14:cfdc:66cd (2804:14c:658b:1000:45d7:3d14:cfdc:66cd): 56 data bytes
ping: sendto: Permission denied
root@EdgeOpenWrt:/home/hikari# ip -6 route del default from 2804:14c:658b:1000:45d7:3d14:cfdc:66cd via fe80::201:5cff:fe
66:7646 dev eth0.3 proto static metric 512 pref medium
RTNETLINK answers: No such process
root@EdgeOpenWrt:/home/hikari# ip -6 route del default from 2804:14c:658b:5fed::/64 via fe80::201:5cff:fe66:7646 dev eth
0.3 proto static metric 512 pref medium
RTNETLINK answers: No such process
root@EdgeOpenWrt:/home/hikari# ip -6 route del default from 2804:1b2:182:d768::/64 via fe80::6b0:e7ff:fec9:4557 dev pppo
e-wan proto static metric 512 pref medium
RTNETLINK answers: No such process
root@EdgeOpenWrt:/home/hikari# ip -6 route del default from 2804:1b2:206:520::/64 via fe80::6b0:e7ff:fec9:4557 dev pppoe
-wan proto static metric 512 pref medium
RTNETLINK answers: No such process
root@EdgeOpenWrt:/home/hikari# ip -6 route add default via fe80::201:5cff:fe66:7646 dev eth0.3 proto static metric 512 p
ref medium
root@EdgeOpenWrt:/home/hikari# ip -6 route add default via fe80::201:5cff:fe66:7646 dev eth0.3 proto static metric 512 p
ref medium
RTNETLINK answers: File exists
root@EdgeOpenWrt:/home/hikari# ip -6 route add default via fe80::6b0:e7ff:fec9:4557 dev pppoe-wan proto static metric 51
2 pref medium
RTNETLINK answers: File exists
root@EdgeOpenWrt:/home/hikari# ip -6 route add default via fe80::6b0:e7ff:fec9:4557 dev pppoe-wan proto static metric 51
2 pref medium
RTNETLINK answers: File exists
root@EdgeOpenWrt:/home/hikari# ping -c 2 -I pppoe-wan ipv6.google.com
PING ipv6.google.com (2800:3f0:4001:81b::200e): 56 data bytes
64 bytes from 2800:3f0:4001:81b::200e: seq=0 ttl=117 time=21.786 ms
64 bytes from 2800:3f0:4001:81b::200e: seq=1 ttl=117 time=21.961 ms

--- ipv6.google.com ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 21.786/21.873/21.961 ms
root@EdgeOpenWrt:/home/hikari# ping -c 2 -I eth0.3 ipv6.google.com
PING ipv6.google.com (2800:3f0:4001:81b::200e): 56 data bytes
64 bytes from 2800:3f0:4001:81b::200e: seq=0 ttl=112 time=41.481 ms
64 bytes from 2800:3f0:4001:81b::200e: seq=1 ttl=112 time=35.011 ms

--- ipv6.google.com ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 35.011/38.246/41.481 ms

Looks like it worked :smiley:

I'm gonna give it some time and see if mwan3 will have it working.

24

Well good and bad news.

It kept working for a few hours. Then I decided to reboot router just to be sure. And it stopped working, and again ping failed.

I executed the code again, and again it's working.

I wonder if I'd need to put it in a script under /etc/init.d or the sorts, so that it's fixed every sad time router reboots.

25 
ubus call system board

What is the output?

1 Like
26 
{
        "kernel": "4.14.131",
        "hostname": "EdgeOpenWrt",
        "system": "MediaTek MT7621 ver:1 eco:3",
        "model": "UBNT-ERX-SFP",
        "board_name": "ubnt-erx-sfp",
        "release": {
                "distribution": "OpenWrt",
                "version": "18.06.4",
                "revision": "r7808-ef686b7292",
                "target": "ramips\/mt7621",
                "description": "OpenWrt 18.06.4 r7808-ef686b7292"
        }
}
1 Like
27

It should be possible to upgrade to the latest stable release.

28

Is it worth upgrading? Isn't opkg upgrading the same?

29

Yes, there's a chance it can fix your issue.

No, it is limited to to a specific code branch and kernel version.

2 Likes
30

I'm gonna read tutorial teaching how to upgrade, specially the required free storage as I don't have any USB or card for external one.

I remember I had a lot of trouble installing OpenWRT first time due to that.

1 Like