Hi,
Just installed Fedora 8 on a new Vostro 200. Everything seems to work fine, but the NIC has problems with the static IP. The card is Intel 82562V.

It is configured to IP 172.28.48.121 but somehow switches to 169.254.8.132 and looses the DNS.
These are the queries I have made:
/sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 00:1A:A0:9B:28:0B
inet addr:169.254.8.132 Bcast:169.254.255.255 Mask:255.255.0.0
inet6 addr: fe80::21a:a0ff:fe9b:280b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6333 errors:0 dropped:0 overruns:0 frame:0
TX packets:3191 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:3059349 (2.9 MiB) TX bytes:789167 (770.6 KiB)
Memory:fdfc0000-fdfe0000

ping 169.254.8.132
PING 169.254.8.132 (169.254.8.132) 56(84) bytes of data.
64 bytes from 169.254.8.132: icmp_seq=1 ttl=64 time=0.026 ms
64 bytes from 169.254.8.132: icmp_seq=2 ttl=64 time=0.020 ms

ping 172.28.48.121
PING 172.28.48.121 (172.28.48.121) 56(84) bytes of data.
64 bytes from 172.28.48.121: icmp_seq=1 ttl=64 time=0.026 ms
64 bytes from 172.28.48.121: icmp_seq=2 ttl=64 time=0.020 ms

So it seems the machine responds to both IP adresses (there is no other machine with same IP on the network).

Modules:
/sbin/lsmod | grep e100
e1000e 86757 0
e100 33997 0
mii 8385 1 e100
e1000 111877 0

I guess this means trouble - the e1000e thould be used I think but not sure.


dmesg | grep eth :

ADDRCONF(NETDEV_UP): eth0: link is not ready
0000:00:19.0: eth0: Link is Up 100 Mbps Full Duplex, Flow Control: RX
0000:00:19.0: eth0: 10/100 speed: disabling TSO
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
eth0: no IPv6 routers present

Not sure if that is informative?




So the network card basically works - but it states that it is using IP 169.254.8.132 and it looses the DNS every time the network script is started.

Any suggestions?
Anyone with similar problems?
The newest updates/kernel (2.6.23.8-63.fc8) are installed.

Thanks
Soren

Post contents of /etc/sysconfig/network-scripts/ifcfg-eth0
Also do you have NetworkManager service running? If using static I would disable this service.

Brian

Thanks Brian - did the trick!
Noticed that someone else had similar problem a few posts back - I guess something has changed in regards to static IP handling.

Thanks a lot for your help!

Soren

Glad to be of help.

Brian