FC9 and default GW

Hi,

just finnished installing Fedora Core 9. The machine is connected to a LAN
with IP 192.168.2.30 and GW 192.168.2.1. But after boot the machine has no
default GW.

a 'route -n' say:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0


I have to do a 'route add default gw 192.168.2.1' after boot.

I have some other machines with FC4 and I have never had any problems with
default gateway.

How can I tell this machine which default gw to use at boot without having
to add a script with the route add command?

/etc/sysconfig/network:
NETWORKING=yes
HOSTNAME=obi-wan.mydomain.net
GATEWAY=192.168.2.1
IPV6_DEFAULTGW=

and /etc/sysconfig/network-scripts/ifcfg-eth0:
DEVICE=eth0
BOOTPROTO=static
BROADCAST=192.168.2.255
HWADDR=00:1f:c6:be:4b:c3
IPADDR=192.168.2.30
IPV6INIT=yes
IPV6_AUTOCONF=yes
NETMASK=255.255.255.0
NETWORK=192.168.2.0
ONBOOT=yes
DNS1=192.168.2.22
SEARCH="mydomain.net"
NM_CONTROLLED=

--
Jørn Dahl-Stamnes
http://www.dahl-stamnes.net/dahls/

On Thu, 27 Nov 2008 15:01:33 +0100, Jørn Dahl-Stamnes wrote:

> Hi,
>
> just finnished installing Fedora Core 9. The machine is connected to a
> LAN with IP 192.168.2.30 and GW 192.168.2.1. But after boot the machine
> has no default GW.
>
> a 'route -n' say:
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0
> eth0
>
>
> I have to do a 'route add default gw 192.168.2.1' after boot.
>
> I have some other machines with FC4 and I have never had any problems
> with default gateway.
>
> How can I tell this machine which default gw to use at boot without
> having to add a script with the route add command?
>
> /etc/sysconfig/network:
> NETWORKING=yes
> HOSTNAME=obi-wan.mydomain.net
> GATEWAY=192.168.2.1
> IPV6_DEFAULTGW=
>
> and /etc/sysconfig/network-scripts/ifcfg-eth0: DEVICE=eth0
> BOOTPROTO=static
> BROADCAST=192.168.2.255
> HWADDR=00:1f:c6:be:4b:c3
> IPADDR=192.168.2.30
> IPV6INIT=yes
> IPV6_AUTOCONF=yes
> NETMASK=255.255.255.0
> NETWORK=192.168.2.0
> ONBOOT=yes
> DNS1=192.168.2.22
> SEARCH="mydomain.net"
> NM_CONTROLLED=

Try disabling NetworkManager. Early on in F9 NetworkManger was screwing
up when you used static IPs, I would have thought that it would be fixed
by now but maybe it hasn't been. I disabled it on all of my systems so I
don't know if the bug has been fixed or not.

General Schvantzkoph wrote:
> Try disabling NetworkManager. Early on in F9 NetworkManger was screwing
> up when you used static IPs, I would have thought that it would be fixed
> by now but maybe it hasn't been. I disabled it on all of my systems so I
> don't know if the bug has been fixed or not.

Thansk.

Network Manager is a new thing for me (I'm used to FC4). How do you disable
this in command mode? (remember I'm not using X11 since this machine shall
be a SQL server only).

--
Jørn Dahl-Stamnes
http://www.dahl-stamnes.net/dahls/

General Schvantzkoph wrote:
> Try disabling NetworkManager. Early on in F9 NetworkManger was screwing
> up when you used static IPs, I would have thought that it would be fixed
> by now but maybe it hasn't been. I disabled it on all of my systems so I
> don't know if the bug has been fixed or not.

Forget my previous question... I found a link in /etc/rc3.d for starting the
network manager. I manually tried to stop it resulting in no network access
at all!

This does not look as any solution at all.

--
Jørn Dahl-Stamnes
http://www.dahl-stamnes.net/dahls/

Jørn Dahl-Stamnes wrote:

> Hi,
>
> just finnished installing Fedora Core 9. The machine is connected to a LAN
> with IP 192.168.2.30 and GW 192.168.2.1. But after boot the machine has no
> default GW.

[putolin]

>
> I have to do a 'route add default gw 192.168.2.1' after boot.

[putolin]

you could add the route command to the /etc/rc.local script file

Jørn Dahl-Stamnes wrote:
> General Schvantzkoph wrote:
>> Try disabling NetworkManager. Early on in F9 NetworkManger was screwing
>> up when you used static IPs, I would have thought that it would be fixed
>> by now but maybe it hasn't been. I disabled it on all of my systems so I
>> don't know if the bug has been fixed or not.
>
> Forget my previous question... I found a link in /etc/rc3.d for starting the
> network manager. I manually tried to stop it resulting in no network access
> at all!
>
> This does not look as any solution at all.

/etc/init.d/NetworkManager stop
chkconfig NetworkManager off
chkconfig --levels 2345 network on
/etc/init.d/network start

Allen Kistler wrote:

> Jørn Dahl-Stamnes wrote:
>> General Schvantzkoph wrote:
>>> Try disabling NetworkManager. Early on in F9 NetworkManger was screwing
>>> up when you used static IPs, I would have thought that it would be fixed
>>> by now but maybe it hasn't been. I disabled it on all of my systems so I
>>> don't know if the bug has been fixed or not.
>>
>> Forget my previous question... I found a link in /etc/rc3.d for starting
>> the network manager. I manually tried to stop it resulting in no network
>> access at all!
>>
>> This does not look as any solution at all.
>
> /etc/init.d/NetworkManager stop
> chkconfig NetworkManager off
> chkconfig --levels 2345 network on
> /etc/init.d/network start

NetworkManager is running in the current runlevel, but still no default gw.
I have to add it from the command line. The config files are shown below
and contain the default gw.

/etc/sysconfig/network:
NETWORKING=yes
HOSTNAME=obi-wan.dahl-stamnes.net
IPV6_DEFAULTGW=

etc/sysconfig/network-scripts/ifcfg-eth0:
# nVidia Corporation MCP61 Ethernet
DEVICE=eth0
BOOTPROTO=none
BROADCAST=192.168.2.255
HWADDR=00:1f:c6:be:4b:c3
IPADDR=192.168.2.30
IPV6INIT=yes
IPV6_AUTOCONF=yes
NETMASK=255.255.255.0
NETWORK=192.168.2.0
ONBOOT=yes
DNS1=192.168.2.22
DNS2=194.213.166.140
SEARCH="dahl-stamnes.net"
NM_CONTROLLED=no
GATEWAY=192.168.2.1
TYPE=Ethernet

--
Jørn Dahl-Stamnes
http://www.dahl-stamnes.net/dahls/

Jørn Dahl-Stamnes wrote:
> Allen Kistler wrote:
>
>> Jørn Dahl-Stamnes wrote:
>>> General Schvantzkoph wrote:
>>>> Try disabling NetworkManager. Early on in F9 NetworkManger was screwing
>>>> up when you used static IPs, I would have thought that it would be fixed
>>>> by now but maybe it hasn't been. I disabled it on all of my systems so I
>>>> don't know if the bug has been fixed or not.
>>> Forget my previous question... I found a link in /etc/rc3.d for starting
>>> the network manager. I manually tried to stop it resulting in no network
>>> access at all!
>>>
>>> This does not look as any solution at all.
>> /etc/init.d/NetworkManager stop
>> chkconfig NetworkManager off
>> chkconfig --levels 2345 network on
>> /etc/init.d/network start
>
> NetworkManager is running in the current runlevel, but still no default gw.
> I have to add it from the command line. The config files are shown below
> and contain the default gw.
>
> [snip]

The commands I list turn off NetworkManager and keep it off forever,
replacing it with the legacy network script. Do all four of them. Try it.

Allen Kistler wrote:
> The commands I list turn off NetworkManager and keep it off forever,
> replacing it with the legacy network script. Do all four of them. Try
> it.

Thanks for your replies. I have just done what you suggested - Still NO
default gw!

In fact, I lost the default gw I have added manually once again

--
Jørn Dahl-Stamnes
http://www.dahl-stamnes.net/dahls/

Jørn Dahl-Stamnes wrote:
> Allen Kistler wrote:
>> The commands I list turn off NetworkManager and keep it off forever,
>> replacing it with the legacy network script. Do all four of them. Try
>> it.
>
> Thanks for your replies. I have just done what you suggested - Still NO
> default gw!
>
> In fact, I lost the default gw I have added manually once again

Then something else is screwed up. By re-enabling the legacy script,
your machine should now be using the config files you thought you were
using before (but weren't).