Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| docs:guide-user:network:wan:multiwan:mwan3 [2023/05/03 18:26] – [OpenWrt version] jamesmacwhite | docs:guide-user:network:wan:multiwan:mwan3 [2024/05/17 08:30] – [nft2ipset init script] jamesmacwhite | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== mwan3 (Multi WAN load balancing/ | ====== mwan3 (Multi WAN load balancing/ | ||
| - | * 22.03: Latest release: [[: | + | * 23.05: Latest release: [[: |
| + | * 22.03: Latest release: 2.11.7 | ||
| * 21.02: Latest release: 2.10.13-1 | * 21.02: Latest release: 2.10.13-1 | ||
| - | * 19.07 or older: No longer supported or maintained. | ||
| ==== About mwan3 ==== | ==== About mwan3 ==== | ||
| Line 59: | Line 59: | ||
| ==== OpenWrt version ==== | ==== OpenWrt version ==== | ||
| + | |||
| + | === 23.05 === | ||
| + | |||
| + | The mwan3 package is mostly unchanged between 22.03 and 23.05, with some additional fixes but otherwise mostly the same. | ||
| + | |||
| + | **Known issues:** | ||
| + | |||
| + | * [[https:// | ||
| === 22.03 === | === 22.03 === | ||
| - | The latest version of mwan3 is currently available in the 22.03 packages repository. While 22.03 switched to nftables for firewall management, mwan3 has not been updated to natively support nftables yet and therefore needs the '' | + | 22.03 switched to firewall4/nftables for firewall management, mwan3 has not been updated to natively support nftables yet and therefore needs the '' |
| **Known issues:** | **Known issues:** | ||
| - | There are a couple of regressions between 2.10 and 2.11 identified with sticky rules and ipset. An issue with fwmark and tunnel connections can cause traffic to be incorrectly routed e.g. L2TP, 6in4 and IPv6 traffic within the tunnel | + | There are a few regressions between 2.10 and 2.11 identified with sticky rules and ipset. |
| + | An issue with fwmark and tunnel connections can cause traffic to be incorrectly routed e.g. L2TP, 6in4 and IPv6 traffic within the tunnel | ||
| - | * [[https:// | + | * [[https:// |
| - | * [[https:// | + | * <del>[[https:// |
| - | * [[https:// | + | * <del>[[https:// |
| * [[https:// | * [[https:// | ||
| === 21.02 === | === 21.02 === | ||
| + | |||
| + | **No longer supported.** | ||
| The version of mwan3 in 21.02 is 2.10.13-1, it has a lot of improvements over the version in 19.07 for both performance and stability. | The version of mwan3 in 21.02 is 2.10.13-1, it has a lot of improvements over the version in 19.07 for both performance and stability. | ||
| Line 123: | Line 134: | ||
| opkg install luci-app-mwan3 | opkg install luci-app-mwan3 | ||
| </ | </ | ||
| + | |||
| + | '' | ||
| <WRAP center info 100%> | <WRAP center info 100%> | ||
| - | For routers using 22.03 or snapshot which uses firewall4/ | + | For routers using 22.03 or above the default firewall |
| </ | </ | ||
| Line 134: | Line 147: | ||
| opkg install ip6tables-nft | opkg install ip6tables-nft | ||
| </ | </ | ||
| - | |||
| - | '' | ||
| ==== Web interface (LuCI) === | ==== Web interface (LuCI) === | ||
| Line 173: | Line 184: | ||
| **Using IPv6 with mwan3:** | **Using IPv6 with mwan3:** | ||
| - | - If your IPv6 is using a tunnel type connection such as 6in4 or Wireguard, you are strongly advised to use OpenWrt | + | - Newer versions of mwan3 have better |
| - You will need to split your WAN network interfaces, so one interface has your IPv4 WAN and another for the IPv6 WAN. A common example convention is wan and wan6 (default with OpenWrt), along with an additional WAN interfaces such as wanb and wanb6 etc. Your IPv6 interface can be an alias interface in most cases. You then define each interface in mwan3 with the address family of either '' | - You will need to split your WAN network interfaces, so one interface has your IPv4 WAN and another for the IPv6 WAN. A common example convention is wan and wan6 (default with OpenWrt), along with an additional WAN interfaces such as wanb and wanb6 etc. Your IPv6 interface can be an alias interface in most cases. You then define each interface in mwan3 with the address family of either '' | ||
| - | - You will need to implement some form of IPv6 masquerading such as NETMAP or NPTv6 or [[docs: | + | - You will likely |
| NETMAP, NPTv6 and NAT66 all are configuration options that can work with mwan3, but it is up to you to implement the IPv6 configuration required. mwan3 does not currently implement any IPv6 masquerading by itself. | NETMAP, NPTv6 and NAT66 all are configuration options that can work with mwan3, but it is up to you to implement the IPv6 configuration required. mwan3 does not currently implement any IPv6 masquerading by itself. | ||
| Line 211: | Line 222: | ||
| === Routers using Distributed Switch Architecture (DSA) === | === Routers using Distributed Switch Architecture (DSA) === | ||
| - | From 21.02 onwards | + | From 21.02 onwards |
| - Go to **Network > Interfaces** and select the Devices tab. Click configure on the br-lan device. | - Go to **Network > Interfaces** and select the Devices tab. Click configure on the br-lan device. | ||
| Line 610: | Line 621: | ||
| === ipset support === | === ipset support === | ||
| + | |||
| + | <WRAP center important 100%> | ||
| + | ipset functionality is broken in 23.05 due to the '' | ||
| + | </ | ||
| ipset is designed to store multiple IP addresses in a single collection, while being performant and easier to maintain. Common usages of ipset include storing large amounts of IP addresses or ranges in a single set as well as conditional routing by domain. As routing ultimately works at the IP layer, being able to use ipset with domain based policies is useful for many websites or services which use multiple IP addresses or large Content Delivery Networks which means the IP address of that domain is constantly changing, individually adding these IP addresses would become unmanageable very quickly, ipset can help maintain this for you. | ipset is designed to store multiple IP addresses in a single collection, while being performant and easier to maintain. Common usages of ipset include storing large amounts of IP addresses or ranges in a single set as well as conditional routing by domain. As routing ultimately works at the IP layer, being able to use ipset with domain based policies is useful for many websites or services which use multiple IP addresses or large Content Delivery Networks which means the IP address of that domain is constantly changing, individually adding these IP addresses would become unmanageable very quickly, ipset can help maintain this for you. | ||
| Line 1337: | Line 1352: | ||
| option family ' | option family ' | ||
| option use_policy ' | option use_policy ' | ||
| + | </ | ||
| + | |||
| + | ==== nft2ipset init script ==== | ||
| + | |||
| + | Due to the default firewall (fw4) now being based on nftables (rather than iptables), the ipset functionality commonly used in conjunction with dnsmasq and mwan3 no longer works in 23.05 releases. This is due to mwan3 not being fully compatible with nftables and requiring iptables compatibility/ | ||
| + | |||
| + | You will need to use nfset with dnsmasq for ipset polices to be created, which mwan3 only supports at this time. mwan3 currently does not support nfset in rules directly, hence the need to create ipset policies. | ||
| + | |||
| + | For help with this init script, please message @Kishi on the forum thread and also thank them if you found this useful! | ||
| + | |||
| + | The script is [[https:// | ||
| + | |||
| + | Installation instructions: | ||
| + | |||
| + | < | ||
| + | wget -O / | ||
| + | chmod +x / | ||
| + | service nft2ipset enable | ||
| + | service nft2ipset start | ||
| </ | </ | ||