Network-manager not working properly in Fedora 8

fpaolini · #1 19th September 2009, 03:28 PM

Hi, I have installed recently the Fedora 8 in a computer and during installation it was set a static IP with the netmask and gateway.
At first it worked well, but after some boots the connection begins to fail.

It seems that the network-manager withdraws the static IP and tries
to get connection via DHCP.

Below is the /var/log/messages file during the failed connection:

Code:

Sep 19 10:36:53 canario avahi-daemon[1695]: Interface eth0.IPv4 no longer relevant for mDNS.
Sep 19 10:36:53 canario avahi-daemon[1695]: Withdrawing address record for fe80::20d:87ff:fe0c:355f on eth0.
Sep 19 10:36:53 canario NetworkManager: <info>  SWITCH: terminating current connection 'Auto Ethernet (eth0)' because it's no longer valid.
Sep 19 10:36:53 canario NetworkManager: <info>  Deactivating device eth0.
Sep 19 10:37:07 canario system-config-network[2195]: -+ //etc/modprobe.conf #011eth0 alias sis900
Sep 19 10:37:08 canario system-config-network[2195]: chmod 0644 //etc/sysconfig/networking/devices/ifcfg-eth0
Sep 19 10:37:08 canario system-config-network[2195]: chmod 0644 //etc/sysconfig/networking/devices/ifcfg-eth0:1
Sep 19 10:37:08 canario system-config-network[2195]: ln //etc/sysconfig/networking/devices/ifcfg-eth0:1 //etc/sysconfig/networking/profiles//default/ifcfg-eth0:1
Sep 19 10:37:08 canario system-config-network[2195]: ln //etc/sysconfig/networking/devices//ifcfg-eth0:1 //etc/sysconfig/network-scripts//ifcfg-eth0:1
Sep 19 10:37:08 canario system-config-network[2195]: rm //etc/sysconfig/network-scripts//ifcfg-eth0
Sep 19 10:37:08 canario system-config-network[2195]: rm //etc/sysconfig/networking/profiles/default/ifcfg-eth0
Sep 19 10:37:17 canario NetworkManager: <info>  SWITCH: no current connection, found better connection 'Auto Ethernet (eth0)'.
Sep 19 10:37:17 canario NetworkManager: <info>  Activating device eth0
Sep 19 10:37:17 canario NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Sep 19 10:37:17 canario NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Sep 19 10:37:17 canario NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Sep 19 10:37:17 canario NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Sep 19 10:37:17 canario NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Sep 19 10:37:17 canario NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Sep 19 10:37:17 canario NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Sep 19 10:37:17 canario NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Sep 19 10:37:17 canario NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Sep 19 10:37:17 canario NetworkManager: <info>  Activation (eth0) Beginning DHCP transaction.
Sep 19 10:37:17 canario NetworkManager: <info>  dhclient started with pid 2339
Sep 19 10:37:17 canario NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Sep 19 10:37:17 canario dhclient: Internet Systems Consortium DHCP Client V3.0.6-Fedora
Sep 19 10:37:17 canario dhclient: Copyright 2004-2007 Internet Systems Consortium.
Sep 19 10:37:17 canario dhclient: All rights reserved.
Sep 19 10:37:17 canario dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Sep 19 10:37:17 canario dhclient:
Sep 19 10:37:17 canario NetworkManager: <info>  DHCP: device eth0 state changed normal exit -> preinit
Sep 19 10:37:17 canario dhclient: Listening on LPF/eth0/00:0d:87:0c:35:5f
Sep 19 10:37:17 canario dhclient: Sending on   LPF/eth0/00:0d:87:0c:35:5f
Sep 19 10:37:17 canario dhclient: Sending on   Socket/fallback
Sep 19 10:37:17 canario dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Sep 19 10:37:19 canario avahi-daemon[1695]: Registering new address record for fe80::20d:87ff:fe0c:355f on eth0.*.
Sep 19 10:37:20 canario kernel: eth0: Media Link On 100mbps full-duplex
Sep 19 10:37:21 canario avahi-daemon[1695]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.3.
Sep 19 10:37:21 canario avahi-daemon[1695]: New relevant interface eth0.IPv4 for mDNS.
Sep 19 10:37:21 canario avahi-daemon[1695]: Registering new address record for 192.168.1.3 on eth0.IPv4.
Sep 19 10:37:25 canario dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13

The output of ifconfig eth0 is

Code:

eth0      Link encap:Ethernet  HWaddr 00:0D:87:0C:35:5F
          inet addr:169.254.29.218  Bcast:169.254.255.255  Mask:255.255.0.0
          inet6 addr: fe80::20d:87ff:fe0c:355f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:97 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:16969 (16.5 KiB)
          Interrupt:11 Base address:0xd400

To solve this problem I stopped the network-manager and set by hand the network, through the ifconfig and route command and editing the /etc/resolv.conf file.

I would like some guesses about why the network-manager presents such a problem.
Thanks.

lollysticky · #2 19th September 2009, 05:42 PM

cause NetworkManager sucks :P

No, offcourse not, but if you can, it's always more reliable to configure the network manually instead of using networkmanager (which is - in my opinion - only needed if you use wireless interfaces).

I've seen networkmanager do some really weird stuff and i decided to stop using it.

fpaolini · #3 19th September 2009, 07:00 PM

Yes, I am not so friend of NetworkManager too.

I will remome the starting of the networkmanager at boot time.
I think it is a simple task.
Another thing is activating the network at boot.
I am used with Debian but not so with Fedora.

I wil search a little in the net and if I have difficulties I will return here.
Any way, there is something similar to the file /etc/network/interfaces in the Fedora?

Thanks

lollysticky · #4 20th September 2009, 03:29 PM

I don't know which file you mean exactly (since I am not used to Debian), but these files are the most important to configure your connection:

/etc/sysconfig/network-scripts/ifcfg-<device>
/etc/sysconfig/network-scripts/route-<device>

another route you can take, is to try "wicd"; it's a python-based networkmanager and I found it to be more reliant that the NetworkManager service. You can only locate it in the atrpms repo!

fpaolini · #5 20th September 2009, 05:01 PM

Thanks lollysticky, I have configured the file
/etc/sysconfig/network-scripts/ifcfg-eth0
(which seems to have the same role of /etc/network/interfaces in Debian like distributions)
like that

Code:

DEVICE=eth0
ONBOOT=yes
BOOTPROTO=none
IPADDR=192.168.1.3
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
TYPE=Ethernet

and cancelled the networkmaneger and inicialized the network script on boot (through the symbolic links on /etc/rc5.d).
It works!
Some one knows the meaning of "BOOTPROTO"? Should I put "static" instead of none?

I did not need the file /etc/sysconfig/network-scripts/route-<device>. I dont know, but maybe it is need to a more complex network.

Soon I will take a look at the "wicd" program.
Thanks!

lollysticky · #6 20th September 2009, 06:42 PM

1) yup that file is correct. BOOTPROTO determines the protocol that the connection will use: DHCP or static ('none'). If you want a static IP, obviously use static, else dhcp.

2) the route file is not created by default, you need to create it. But idd, it can be unnecessary if it works like this

P.S.
just another line you can add to the script (if you need it, that is):
NICKNAME=<whatever-your-computer-is-called-like>