Kyle McDonald writes: > James Carlson wrote: > > No. The kernel knows nothing of hop counts or weights. Those are > > routing protocol issues -- if you have a preference, then use a > > routing daemon to implement it. The kernel is just a forwarding base, > > not a policy engine. > > > > > Oh. I'm not even forwarding anything. I think forwarding is turned off.
Routing != forwarding. They're two independent concepts. "Routing" is the process of determining (by some means) "routes" or "forwarding table entries," which are objects that, given an IP address, will tell you where to send that packet. "Forwarding" is taking a packet in one interface, looking it up in a forward table, and then sending that packet one hop closer to its destination. Nodes may be configured to route, forward, do both, or do neither. > I just wanted to 'prefer' to send things not for the local net to the > router for the production network, not the mgmt network. In that case, it sounds like you do *NOT* want a default route pointing to the management network. You want a default route for the production network, and then more specific routes (that capture the "local" packets and direct them appropriately) for the management parts. > I used route -p to add the routes with different hop counts. couldn't > tell which way the replies to the pings were going though. Hop counts are ignored there. Feel free to set 'em up any way you like. ;-} > I wish the network admin would enable rdisc, or rip, or something. I > don't like hardcoding the routers on the machine. I can imagine. For what it's worth, I think it's possible to configure routing daemons (such as Quagga) to apply policy to static routes, so that you get the hop-count-preference resolution you're looking for. Obviously, it's really suboptimal because static routes are ... well ... static. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
