[opensuse] Activating routes
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. 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 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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> --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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> --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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. 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 --------------------------------------- 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@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Wed, 15 Nov 2006, by suse_mailing_list@jimmo.com:
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 -- Theo v. Werkhoven Registered Linux user# 99872 http://counter.li.org ICBM 52 13 26N , 4 29 47E. + ICQ: 277217131 SUSE 9.2 + Jabber: muadib@jabber.xs4all.nl Kernel 2.6.8 + See headers for PGP/GPG info. Claimer: any email I receive will become my property. Disclaimers do not apply. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday November 15 2006 3:45 pm, Theo v. Werkhoven wrote:
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
Theo, Only send to the opensuse@opensuse.org list. suse-linux-e is deprecated now and will be killed off soon. Don't know if you know what I know but I thought I'd let you know that your messages are in stereo... Stan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2006-11-15 17:08, Stan Glasoe wrote:
Theo,
Only send to the opensuse@opensuse.org list. suse-linux-e is deprecated now He may have done that because the OP sent to the old list.
I do wish Henne would just nuke that thing, then maybe a few people will fix their mail agents when they start seeing their emails getting bounced. -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Wed, 15 Nov 2006, by srglasoe@comcast.net:
On Wednesday November 15 2006 3:45 pm, Theo v. Werkhoven wrote:
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
Theo,
Only send to the opensuse@opensuse.org list. suse-linux-e is deprecated now and will be killed off soon. Don't know if you know what I know but I thought I'd let you know that your messages are in stereo...
From my previous post I'm sure you can see I do know thie suse-e
The OP's message had in the headers: # To: suse-linux-e@suse.com [..] # Mailing-List: contact opensuse+help@opensuse.org; run by mlmmj # X-Mailinglist: opensuse I replied to opensuse, (but) Mutt put both in the To: field. I can't help it if other people use the wrong address, and I don't always see these mistaks myself. list has been deprecated. Tnx for letting me know anyway. Theo -- Theo v. Werkhoven Registered Linux user# 99872 http://counter.li.org ICBM 52 13 26N , 4 29 47E. + ICQ: 277217131 SUSE 9.2 + Jabber: muadib@jabber.xs4all.nl Kernel 2.6.8 + See headers for PGP/GPG info. Claimer: any email I receive will become my property. Disclaimers do not apply. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Theo v. Werkhoven
The OP's message had in the headers: # To: suse-linux-e@suse.com [..] # Mailing-List: contact opensuse+help@opensuse.org; run by mlmmj # X-Mailinglist: opensuse
I replied to opensuse, (but) Mutt put both in the To: field.
I can't help it if other people use the wrong address, and I don't always see these mistaks myself.
You were subscribed to both lists (in .muttrc) so mutt recognized both as email-list addresses and did as it was directed/configured. remove suse-linux-e from your subscription listing in your .muttrc and you will not have this problem. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 15 November 2006 22:45, Theo v. Werkhoven wrote:
Wed, 15 Nov 2006, by suse_mailing_list@jimmo.com:
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@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Darryl Gregorash -
J Sloan -
James Mohr -
Patrick Shanahan -
Stan Glasoe -
Theo v. Werkhoven