ER8411 - Dual WAN with faillover, primary WAN isn't prioritized after reconnection
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.ER8411 - Dual WAN with faillover, primary WAN isn't prioritized after reconnection
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Hello again!
I have configured my ER8411 with Link Backup. I have two WANs with the following characteristics:
- WAN1: 10 Gbps, PPPoE, IPv4+IPv6 (both dynamic)
- WAN3: 1 Gbps, IPoE, IPv4 (dynamic)
Load Balancing > Link Backup settings:
- Primary WAN: WAN1
- Secondary WAN: WAN3
- Mode: Failover (any, tried both)
- Status: Enable
Routing > Static Route settings:
- Static route to X.X.X.X.0/24, next hop 0.0.0.0, to WAN3 (for SIP, works fine).
When my primary WAN1 fails, secondary WAN3 gets prioritized; but then after WAN1 reconnects, the routing table doesn't prioritize WAN1 again:
| ID | Destination IP | Subnet Mask | Next Hop | Interface | Metric |
| 1 | X.X.X.0 | 255.255.255.0 | 0.0.0.0 | SFP WAN/LAN3 | 0 |
| 2 | 0.0.0.0 | 0.0.0.0 | 188.X.X.X | SFP WAN/LAN3 | 0 |
| 3 | 0.0.0.0 | 0.0.0.0 | 10.0.0.1 | SFP+ WAN1 | 0 |
| 4 | 10.0.0.1 | 255.255.255.255 | 0.0.0.0 | SFP+ WAN1 | 0 |
| 5 | 87.X.X.X | 255.255.255.255 | 188.X.X.X | SFP WAN/LAN3 | 0 |
| 6 | 87.X.X.X | 255.255.255.255 | 188.X.X.X | SFP WAN/LAN3 | 0 |
| 7 | 100.X.X.X | 255.255.255.255 | 10.0.0.1 | SFP+ WAN1 | 0 |
| 8 | 100.X.X.X | 255.255.255.255 | 10.0.0.1 | SFP+ WAN1 | 0 |
| 9 | 188.X.X.0 | 255.255.252.0 | 0.0.0.0 | SFP WAN/LAN3 | 0 |
| 10 | 192.168.0.0 | 255.255.252.0 | 0.0.0.0 | LAN | 0 |
When primary WAN1 is active, rows 2 and 3 are swapped, with WAN1 first. I wouldn't have specified what's the primary WAN if I didn't care.
As always, I'll answer any question about the issue.
Best regards!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Problems appear with the last update ou Er8411. Before all was good. Same issue.
Fix only with downgrade of Er8411 and Oc300 to be stable.
- Copy Link
- Report Inappropriate Content
Hi @Gilles72
Thanks for posting in our business forum.
Gilles72 wrote
Problems appear with the last update ou Er8411. Before all was good. Same issue.
Fix only with downgrade of Er8411 and Oc300 to be stable.
OP said this is in standalone. How did you test your device? What steps did you perform? I'd hear a more accurate description with a methodology to replicate the issue.
Or this could be a false alarm and not worth much attention because we cannot replicate it and don't have details.
In the previous replies, I used ER8411 V1.3.0 firmware and performed in the standalone, OP has already found out the difference between my test result and his setup.
- Copy Link
- Report Inappropriate Content
Clive_A wrote
Hi @EmuAGR
When failover is enabled, backup WAN is offline until the Online Detection fails to ping through primary and tells the router to switch over. It's been like this ever since the Omada router was released years ago.
@Clive_A I've been testing this for a week and it seems the failover works as expected now, enabling load balancing indeed fixed the issue. I could also check that no traffic was sent to the backup WAN, except the VoIP calls, due to the static routes I added.
So I think this works as expected then, and marked your post as the solution. Thank you!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 1752
Replies: 13
Voters 1
