Per Jessen wrote:
Linda Walsh wrote:
I'm not trying anything 'complex'. I'm just trying to use the 'ifroute.eth[#]' files to install the routes associated with each route, as documented.
Sorry, I was having trouble understanding what you were trying to achieve. I've never had reason to use interface-specific routes. Can you give an example of which route you need, and why it can't just go in /etc/sysconfig/network/routes?
The route isn't available until the interface comes up -- so why shouldn't it be in the ifroutes? I didn't put it there initially, suseconfig did, but it has it wrong (w/o the gateway). It put 'lo' in the general routes file because, I'm guessing, it will always be there? My network cards have been getting changed a bit, so I want to make sure the routes get installed when the cards come up. I have two cards on two different machines configured to talk directly to each other via a crossover, but it's an experiment -- and I bring it up manually -- so I only want the routes installed when I bring it up. But I'd like to assign weights to the routes -- as the other interfaces involve them going through a switch -- a bit like a hop -- this way if I bring up the manual route, I should see traffic between the two start to go over the dedicated link -- I hope to 'graduate' eventually to using it and the other link in a 'bonded' with traffic first going over the dedicated link, and 2nd over the switch. I'm maxing out on network speed with max Mbits in the 900's, so I thought trying bonded links might help, as 10Gbit is way expensive for my budget (vs. an extra 1Gbit port and wire...well...)...
How can this be considered 'beyond' what OS Netconf offers? One has 'routes' associated with each interface.
In a default config, only 'lo' has such a route.
It would be 'expectable', that one of those routes would be the route you would use to get to the external network.
No, I would expect that to be the default gateway.
--- ??? In my ISP setup, I forward my packets to another host addr that is the 'gateway' that isn't on my machine. My interface is on the same subnet as it, but I forward packets to it to get out to the internet. Perhaps my ISP lies to me and I can just broadcast my traffic out my ethernet port, but I've gotten complaints from other people (on the same subnet) as routed to them. I have a static IP and am only one of ~250 host addr's on the specific sub-addr I am on. So I set my interface to to be 1.2.3.4 with its mask as 255.255.255.0 on the 1.2.3.0 net, with my default gateway being via "1.2.3.1". My machine isn't the gateway -- that's why one uses 'via'.
My external interface is on the same 'subnet' as my external-gateway. So I simply need to add a 'route' to the 'ifroute' file that says "for 'default', use 'gateway <<host>>' [on interface] 'eth0' ".
route add default gateway n.n.n.n eth0
in /etc/sysconfig/network/routes:
default n.n.n.n - -
---
Can't do that. Doesn't work =illegal route=.
n.n.n.n isn't a local address. My addr is n.n.n.l on eth0, while
another host, 'n.n.n.n' is the gateway.
But I know how to to do 'via' in routes anyway -- the
'want' is to do it in in the if-specific route file, so it only gets installed if there is no problem with that interface coming up. I'd like to arrange two different cards to talk to the gateway machine -- but that would mean
the route to the gateway would use a different device depending on which is working (cables get unplugged, or who knows what...). With the route on the interface, I can make sure that the correct route gets installed.
in routes, use something like
default 0.0.0.0 0.0.0.0 eth0 via