Closed brianjmurrell closed 4 years ago
brianjmurrell
commented
4 years ago I forget much of how this stuff is configured, but shouldn't:
config rule 'default_rule'
option dest_ip '0.0.0.0/0'
option proto 'all'
option sticky '0'
option use_policy 'wan0_wan1'mean there should be a:
config policy 'wan0_wan1'?
brianjmurrell
commented
4 years ago I think what I probably want[ed] was:
config rule 'default_rule'
option dest_ip '0.0.0.0/0'
option proto 'all'
option sticky '0'
option use_policy 'wan0_henet_wan1'I must say however, I find it difficult to wrap my mind around there being just a single rule for the default route for both ipv4 and ipv6. Historically, when I have done this kind of multi-wan configuration (using tools other than mwan3) I have treated ipv4 and ipv6 completely separate with a parallel set of configs, one for each.
In any case, changing as per the above still does not result in a default route via pppoe_wan1 when eth0.2 goes down.
jamesmacwhite
commented
4 years ago @brianjmurrell IPv4 and IPv6 being separate was something that was changed in the default config a few versions ago. As I agree it is quite weird having a IPv4 mask rule controlling both IPv4 and IPv6. It is now like this:
https://github.com/openwrt/packages/blob/master/net/mwan3/files/etc/config/mwan3#L141-L149
Other experts would need to look at the failover configuration in more detail, but just wanted to point out the configuration change.
brianjmurrell
commented
4 years ago So what's the theory of operation for failover routing? Let's take the simple case of "balanced", shouldn't both interfaces be in the routing main routing table.
I wonder if somebody can provide a copy of their Troubleshooting tab so that I can see what things are at least supposed to look like.
brianjmurrell
commented
4 years ago Does mwan3 expect the network interface configuration to install the default route?
I.e. should I remove the option defaultroute '0' from my interface configuration below?
config interface 'wan1'
option ifname 'eth0.3'
option proto 'pppoe'
...
option defaultroute '0'
option ipv6 '1'
option metric '20'I don't personally use option defaultroute '0' on any of my interfaces. I believe mwan3 would expect the default route to be present in the main routing table
aaronjg
commented
4 years ago Yes, mwan3 expects the default route to be present see "verify the routing table" in the doc
IPv4 and IPv6 being separate was something that was changed in the default config a few versions ago
They actually were always separate, but a few versions ago we added a default config rule for ipv6. Prior to that there was no default rule or ipv6.
brianjmurrell
commented
4 years ago How is the mwan3 member metric related to the interface metric option?
aaronjg
commented
4 years ago Member metric applies to the mwan3 policy, and interface metric applies to the default routing table. So if you have wana and wanb, you could have one policy that fails over from wana to wanb for some domains and another that fails over from wanb to wana for other domains
If you want load balancing, then the mwan3 metric should be the same.
ptpt52
commented
4 years ago I notice this issue, since the current upstream mwan3 in a bad/bug stage for now and it may take a long time to fix
I am sure that my version of mwan3 work great, resolve this issue
feckert
commented
4 years ago @brianjmurrell For me the failover from wan -> xdsl -> wwan works. I have noticed the following things that you have already changed? You have fixed the policy wan0_wan1. And the default route of pppoe in the main table you have also recognized.
Maintainer: @feckert Environment: x86, generic, 19.07.3
Description: I have a primary/backup configuration but when the primary connection (
eth0.2) loses pings, routing is not adjusted to use the backup connection (pppoe-wan1).The troubleshooting tab shows:
My configuration is:
If the cause is not obvious, I will start debugging, but I was hoping it would be obvious and could save me some time.