Mwan3 On Openwrt - Revision history

Adminguy: /* Tips/Troubleshooting */

2020-10-28T20:32:31Z

Tips/Troubleshooting

2020-10-28T08:25:40Z

2020-10-28T08:24:30Z

Firewall zones must include wan2/wanb in addition to wan

2020-10-28T08:24:17Z

Firewall zones must include wan2/wanb in addition to wan

2020-10-28T08:23:38Z

Tips/Troubleshooting

2020-10-28T08:21:00Z

Be consistent, whether wan2 or wanb. Label must match /etc/config/network

2020-10-28T08:18:52Z

Be consistent, whether wan2 or wanb. Label must match /etc/config/network

2020-10-28T08:17:11Z

2020-10-28T08:09:12Z

2020-10-28T08:08:42Z

Tips/Troubleshooting

← Older revision		Revision as of 20:32, 28 October 2020
Line 46:		Line 46:

	===Conntrack should be enabled===		===Conntrack should be enabled===
		+	See above.
		+
		+	===Masquerade may need to be enabled===
	See above.		See above.

@@ Line 39: / Line 39: @@
 See why?
-(What happens is that DNS will fail on the second wan only (port 53 ICMP unreachable is one such error tcpdump may report), but only from clients on the lan. Not from the router itself. It's not easy to track via iptables, although you can see the rejects increasing with iptables -L -v)
+(What happens is that DNS will fail on the second wan only (port 53 ICMP unreachable is one such error tcpdump may report), but only from clients on the lan. Not from the router itself. It's not easy to track via the multi-layered iptables, although you can see the rejects increasing with iptables -L -v)
 note that the latter is 19.07, and the former 17

@@ Line 39: / Line 39: @@
 See why?
-(What happens is that DNS will fail on the second wan only (port 53 unreachable is one such error), but only from clients on the lan. Not from the router itself. It's not easy to track via iptables, although you can see the rejects increasing with iptables -L -v)
+(What happens is that DNS will fail on the second wan only (port 53 ICMP unreachable is one such error tcpdump may report), but only from clients on the lan. Not from the router itself. It's not easy to track via iptables, although you can see the rejects increasing with iptables -L -v)
 note that the latter is 19.07, and the former 17

← Older revision		Revision as of 08:23, 28 October 2020
Line 38:		Line 38:

	See why?		See why?
		+
		+	(What happens is that DNS will fail on the second wan only (port 53 unreachable is one such error), but only from clients on the lan. Not from the router itself. It's not easy to track via iptables, although you can see the rejects increasing with iptables -L -v)

	note that the latter is 19.07, and the former 17		note that the latter is 19.07, and the former 17

@@ Line 67: / Line 67: @@
          option family 'ipv6'
 </pre>
 ===Balanced Policy Internet Errors===

@@ Line 47: / Line 47: @@
 ===Be consistent, whether wan2 or wanb. Label must match /etc/config/network===
 If you set the label of the new /etc/config/network wan interface to be wan2 instead of wanb
 then you should change the below rules and policies accordingly in /etc/config/mwan3. Or, just

@@ Line 1: / Line 1: @@
-<small>Here is a guide for setting up mwan3 on terminal for Openwrt (last tested 19.07).
+<small>Here are tips for setting up mwan3 via terminal / uci configs for Openwrt (last tested 19.07).
 ==Tips/Troubleshooting==
@@ Line 71: / Line 73: @@
 However, simply setting a wan2_wan or wan_wan2 policy (where one is failover only), will work out of the box.
 </small>

← Older revision		Revision as of 08:08, 28 October 2020
Line 66:		Line 66:
	option family 'ipv6'		option family 'ipv6'
	</pre>		</pre>
		+
		+	===Balanced Policy Internet Errors===
		+	I've seen issues with the default balanced policy only. Either, some manual troubleshooting / investigation is needed into the services breaking or you can try by setting the 'stickiness' on port 443, and 80. Perhaps 443 and 80 alone is not enough. With just balanced, it may not work 100%.
		+
		+	However, simply setting a wan2_wan or wan_wan2 policy (where one is failover only), will work out of the box.