No DHCP on wired internet connection (Realtek RTL8139)
Hi everybody,
I am running Mandriva 2007 and have a wired network card, the Realtek RTL8139. If I connect to a network I do not receive DHCP offers, I assume that my DHCP requests do not even come through. If I connect to the network running Windows everything works fine, so it is not a network issue. I have this problem on all the networks I connect to using the wired NIC. It always works on Windows and never on Linux. When I set a fixed IP it still does not work, I can not ping any other machine in the network and I can not make use of the Internet. This is what happens: Quote:
Quote:
- putting "alias net-pf-10 off" in /etc/modprobe.conf - disable apic and lapic This is how my /etc/modprobe.conf looks: Quote:
Quote:
Best regards, Jethro Borsje |
The only thing I see that stands out is in "ifcfg-eth0" the metric is set to 10, but when in /var/log/messages it's showing it's going up as 100 Mbps Full Duplex. If I recall correctly (it's been a while) this isn't right. If it's trying to start as 100 Mbps and your metric is 10 Mbps, then it might affect it? You could try setting the metric in "ifcfg-eth0" to 100 and see what happens. If it doesn't help, you can always change it back.
-Josh- |
Realtek 8139 W/ Mandriva 2007
I have the same problem. Everything works in MShit but nodda in Mandriva. I even disabled the onboard Realtek and installed a pci nic and the same thing occurs.
I am using ALICE DSL connection here in Italy and in the configuration, it ask for user name and password (for pppoa). I enter this info correctly but nodda. I am using the ASUS A8N-ALI mainboard with the built in NIC Realek 8139 Thanks for any information, David :confused: |
Quote:
Quote:
I looked more closely and /var/log/messages and this part also looks strange to me: Quote:
Best regards, Jethro Borsje |
ok, the METRIC value is a routing metric (a cost per hop if used as a router) it is *not* the bandwidth, so that's not relevant.
does seem an odd scenario though. i would try to look at the situation from the DHCP server side though... can you try running a tcpdump or wireshark on the DHCP server to see what it is recieving? obviosuly if it's an ADSL router or somethign then that's not possible, but also you could just run wireshark on any other network pc, whcih because DHCP is a broadcast, will actually be recieved by all other machines. so that way you can actually pull apart the DCP request when the machine is booted in to Linux or Winodws (it was dual boot right?) and compare and contrast. also i would suggest trying to temporarily hard code the normal IP you get under windows and use that to force the interface up, and see that you are happily able to access the lan at IP level after that's done, thus removing issues about card drivers etc... |
If I manually set a static IP (being the IP I get under Windows) I can not ping to any server in the network, so I have no connection on the IP level. Even when forcing it with the correct IP adress, subnetmask and gateway. So there is something wrong with the driver then?
|
if would certainly seem so. check the contents of dmesg (specifically run "dmesg | grep eth0"), also the output of ifconfig and lsmod to show the driver for eth0 is loaded and in use. having said that, things look good above. erm, oh see what ethtool says about the physical status of the nic too. you might also try changing the driver from 8139too ro rtl8139, but i've always prefered the 8139too, works better in general, but that's about the only real variable i can suggest worth looking at at present.
|
This is what ethtool says when I did not plug in an UTP cable:
Quote:
These are the things I think are relevant from lsmod: Quote:
This is the relevant part of ifconfig (again with cable unplugged): Quote:
1 - do they look ok to you? 2 - should I have done this with the cable plugged in? (I don't have one present at this moment) Best regards, Jethro Borsje |
well the ethtool and ifconfig output when the cable is plugged in your really be more useful to be honest... you should see the "Link detected" entry go to yes and the speed shoudl go up to 100/full.
another potentially useful poin tof call would be to run a tcpdump on the client in question and see if it hears any broadcasts on the line without without an IP address. make some other clients generate broadcasts by renewing dhcp leases etc... |
Alright, I finally was at my workplace again and had the time to execute the commands WITH the cable PLUGGED IN. These are the results, firt ifconfig:
Quote:
Quote:
|
By the way, I also have madwifi configured and running for my wireless adapter. This does work on the same network. If I connect via my wireless adapter on a network which offers both wired and wireless access my Wireless adapter gets an IP-adress, my wired adapter does not.
|
All times are GMT -5. The time now is 12:27 AM. |