On Tue, 2008-02-12 at 19:29 -0600, Jerry Vonau wrote: > > My what you miss when your sleeping... > > If your talking init scripts here, right?
Well, initscripts in terms of any of /etc/init.d, /sbin/dhclient-script /etc/ppp/ip-up[.d] and so forth, yes. > The issues I found with > dealing with iproute2, is that the packages that deal with > obtaining/creating an ip address only assume the main routing table > should be used. _Exactly!_ Even routing protocols like quagga only deal with the single main routing table -- AFAIK. > While what we really want here, I think, is one table > per ip, IP or interface? > maybe one per net route with secondary ips using src. Much like > what a table looks like with what shorewall generates without an entry > in the copy column for a provider, just the ip specific routing. Then > the other issue becomes /etc/iproute2 data, what should the table names > be? Tom's manipulation of rt_tables could be used to set the table's > name based on the interface name, and the related route rule code use to > create the routing rule. > Thus, to look up a route it would be: ip route ls table ppp0, > ip route ls table tun0, ip route ls table eth0 etc... Hrmmmm. > I'm I on track here or way off base? I'm not sure. I'd have to flesh out an example or see an example to know for sure. > To change the networking scripts would be a major under taking here, > and maintaining patches until upstream came on board would be a > headache, Agreed. > I gave up with the little bit I came up with for multi-dhcp > provider support for fedora. Maybe, I'm up for it now, if there is > others who are interested, otherwise I'm not going to bother trying to > change the world. It seems to me that what we really want is configurable route manipulation. Something like a set of rules and filters between "route add" (and quagga and whatever else will want to manipulate routing) and the final routing manipulation. The idea would be a process that receives input in the form of a userspace routing request (source, dest, interface, etc.) that goes through user configurable filters and rules before it is finally inserted (or deleted or replaced as the case may be) into one or more routing tables. Or am I way off base? 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
