10894 questions

12980 answers

20232 comments

26389 members

0 votes
120 views 5 comments
by

Hello,

IPv6 doesn't work as expected. The mobile provider assigns an address with PD to the wwan0 interface, and a valid address in the allowed range is assigned to br-lan and the the odhcp clients. So far so good, but not farther ... The router itself can ping well-known servers in the outside world, however lan clients cannot the packets are dropped with an icmp address unreachable diagnostic.

The rules table for ipv6 contains:

root@lgrrutx:/etc/iproute2# ip -6 rule show
0:	from all lookup local
2061:	from all fwmark 0x3d00/0x3f00 blackhole
2062:	from all fwmark 0x3e00/0x3f00 unreachable
32766:	from all lookup main
4200000000:	from 2a02:8440:611a:d213::1/64 iif br-lan unreachable
4200000001:	from all iif lo failed_policy
4200000010:	from all iif wwan0 failed_policy
4200000010:	from all iif wwan0 failed_policy
4200000010:	from all iif wwan0 failed_policy
4200000096:	from all iif br-lan failed_policy
4200000141:	from all iif wglg failed_policy

The best candidate for the icmp unreachable diagnostic seems to be the 2062 rule a workaround is to delete both 2061 and 2062 via /etc/mwan3.user:

[ "$ACTION" == "ifup" ] && [ "$DEVICE" == "wwan0" ] && { ip -6 rule delete $(ip -6 rule show| grep 2061 | cut -d":" -f 2) ip -6 rule delete $(ip -6 rule show| grep 2062 | cut -d":" -f 2) }

The ipv4 rules table contains the same 2061 and 2062 values and works without issues. Looks like mwan3.sh doesn't do its job correctly or /etc/config/mwan3 is missing some critical fields.

Regards,
by

Looks like there is some formatting issues here. mwan3.user;

[ "$ACTION" == "ifup" ] && [ "$DEVICE" == "wwan0" ] && {

ip -6 rule delete $(ip -6 rule show| grep 2061 | cut -d":" -f 2)

ip -6 rule delete $(ip -6 rule show| grep 2062 | cut -d":" -f 2)

}

1 Answer

0 votes
by
Hello,

Thank you for your feedback.

Our RnD team will look into this question. Will let you know once we will have a solution.
Best answer
by

Update: In the near future new RUTX firmware would be released, version 7.2. That firmware would have a lot of changes to mwan3 function, including changes how IPv6 routing tables with lower IDs than 2061/2062 are installed.

When this firmware will be released, you will be able to download it from the following wikipage: https://wiki.teltonika-networks.com/view/RUTX11_Firmware_Downloads

It would be great if you could test this firmware, once it will be available and comment if your issue is indeed resolved. If issue would not be resolved with 7.2 firmware version, please download troubleshoot package from your router's "System -> Administration -> Troubleshoot" menu and send it to me via private message.

by
Do you have an expected date for this release ? I can try a beta version.
by
The behavior is correct in version 07.02 with the default ip -6 rules in place. Good.
by
Unfortunately a similar issue for IPv4 appears now at random sometime after a reboot.

Just after the reboot I can ping 8.8.8.8 (or any other address) from devices on the lan, but 1/2--2 hours later the same ping fails I have to delete the same 2062 rule from the ip -4 rule table to restore the connectivity.

I'll send you the TS file via PM.