On Tue, 2008-02-12 at 19:05 +0000, Andrew Suffield wrote: > > If you place 'static' routes in zebra.conf, thusly: > > ip route 10.1.0.1/32 10.1.100.2
That works as long as you know ahead of time what your default router is going to be. In the dynamic IP consumer world, that's not always the case. In fact I can and have had two devices on the same cable modem that get addresses out of entirely different netblocks. > That combined with suitably crafted routing tables should be > sufficient, if I've understood your problem correctly. The problem is that the content of those provider tables is dynamic also. As I understand it, each provider table is essentially a copy of the main table (so all known routing entries) minus any entries which are a result of other providers. So given a situation where a non-provider based interface (i.e. VPN) and/or routes show up, the provider tables need to all be updated. Maybe there is a better way to do it than shorewall currently implements. It would indeed be good if the provider tables could somehow only need the relevant entries for what it's providing. Maybe put the non-provider table before it in the routing rule list. Not really sure. b.
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
