![]() The address will be configured to the loopback interface lo by netifd on the *ifup/ifdown* hotplug script. Normally this would be lan.Īfter this all traffic originating from router itself (if no more specific route is found) will have source address of the lan interface (before NAT). The value must be one of the interfaces in /etc/config/network. You have to add into “/etc/config/mwan3” the option “local_source”. Traffic from LAN clients will always be balanced based on mwan3 configured rules even if no routable loopback address is configured.Ĭonfiguring a routable loopback (lede-17.01):Īdd the following interface to /etc/config/network.Īfter this all traffic originating from router itself (if no more specific route is found) will have source address of 192.168.1.1 (before NAT).Įxtra advantage is that configuring mwan3 rules for router only traffic is much easier.Ĭonfiguring a routable loopback (openwrt-18.06): This however only effects router initiated traffic. So if you don't configure a routable loopback address with corresponding more preferred default route, all traffic originating from the router itself will leave the primary WAN with the source address of that wan interface, regardless of configured user mwan3 rules. In practice this means the default route with the lowest metric is used to determine which source address to use. The downside of this is that when an application does not specify which source address to use (most of the time) the kernel will pick a source address based on the routing table. The advantage of this is that an applications can have control over which WAN interface to use. Packets were load-balanced regardless of source address, based on configured user rules.Īs of version 2.0 mwan3 does respect the already set source address. Up until version 2.0, mwan3 did not respect the already set source address of router originated packets. But with two or more wWAN interfaces you may wish to have control over this. On routers with just one WAN interface (and one default route), there is no issue on which source address to use for new initiated sessions. This is now working out of the box without any workarounds needed. Also as inbound traffic has no dedicated firewall tables anymore. ![]() The service is responsible for syncing the main routing table with the interface routing tables. ![]() Router initiated traffic is also load-balanced and can fail-over correctly.Ī new service mwan3rtmon was added by Chen Minqiang. ![]() If you are using a newer release branch build of OpenWrt after 18.06, this step is not necessary anymore. ![]()
0 Comments
Leave a Reply. |