Jump to content

No DHCP on wired internet connection [solved]


jethro
 Share

Recommended Posts

Hi everybody,

 

My wired network card does not get any DHCPOFFERS when I connect it to a network. Under Windows on the same network everything works fine. I do not know what might me the problem. The wireless network does get DHCPOFFERS from the same DHCP-server. Does anybody know how this can be fixed?

 

Best regards,

Jethro

 

PS. I am running Mandriva 2007 on my notebook with a Realtek RTL8139 network card.

Link to comment
Share on other sites

Can you post me the contents of the /etc/sysconfig/ifcfg-ethx file. where ethx is the ethernet card you're trying to get running.

 

Anyhow, as a side note, it could be that you're not getting dhcp because of ipv6, so make this change first and reboot. Edit /etc/modprobe.conf and add this line to the bottom:

 

alias net-pf-10 off

 

if that doesn't do it, then it could be an apic thing, so you can go into System/Configuration/Configure Your Computer/Boot/Boot Loader and then there are some options to disable apic and local apic. First disable apic and then reboot, that might do it. If not, disable local apic as well and reboot.

 

If that doesn't make a difference, post the contents of ifcfg-ethx file as previously mentioned.

Link to comment
Share on other sites

This is what I do:

[root@localhost network-scripts]# ifconfig eth0 up
[root@localhost network-scripts]# dhclient eth0
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/eth0/00:a0:d1:2f:9a:6a
Sending on   LPF/eth0/00:a0:d1:2f:9a:6a
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

 

This is the content of /etc/sysconfig/network-scripts/ifcfg-eth0:

[root@localhost network-scripts]# cat ./ifcfg-eth0
DEVICE=eth0
BOOTPROTO=dhcp
IPADDR=192.168.0.52
NETMASK=255.255.255.0
ONBOOT=yes
METRIC=10
MII_NOT_SUPPORTED=no
USERCTL=yes
RESOLV_MODS=no
IPV6INIT=no
IPV6TO4INIT=no
DHCP_CLIENT=dhclient
NEEDHOSTNAME=yes
PEERDNS=yes
PEERYP=yes
PEERNTPD=no

 

This is the content of modprobe.conf:

[root@localhost network-scripts]# cat /etc/modprobe.conf
alias eth0 8139too
alias sound-slot-0 snd-hda-intel
install scsi_hostadapter /sbin/modprobe sata_sil; /bin/true
remove snd-hda-intel /sbin/modprobe -r snd-pcm-oss; /sbin/modprobe --first-time -r --ignore-remove snd-hda-intel
install snd-hda-intel /sbin/modprobe --first-time --ignore-install snd-hda-intel && { /sbin/modprobe snd-pcm-oss; /bin/true; }
install usb-interface /sbin/modprobe ohci-hcd; /sbin/modprobe ehci-hcd; /bin/true
alias eth1 eth1394
alias ieee1394-controller ohci1394
alias ath0 ath_pci
alias net-pf-10 off

 

I boot with both noapic and nolapic, see lilo.conf:

[root@localhost network-scripts]# cat ../../lilo.conf
# File generated by DrakX/drakboot
# WARNING: do not forget to run lilo after modifying this file

default="linux"
boot=/dev/sda
map=/boot/map
keytable=/boot/us-intl.klt
menu-scheme=wb:bw:wb:bw
compact
prompt
nowarn
timeout=100
message=/boot/message
image=/boot/vmlinuz
	label="linux"
	root=/dev/sda6
	initrd=/boot/initrd.img
	append="noapic nolapic resume=/dev/sda7 splash=verbose"
	vga=788
image=/boot/vmlinuz
	label="linux-nonfb"
	root=/dev/sda6
	initrd=/boot/initrd.img
	append="noapic nolapic resume=/dev/sda7 splash=verbose"
image=/boot/vmlinuz
	label="failsafe"
	root=/dev/sda6
	initrd=/boot/initrd.img
	append="failsafe resume=/dev/sda7"
other=/dev/sda1
	label="windows"
	table=/dev/sda

Link to comment
Share on other sites

Your ifcfg-eth0 is confusing, because it's configured for DHCP, yet it has a static ip addressed assigned in it!

 

I would suggest deleting this file, and then reconfiguring your eth0 card using System/Configure/Configure Your Computer and in the networking you can find the wizard to set up a new lan connection. Set it for DHCP and you'll get a new blank ifcfg-eth0 created with just the relevant entries instead of a mixmatch of settings.

Link to comment
Share on other sites

I deleted the ifcfg-eth0 file and then set up a new lan / ethernet connection trough the control panel. This is the content of the new ifcfg-eth0 file:

[jethro@localhost network-scripts]$ cat ifcfg-eth0
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
METRIC=10
MII_NOT_SUPPORTED=no
USERCTL=yes
RESOLV_MODS=no
IPV6INIT=no
IPV6TO4INIT=no
DHCP_CLIENT=dhclient
NEEDHOSTNAME=yes
PEERDNS=yes
PEERYP=yes
PEERNTPD=no

 

I still do not receive DHCP offers on the ethernet card.

Link to comment
Share on other sites

OK, so is the wireless and wired unit the same router? I'm assuming that it's a wireless router that also has wired connections, and that this is providing the DHCP addresses?

 

If not, please explain how your network is setup so that I can picture how all is connected together.

Link to comment
Share on other sites

Well, my wired networkcard does not work in any setup, but this is the setup I tested it with yesterday: there is a wireless router with a DHCP server which is connected to a switch. I connect my laptop to this switch. With Windows my laptop then receives an IP adres from the wireless router, but with Mandriv 2007 it does not.

 

Currently I am at my work and there is a more complicated setup with a server and several routers. Here the wired network card also does not work.

Link to comment
Share on other sites

It could be that the Wireless Router is not passing DHCP to wired connections. It might not do this, or the feature might be disabled or something.

 

I have a firewall that offers DHCP, but it won't pass it over my wireless connection. You could have the same problem but the other way. You might need to give your machine a static IP address instead - as I had to do for my wireless connections, all my wireless connections are static IP.

 

I don't know about your office, but maybe they have the switches configured to block unknown mac addresses, although if you're responsible for all this, then maybe this is not the case. Either that, or there is something wrong with your network card.

 

I would configure it with a static IP address, and then see if you can ping your wireless router or even other machines on the network. If you can, then the card works, and the DHCP problem is with your network setup, or it's not offered by your wireless router on wired connections.

Link to comment
Share on other sites

When I run Windows on the same networks my wired network card does get an IP adres from the DHCP server, so in my opinion it can not be a MAC adress ore wireless issue. Because in these two cases it should also not work under Windows. So with Windows my wired connection works fine on all networks.

 

When I set a static IP under Linux I can not ping the DHCP server or anything else for that mather.

Link to comment
Share on other sites

After you edited the lilo.conf, did you rerun lilo to reinstall the boot loader? Because the only problem with Realteks in Linux is either IPV6 or the noapic stuff, and with lilo you have to run the lilo command from the prompt to reinstall lilo after making changes to lilo.conf.

 

And it sounds to me as if noapic and nolapic have been installed into the mbr to get it to work.

Link to comment
Share on other sites

I have edited Lilo trough the configuration panel of Mandriva 2007, I kind of expected that to run the "lilo" command for me. I will run it by hand again, just to be sure.

 

Is there a way to make sure Mandriva truly booted with noapci and nolapic?

Link to comment
Share on other sites

You can press esc at the lilo screen and type:

 

linux noapic nolapic

 

just to make sure.

I have just done that and it did not make a difference. It still does not work.

 

This is what I pulled out of /var/log/messages:

Dec 5 13:37:56 localhost kernel: NET: Registered protocol family 17

Dec 5 13:37:56 localhost kernel: ath_hal: module license 'Proprietary' taints kernel.

Dec 5 13:37:56 localhost kernel: ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)

Dec 5 13:37:56 localhost kernel: wlan: 0.8.4.2 (svn r1753)

Dec 5 13:37:56 localhost kernel: ath_rate_sample: 1.2 (svn r1753)

Dec 5 13:37:56 localhost kernel: ath_pci: 0.9.4.5 (svn r1753)

Dec 5 13:37:56 localhost kernel: ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11

Dec 5 13:37:56 localhost kernel: ACPI: PCI Interrupt 0000:02:04.0[A] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11

Dec 5 13:37:56 localhost kernel: wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps

Dec 5 13:37:56 localhost kernel: wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps

Dec 5 13:37:56 localhost kernel: wifi0: H/W encryption support: WEP AES AES_CCM TKIP

Dec 5 13:37:56 localhost kernel: wifi0: mac 7.8 phy 4.5 radio 5.6

Dec 5 13:37:56 localhost kernel: wifi0: Use hw queue 1 for WME_AC_BE traffic

Dec 5 13:37:56 localhost kernel: wifi0: Use hw queue 0 for WME_AC_BK traffic

Dec 5 13:37:56 localhost kernel: wifi0: Use hw queue 2 for WME_AC_VI traffic

Dec 5 13:37:56 localhost kernel: wifi0: Use hw queue 3 for WME_AC_VO traffic

Dec 5 13:37:56 localhost kernel: wifi0: Use hw queue 8 for CAB traffic

Dec 5 13:37:56 localhost kernel: wifi0: Use hw queue 9 for beacons

Dec 5 13:37:56 localhost kernel: wifi0: Atheros 5212: mem=0xc0200000, irq=11

Dec 5 13:37:56 localhost kernel: 8139too Fast Ethernet driver 0.9.27

Dec 5 13:37:56 localhost kernel: ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10

Dec 5 13:37:56 localhost kernel: ACPI: PCI Interrupt 0000:02:07.0[A] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10

Dec 5 13:37:56 localhost kernel: eth0: RealTek RTL8139 at 0xf9126000, 00:a0:d1:2f:9a:6a, IRQ 10

Dec 5 13:37:56 localhost kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

Dec 5 13:37:56 localhost kernel: ACPI: PCI Interrupt 0000:00:14.2[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11

Dec 5 13:37:57 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4

Dec 5 13:37:58 localhost kernel: hda_codec: Unknown model for ALC861, trying auto-probe from BIOS...

Dec 5 13:38:01 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8

Dec 5 13:38:09 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7

Dec 5 13:38:16 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18

Dec 5 13:38:17 localhost kernel: tun: Universal TUN/TAP device driver, 1.6

Dec 5 13:38:17 localhost kernel: tun: © 1999-2004 Max Krasnyansky <maxk@qualcomm.com>

Dec 5 13:38:17 localhost udevd-event[3402]: udev_node_symlink: symlink(../tun, /dev/net/tun) failed: File exists

Dec 5 13:38:17 localhost avahi-daemon[3509]: Found user 'avahi' (UID 71) and group 'avahi' (GID 71).

Dec 5 13:38:18 localhost avahi-daemon[3509]: Successfully dropped root privileges.

Dec 5 13:38:18 localhost avahi-daemon[3509]: avahi-daemon 0.6.13 starting up.

Dec 5 13:38:18 localhost avahi-daemon[3509]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!

Dec 5 13:38:18 localhost avahi-daemon[3509]: Successfully called chroot().

Dec 5 12:38:18 localhost avahi-daemon[3509]: Successfully dropped remaining capabilities.

Dec 5 12:38:18 localhost avahi-daemon[3509]: Failed to read /etc/avahi/services.

Dec 5 12:38:18 localhost avahi-daemon[3509]: socket() failed: Address family not supported by protocol

Dec 5 12:38:18 localhost avahi-daemon[3509]: Network interface enumeration completed.

Dec 5 12:38:18 localhost avahi-daemon[3509]: Registering HINFO record with values 'I686'/'LINUX'.

Dec 5 12:38:18 localhost avahi-daemon[3509]: Server startup complete. Host name is localhost.local. Local service cookie is 2248768130.

Dec 5 13:38:18 localhost rpc.statd[3649]: Version 1.0.9 Starting

Dec 5 13:38:19 localhost xinetd[3599]: xinetd Version 2.3.14 started with libwrap options compiled in.

Dec 5 13:38:19 localhost xinetd[3599]: Started working: 0 available services

Dec 5 13:38:19 localhost kdm_config[3671]: Invalid option value 'All' at /usr/share/config/kdm/kdmrc:359

Dec 5 13:38:21 localhost crond[3811]: (CRON) STARTUP (V5.0)

Dec 5 13:38:22 localhost kernel: mtrr: no more MTRRs available

Dec 5 13:38:23 localhost kernel: NETDEV WATCHDOG: eth0: transmit timed out

Dec 5 13:38:25 localhost nmbd[3874]: [2006/12/05 13:38:25, 0] nmbd/nmbd_subnetdb.c:create_subnets(188)

Dec 5 13:38:25 localhost nmbd[3874]: create_subnets: No local interfaces !

Dec 5 13:38:25 localhost nmbd[3874]: [2006/12/05 13:38:25, 0] nmbd/nmbd_subnetdb.c:create_subnets(189)

Dec 5 13:38:25 localhost nmbd[3874]: create_subnets: Waiting for an interface to appear ...

Dec 5 13:38:26 localhost kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

 

Dec 5 13:38:34 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21

Dec 5 13:38:51 localhost kernel: hda-intel: Invalid position buffer, using LPIB read method instead.

Dec 5 13:38:55 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3

Dec 5 13:38:55 localhost net_applet[4368]: ### Program is starting ###

Dec 5 13:38:55 localhost mdkapplet[4370]: ### Program is starting ###

Dec 5 13:38:58 localhost dhclient: No DHCPOFFERS received.

Dec 5 13:38:58 localhost ifplugd(eth0)[1988]: client: Determining IP information for eth0... failed.

Dec 5 13:38:58 localhost ifplugd(eth0)[1988]: Program execution failed, return value is 1.

Dec 5 13:38:58 localhost ifplugd(eth0)[1988]: Exiting.

 

Perhaps this means anything to you?

 

Best regards,

Jethro

Link to comment
Share on other sites

Is there nothing else I can try? Thinking about it I gues there is something wrong with the ethernet layer of my wired network card, because even if I set up my network card with a static IP I am still not able to ping to another pc in the network.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...