I'm finding that just a simple matter of my ppp session going down and then back up again is messing up the delicate balance (no pun intended) of route rules and tables that shorewall sets up to achieve track/balance/policy routing. If I simply do a "shorewall[-lite] restore" things return to normal.
I'm not quite sure what's happening yet but it's probably got to do with having both a DHCP Internet connection and PPPoE connection and having them stomping on each other's default routes (even though I have set removed the replacedefaultroute option from the ppp configuration), but it makes me wonder if it wouldn't be useful to separate out the code from shorewall[-lite] that restores the routing configuration so that one can call that without having to reload the whole firewall configuration. In the meanwhile I think I probably have to fiddle these connections up and down a few times and watch what each are doing with the default route(s). It sees that at some point the default route through the DHCP connection gets completely lost so that shorewall fails to reload because it can't even figure out what the default route is through that interface. Thots? b. -- My other computer is your Microsoft Windows server. Brian J. Murrell
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
