Hi All On 05/24/12 11:24, Artur Uszyński wrote: > Hello. > > In a situation like this: > - a firewall has two or more internet connections, > - a firewall runs shorewall 4.5.1 (multiple isps configured) > - one connection is broken, > - default route in the main routing table leads through the failed connection, > - a firewall is 20000 km away from admin ;),
And here I complain about a customer 200Km away! Only ever had one emergency trip there to phix a typo I made! I strangled the ingress shaping to 500 bits per second instead of 500K! > and after taking the following actions: > - logging in to the firewall through working connection, > - changing shorewall configuration and making a stupid error in it > - doing "shorewall stop; shorewall start" :s, > > you must take nearest flight from Europe to Australia to bring the firewall > back to life ;) (because returning traffic goes through default, non-working > link) > > Can shorewall handle such cases in a way, which would prevent similar > accidents ? Did I miss any option ? > If the above scenario was never considered - may I ask to add a possibility > to retain appropriate route rules and routing tables after shorewall is > stopped ? (extended routestopped functionality ?) Do you not have a pair of smart hands that you could use? I have successfully brought a system back to life by working step by step with the company owner as she typed what I told her! One trick I have learnt is to force a backdoor route just in case and even if that does mean customer hopping! Cheers Ang -- Angela Williams angierfw at gmail dot com Linux/Networking Hacker Blog http://angierfw.wordpress.com Smile! Yeshua Loves You! ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
