[big_k105]

its more fun to do it manually

[flw]

I have to do it manunally becasue Yast2 is not saving the gateway setting.

In the example of:

Code:
kkjorsvik@dc:/etc/sysconfig/network> cat ifcfg-lo

IPADDR=127.0.0.1
NETMASK=255.0.0.0
NETWORK=127.0.0.0
BROADCAST=127.255.255.255
STARTMODE=onboot

kkjorsvik@dc:/etc/sysconfig/network> cat ifcfg-eth0

BOOTPROTO='static'
BROADCAST='192.1.1.255'
IPADDR='192.1.1.61'
NETMASK='255.255.255.0'
NETWORK='192.1.1.0'
REMOTE_IPADDR=''
STARTMODE='onboot'
UNIQUE='_Znp.Y3FLaENdpw9'
WIRELESS='no'

The gateway is not defined. The file that contains the gateway setting is what I can't find.

other ideas?

[CopperTop]

Hmmm, what about:

route add default gw 192.168.1.1

Would this cause the kernel to remeber it?

[flw]

Well I tried the above and no luck.

I think I try grep "gateway' -r / > gateway.txt" and just wait for it to finish to see what file contain any references t a gateway. :<

[Giro]

Have you RTFM my suse 7.1 came with a nice big manual

[lordnothing]

due to ol' man's post, i just remembered that i have the admin guide for 8.2... the cfg files are located at:
/etc/sysconfig/network/ifcfg-eth?
it also says to consult the manual for 'ifup' for the complete list of variable for the network config..
also, routing info is in the following places:
/etc/sysconfig/network/routes
/etc/sysconfig/network/ifroute-*

hope that helps

[big_k105]

the ifcfg-eth0 file says nothing about gateway tho and thats what he is trying to find out how to set.

[Giro]

Edit -> /etc/sysconfig/network/routes , And add -> default: 192.168.1.254 - eth1

Obviousely change the IP to your gateways ip and eth1 to your device, And it seems that you can do it with yast2 so just type yast2 IIRC

[flw]

Incase anyone is looking for the proxy settings file its in /etc/sysconfig/proxy

My problem has taken a turn (since I discovered it was saving the settings) into the network service just not starting properly for eth1 rather than not saving the settings. Sorry about that .

I'm going to check over my /var/log/msg and see if there is anything obvious.