Madwifi broke eth0 static IP address

[rockyl]

I recently installed FC6 x86_64 and upgraded the kernel to 2895. It's been working great for a few weeks. I have a small LAN on eth0 and this machine is a gateway to a dialup connection. I am trying to get madwifi going on a DLink (Atheros) pcmcia card. I am still tinkering with that, but this morning I booted up and the other machines on the LAN couldn't connect. I traced it down to them doing an arp request for 192.168.0.1 and not getting any reply. I then rna ifconfig and the IP address for eth0 is now 192.168.0.252. It seems that it is doing a dhcp request and giving itself that address.

When I run system-config-network it still shows eth0 as having a static IP address at 192.168.0.1.

Does anyone know where I might look to see where and why it is doing a dhcp request? I can set it back manually, but that would be a PITA if I had to do it every time.

[Brian1]

What does the file /etc/sysconfig/network-scripts/ifcfg-eth0 contain? Post contents.
Also post output of /sbin/ifconfg -a

Brian

[rockyl]

Here's ifcfg-eth0:

# cat /etc/sysconfig//network-scripts/ifcfg-eth0
# Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+
DEVICE=eth0
BOOTPROTO=none
BROADCAST=192.168.0.255
HWADDR=00:15:F2:47:9E:80
IPADDR=192.168.0.1
NETMASK=255.255.255.0
NETWORK=192.168.0.0
ONBOOT=yes
TYPE=Ethernet

Here's /sbin/ifconfig immediately after boot :

ath0 Link encap:Ethernet HWaddr 00:15:E9:73:44:C3
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth0 Link encap:Ethernet HWaddr 00:15:F2:47:9E:80
inet addr:192.168.0.252 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:73 (73.0 b) TX bytes:1320 (1.2 KiB)
Interrupt:21 Base address:0x4000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2150 errors:0 dropped:0 overruns:0 frame:0
TX packets:2150 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2150161 (2.0 MiB) TX bytes:2150161 (2.0 MiB)

wifi0 Link encap:UNSPEC HWaddr 00-15-E9-73-44-C3-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:20 errors:0 dropped:0 overruns:0 frame:2657
TX packets:97 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:1182 (1.1 KiB) TX bytes:4462 (4.3 KiB)
Interrupt:17 Memory:ffffc200100a0000-ffffc200100b0000


Here's /sbin/ifconfig -a current after setting IP to 192.168.0.1:

# /sbin/ifconfig -a
ath0 Link encap:Ethernet HWaddr 00:15:E9:73:44:C3
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth0 Link encap:Ethernet HWaddr 00:15:F2:47:9E:80
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:183 errors:0 dropped:0 overruns:0 frame:0
TX packets:183 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13225 (12.9 KiB) TX bytes:18528 (18.0 KiB)
Interrupt:21 Base address:0x4000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4198 errors:0 dropped:0 overruns:0 frame:0
TX packets:4198 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2207569 (2.1 MiB) TX bytes:2207569 (2.1 MiB)

ppp0 Link encap:Point-to-Point Protocol
inet addr:66.81.46.30 P-t-P:69.19.217.21 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:1569 errors:0 dropped:0 overruns:0 frame:0
TX packets:1629 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:573280 (559.8 KiB) TX bytes:260626 (254.5 KiB)

wifi0 Link encap:UNSPEC HWaddr 00-15-E9-73-44-C3-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:198 errors:0 dropped:0 overruns:0 frame:104453
TX packets:865 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:11576 (11.3 KiB) TX bytes:39790 (38.8 KiB)
Interrupt:17 Memory:ffffc200100a0000-ffffc200100b0000

[Brian1]

That is very strange. Do you have NetworkManager running? If disable that and reboot.
Something is telling it to change IP down the line. Look in /etc/rc.local and see anything is in there to change IP.

Brian

[rockyl]

# ps -ef | grep -i net
root 2519 1 0 11:07 ? 00:00:00 NetworkManager --pid-file=/var/run/NetworkManager/NetworkManager.pid
root 2535 1 0 11:07 ? 00:00:00 NetworkManagerDispatcher --pid-file=/var/run/NetworkManager/NetworkManagerDispatcher.pid


It looks like it is running. Is this different from Network Device Control and/or the Network system service? I thought there was supposed to be an icon on the tray (maybe that is only gnome, I am running kde).

[rockyl]

Here is what nm-tool says. I think you may be onto something.

# nm-tool

NetworkManager Tool

State: connected

- Device: eth0 ----------------------------------------------------------------
NM Path: /org/freedesktop/NetworkManager/Devices/eth0
Type: Wired
Driver: 8139too
Active: yes
HW Address: 00:15:F2:47:9E:80

Capabilities:
Supported: yes
Carrier Detect: yes
Speed: 100 Mb/s

Wired Settings
Hardware Link: yes

IP Settings:
IP Address: 192.168.0.252
Subnet Mask: 255.255.255.0
Broadcast: 192.168.0.255
Gateway: 192.168.0.1
Primary DNS: 66.81.1.251
Secondary DNS: 66.81.1.252

[rockyl]

I suspect what is happening is that the DHCP client is now started at boot time. Reading the info page it says that, if there is no dhclient.conf file (which there is not) then it will obtain a list of all network interfaces and attempt to get leases for each one.

[Brian1]

NetworkManager is a tool that is suppose to check for network connections whether wired or wireless and bring them up or down when cables are connected or removed. For me it does not work well so I disable it and set the correct files.

Brian

[rockyl]

I disabled NetworkManager and it works now.

Thanks.

[Brian1]

Glad to see you you have it working. That NetworkManager can be a pain. Usually works fine but when you start adding multiple nics and network connections it can go crazy on its own.

Brian