| Anonymous | Login | 2024-12-22 00:33 MST |
| Main | My View | View Issues | Change Log | Roadmap | Repositories |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0001456 | ClearOS | app-syswatch - System Watch | public | 2013-12-10 09:01 | 2020-03-02 08:50 | ||||
| Reporter | nikkilocke | ||||||||
| Assigned To | |||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||
| Status | closed | Resolution | suspended | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | 6.4.0 | ||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0001456: Syswatch does not set default route to primary network interface if secondary interface is still up | ||||||||
| Description | I have 2 WAN interfaces, ppp0 (via fibre to the cabinet, reasonably fast) and eth1 (via slow wireless link to very slow ADSL connection. I have set the relative priorities of these to 200 and 1 in MultiWAN (would prefer eth1 to be backup, but that doesn't work - see bug 1424). If ppp0 goes down for a while, syswatch switches the default route to eth1. When ppp0 comes back, the default route remains eth1. | ||||||||
| Steps To Reproduce | Have 2 network interfaces with different priorities in multiwan. Note the first one is set as the default route. Unplug it and wait until syswatch notices. Note the second one is now default route. Plug in the first one again and wait until syswatch notices - default route remains unchanged. | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
|
(0001098) user2 2013-12-10 09:25 |
Keep in mind, there's no concept of "primary/secondary" in multiWAN. Yes, a human being would consider the WAN with the 200 weighting as the primary, but the multiWAN system doesn't care. When multiWAN is active, the main routing table that you see using the "route" or "ip route" command is not active. In fact, it could be completely blank if it weren't for IPsec (shakes fist at IPsec... again). You can see the default route in MultiWAN by running the following command: # ip route show table 250 default proto static nexthop via 1.2.3.4 dev ppp0 weight 200 nexthop via 4.3.2.1 dev eth1 weight 1 You can find more technical details here: http://www.clearfoundation.com/docs/developer/apps/multi-wan/routing_and_multi-wan [^] |
|
(0013141) NickH (developer) 2020-03-02 08:50 |
Migrated to https://gitlab.com/clearos/clearfoundation/syswatch/issues/3 [^] |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2013-12-10 09:01 | nikkilocke | New Issue | |
| 2013-12-10 09:25 | user2 | Note Added: 0001098 | |
| 2013-12-10 09:25 | user2 | Status | new => acknowledged |
| 2020-03-02 08:50 | NickH | Note Added: 0013141 | |
| 2020-03-02 08:50 | NickH | Status | acknowledged => closed |
| 2020-03-02 08:50 | NickH | Resolution | open => suspended |
|
Issue History |