[suse-sles-e] if-up and route add -net command

From: Alexei_Roudnev (Alexei_Roudnev_at_exigengroup.com)
Date: Thu Oct 05 2006 - 20:17:43 CEST


Message-ID: <0b6b01c6e8aa$8cef1180$6f31a8c0@sjc.exigengroup.com>
From: "Alexei_Roudnev" <Alexei_Roudnev@exigengroup.com>
Date: Thu, 5 Oct 2006 11:17:43 -0700
Subject:  [suse-sles-e] if-up and route add -net command


Of course - and it is EXACTLY what YaST2 is doing! Why to use 'vi' when
system have standard tool for this thing?
(Except if you use some automation, of course - unfortunately YaST2 have not
command line interface so we can't use it
for automation).

SuSe is not one of _old dumb linux, with 'vi' as the only administrative
command_. Doing things manually can break it, exactly as doing things by
'regedit' in windows. Use YaST2 when it is possible, and 'vi' only in 'hard
cases' or if you are doing something very complicated.

----- Original Message -----
From: "Dan Andruszkiw" <dan.andruszkiw@pcmsgroup.com>
To: "'Alexei_Roudnev'" <Alexei_Roudnev@exigengroup.com>
Sent: Thursday, October 05, 2006 6:23 AM
Subject: RE: [suse-sles-e] if-up and route add -net command

Hi

You need to add your routes to /etc/sysconfig/network/routes file for
the routes to be there after a reboot

Dan

-----Original Message-----
From: Alexei_Roudnev [mailto:Alexei_Roudnev@exigengroup.com]
Sent: 04 October 2006 22:31
To: suse-sles-e@suse.com; heze54
Subject: Re: [suse-sles-e] if-up and route add -net command

Why do not use YaST2 to configure persistant routing (as it is
designed)?
(Then you can see, where it created records,
and do the same manually if you want).

YaST2 -> Network decides -> edit (interface) -> routing

----- Original Message -----
From: "heze54" <heze54@hezesoft.org>
To: <suse-sles-e@suse.com>
Sent: Wednesday, October 04, 2006 1:52 PM
Subject: [suse-sles-e] if-up and route add -net command

Hi,

I need to add several route add- net routes when the server re-starts,
starts or the interface becomes up(ip-up).

Like my opensuse, I add a bash file to /etc/sysconfig/network/if-up.d..
and then a bash file like this..

!/bin/bash

# this scripts is called with the name of the interface in
# parameter $1

# source configuration file

route add -net 192.168.158.0 netmask 255.255.255.0 gw 192.168.154.254

With suse 10 or open suse it works fine but... with my sles9, when I
restart the system, there are not route added they must be added
manually..

Why? what¶ wrong?

best regards

heze54

Antes de imprimir piensa en tu responsabilidad y compromiso con el MEDIO
AMBIENTE

---------------------------------------------------------------------
To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
For additional commands, e-mail: suse-sles-e-help@suse.com

---------------------------------------------------------------------
To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
For additional commands, e-mail: suse-sles-e-help@suse.com

---------------------------------------------------------------------
To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
For additional commands, e-mail: suse-sles-e-help@suse.com



This archive was generated by hypermail 2.1.7 : Thu Oct 05 2006 - 20:14:34 CEST