Mwan3 interfering with WAN that wasn't added to it

Ok, it was mwan3 x.x

I added the interface to it (only config interface, not to members and policies), and now it's working.

# ping -c 4 -I eth2 v4.ipv6-test.com ; ping -c 4 -I eth2 ipv4.google.com ; ping -c 4 -I eth2 amazon.com
PING v4.ipv6-test.com (51.75.78.103) from 192.168.20.16 eth2: 56(84) bytes of data.
64 bytes from muscaria.t0x.net (51.75.78.103): icmp_seq=1 ttl=44 time=243 ms
64 bytes from muscaria.t0x.net (51.75.78.103): icmp_seq=2 ttl=44 time=242 ms
64 bytes from muscaria.t0x.net (51.75.78.103): icmp_seq=3 ttl=44 time=242 ms
64 bytes from muscaria.t0x.net (51.75.78.103): icmp_seq=4 ttl=44 time=248 ms

--- v4.ipv6-test.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 242.241/243.681/247.569/2.247 ms
PING ipv4.l.google.com (142.250.219.14) from 192.168.20.16 eth2: 56(84) bytes of data.
64 bytes from gru14s27-in-f14.1e100.net (142.250.219.14): icmp_seq=1 ttl=113 time=34.8 ms
64 bytes from gru14s27-in-f14.1e100.net (142.250.219.14): icmp_seq=2 ttl=113 time=33.5 ms
64 bytes from gru14s27-in-f14.1e100.net (142.250.219.14): icmp_seq=3 ttl=113 time=33.3 ms
64 bytes from gru14s27-in-f14.1e100.net (142.250.219.14): icmp_seq=4 ttl=113 time=34.1 ms

--- ipv4.l.google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3006ms
rtt min/avg/max/mdev = 33.287/33.927/34.848/0.605 ms
PING amazon.com (176.32.103.205) from 192.168.20.16 eth2: 56(84) bytes of data.
64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=1 ttl=222 time=156 ms
64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=2 ttl=222 time=155 ms
64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=3 ttl=222 time=155 ms
64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=4 ttl=222 time=155 ms

--- amazon.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 154.692/155.105/155.557/0.317 ms

I believed that mwan3 only deals with LAN connections, I didn't know it interferes with router-initiated connections too.

So, if a interface is configured on /et/config/network but not added to /etc/config/mwan3, Internet isn't reachable on it from the router?

1 Like

It would help troubleshooting to mention that you are using mwan3.

It does, mwan3_hook iptables chain is applied to OUTPUT as well.

mwan3 rules have priority let's say.

2 Likes

Sorry for nor mentioning it :confused:

How to completely disable mwan3 so that it doesn't affect routing, and LAN can reach internet using any WAN available?

I disabled it with mwan3 stop and now this ISP works fine, but LAN lost internet connectivity. I'd like to disable mwan3 and take a break, keep monitoring WANs without it, then configure it later.

BTW, when there are more than 1 WAN and mwan3 is disabled, what rule is used to choose which WAN to route packages?

/etc/init.d/mwan3 disable
/etc/init.d/mwan3 stop

You may need to reboot the router to restore some runtime settings.

IP rules, routing table and/or routing metric.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.