DHCP-Problem with new kernel
From: Robert Bamler (robert.bamler_at_gmx.de)
Date: 10/22/03
- Next message: Bill McIntyre: "Re: Enable corefile in RH8.0"
- Previous message: J. B. Wood: "Grub & BootMagic"
- Next in thread: Erwin Rieger: "Re: DHCP-Problem with new kernel"
- Reply: Erwin Rieger: "Re: DHCP-Problem with new kernel"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 22 Oct 2003 17:13:01 +0200
Hello,
I hope you can help me with a problem concerning a new kernel I built on
Debian woody. I can connect to my broadband router (Allied Telesyn) with my
onboard network card (VIA Rhine II Fast Ethernet Adapter) when booting with
the kernel that came with Debian. Then I compiled and set up a new kernel
and I tried to use the same options as the Debian developers chose. For
this reason I copied the file /boot/config-2.2.20-idepci to
/usr/linux/.config (the directory where I compiled my kernel). However, I
had to make some changes in the IDE-section in order to get linux mount the
root file system (Thanks again to the people in this group that helped me
doing this).
But when I now boot with the new kernel, I cannot access to the internet. I
get the following on startup:
-------------------------
Running 0dns-down to make sure resolv.conf is ok...done.
Cleaning: /etc/network/ifstate.
Setting up IP spoofing protection: rp_filter.
Configuring network interfaces... Internet Software Consortium DHCP Client
2.0pl5
opyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.
Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html
Listening on LPF/eth0/00:e0:4c:95:7b:4d
Sending on LPF/eth0/00:e0:4c:95:7b:4d
Sending on Socket/fallback/fallback-net
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
Trying recorded lease 192.168.1.12
PING 192.168.1.1 (192.168.1.1): 56 data bytes
--- 192.168.1.1 ping statistics ---
1 packets transmitted, 0 packets received, 100% packet loss
bound: renewal in 1073741011 seconds.
-------------------------
As a reference, I normally get this:
-------------------------
Running 0dns-down to make sure resolv.conf is ok...done.
Cleaning: /etc/network/ifstate.
Setting up IP spoofing protection: rp_filter.
Configuring network interfaces... Internet Software Consortium DHCP Client
2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.
Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html
Listening on LPF/eth0/00:e0:4c:95:7b:4d
Sending on LPF/eth0/00:e0:4c:95:7b:4d
Sending on Socket/fallback/fallback-net
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.12 -- renewal in 1073741823 seconds.
-------------------------
Running ifconfig directly after the failing DHCP-connect, I get:
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:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:112 (112.0 b) TX bytes:112 (112.0 b)
Instead of (what I get with the kernel that came with Debian):
eth0 Link encap:Ethernet HWaddr 00:E0:4C:95:7B:4D
inet addr:192.168.1.12 Bcast:192.168.1.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:1 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:328 (328.0 b) TX bytes:342 (342.0 b)
Interrupt:11 Base address:0xe800
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 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)
I am using KDE as default and when I switch to tty1 with Ctrl+Alt+F1 I
continuously get:
eth0: Setting full-duplex based on MII #1 link partner capability of 45e1.
NETDEV WATCHDOG: eth0: transmit timed out
eth0:Transmit timed out, status 0003, PHY status 786d, resetting...
eth0: Setting full-duplex based on MII #1 link partner capability of 45e1.
NETDEV WATCHDOG: eth0: transmit timed out
eth0:Transmit timed out, status 0003, PHY status 786d, resetting...
[...]
But I don't have CONFIG_WATCHDOG set in the kernel configuration. I cannot
stop these messages with Ctrl+C unless I pull out the ethernet cable from
my networking card.
I have already tried to fix this problem with ifconfig, route and dhclient,
but I had no success. I can configure the network with ifconfig so that
ping 192.168.1.1 (the address of my router) works, but I cannot connect to
the DHCP server with dhclient.
It would be great if you could help me with this problem. I am new to linux
and I don't know much about networking, so I am a bit confused with this
messages.
Thanks a lot,
Robert
- Next message: Bill McIntyre: "Re: Enable corefile in RH8.0"
- Previous message: J. B. Wood: "Grub & BootMagic"
- Next in thread: Erwin Rieger: "Re: DHCP-Problem with new kernel"
- Reply: Erwin Rieger: "Re: DHCP-Problem with new kernel"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
