Hellows everyone ... Very soon I will need to migrate a DNS system from Debian Sarge to Debian Etch . That means migrate from Shorewall 2.2.4 to 3.2.6 . Zones, policies, rules, no problems ... My question is about a custom route command placed in init . This system has 2 network interfaces, in 2 completely different connections, one is a DSL with low bandwidth, and the other is a fiber channel . Yes, everyone probably already guessed, one is the master DNS and the other is the slave one . Default route is fiber, and the DSL is alternative, so in my /etc/shorewall/init I have this command :
run_and_save_command "/etc/shorewall/addroutes" and the content off /etc/shorewall/addroutes is : ip route add 200.235.10.0 dev eth2 src 200.235.10.xxx table uniempe ip route add default via 200.235.10.yyy table uniempe ip rule add from 200.235.10.xxx table uniempe Yes, this command just makes all packets coming from uniempe to be answered in the same route . So, finally, I can use it in 3.2.6 or not ? If not, what is the "shorewall way" to do things like that now ? Thanks in advance for any help .. Fábio Rabelo ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
