ClearFoundation Tracker - ClearOS
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001456ClearOSapp-syswatch - System Watchpublic2013-12-10 09:012020-03-02 08:50
Reporternikkilocke 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionsuspended 
PlatformOSOS Version
Product Version6.4.0 
Target VersionFixed in Version 
Summary0001456: Syswatch does not set default route to primary network interface if secondary interface is still up
DescriptionI 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 ReproduceHave 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.
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2013-12-10 09:01nikkilockeNew Issue
2013-12-10 09:25user2Note Added: 0001098
2013-12-10 09:25user2Statusnew => acknowledged
2020-03-02 08:50NickHNote Added: 0013141
2020-03-02 08:50NickHStatusacknowledged => closed
2020-03-02 08:50NickHResolutionopen => suspended

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   
2020-03-02 08:50   
Migrated to https://gitlab.com/clearos/clearfoundation/syswatch/issues/3 [^]