Mailinglist Archive: opensuse (4498 mails)

[James Mohr <suse_mailing_list@xxxxxxxxx>]

On Wednesday 15 November 2006 22:45, Theo v. Werkhoven wrote:
> Wed, 15 Nov 2006, by suse_mailing_list@xxxxxxxxx:
> > On Tuesday 14 November 2006 17:36, J Sloan wrote:
> > > James Mohr wrote:
> > > > Hi All!
> > > >
> > > > This is a pretty basic question and I am almost embarrassed to ask. I
> > > > have SUSE 10.0 Pro and configured a route in
> > > > /etc/sysconfig/network/routes.  I have been digging through the
> > > > scripts under /etc/sysconfig/network/scripts, looking for a means to
> > > > activate this route without having to run "/etc/init.d/network
> > > > restart". Doing that does not seem to be a problem, but it seems to
> > > > be overkill. Any info is appreaciated.
> > >
> > > ip route change default via <new gateway IP>
> >
> > Thanks for the info. Not quite exactly what I was looking for. As far as
> > I can see, that changes the routes, but does not use the values
> > from  /etc/sysconfig/network/routes. That naturally solves the problem of
> > adding a route without restarting the network (just as using the route
> > command would). However, it doesn't check the validity/correctness of the
> > routes file. I guess I should have been a little more specific in what I
> > was looking for.
>
> routes(5)
> DESCRIPTION
>    The files /etc/sysconfig/network/routes   and /etc/sysconfig/net-
>    work/ifroute-config  are  parsed  by  the  script /etc/sysconfig/net-
>    work/scripts/ifup-route which sets up routing for an interface/configu-
>    ration.
>
> Theo

I tried ifup-route but I was getting an error that the interface was not up 
because that's the interface which connects me to my router and "has to be 
up". So, my assumption was that there was something wrong in my syntax, but I 
could not figure out what was wrong. 

Turns out that the system was right. The interface was not up. I have an 
interface built-in on the motherboard. Sometimes it is recognized as eth0 and 
sometimes as eth1, with my other NIC recognized as the other one. Up to now, 
I had only seen it when the built-in NIC was eth1, so I never thought much of 
it. Now, eth0 is the built-in and isn't up. Thus, I get the error. Using 
"ifup-route eth1" works as I had wanted. Imagine that!

Thanks for the help.

Regards,

Jim Mohr

-- 
---------------------------------------
"Be more concerned with your character than with your reputation. Your
character is what you really are while your reputation is merely what others
think you are." -- John Wooden
---------------------------------------
Be sure to visit the Linux Tutorial:  http://www.linux-tutorial.info
---------------------------------------
NOTE: All messages sent to me in response to my posts to newsgroups or forums 
are subject to reposting.
-- 
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx