ClearFoundation Tracker - ClearOS
View Issue Details
0000679ClearOSapp-firewall - Firewallpublic2012-07-11 11:002012-08-02 19:03
dsokoloski 
dsokoloski 
highmajoralways
closedfixed 
6.2.x 
6.3.06.3.0 
0000679: MultiWAN Default Routing Required
It appears in ClearOS 6.x that default routing rules should be created regardless if syswatch has marked the external interface as off-line. Failure to do so results in an eventual total loss of connectivity if each external interface inevitably fails it's ping tests.
For a dual-WAN set-up:

- Edit /etc/syswatch, add two custom ping servers that you can control and restart syswatch.
- On the ping servers, add a blocking firewall rule that blocks pings from one of the external interfaces addresses, causing syswatch to mark that interface off-line. The firewall will be restarted by syswatch and all MultiWAN routing will be removed.
- Remove the blocking firewall rule so the host can now ping the servers.
- It would be expected that syswatch can now contact both ping servers and the MultiWAN environment would be restored. However this will never happen. ICMP pings/replies will be seen on the off-line interface, but for some reason (which is not due to any local firewall rules), the kernel discards them and user-land never sees them.
- If you block the second IP address on the ping servers, the same events occur and now the system is totally off-line and will never recover.
Experimental fix in SVN r4442.
No tags attached.
Issue History
2012-07-11 11:00dsokoloskiNew Issue
2012-07-11 11:00dsokoloskiStatusnew => assigned
2012-07-11 11:00dsokoloskiAssigned To => dsokoloski
2012-07-11 11:02dsokoloskiStatusassigned => confirmed
2012-07-11 11:02dsokoloskiAdditional Information Updatedbug_revision_view_page.php?rev_id=10#r10
2012-07-19 13:41user2Statusconfirmed => resolved
2012-07-19 13:41user2Fixed in Version => 6.3.0 Updates
2012-07-19 13:41user2Resolutionopen => fixed
2012-08-01 04:55user2Target Version6.3.0 Updates => 6.3.0
2012-08-01 04:56user2Fixed in Version6.3.0 Updates => 6.3.0
2012-08-02 19:03user2Statusresolved => closed

There are no notes attached to this issue.