Dhcp problems with debian linux-image-2.6.15-1-686 in etch
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Dhcp connection problem with debian linux-image-2.6.15-1-686 in etch
I recently installed the new kernel in debian etch and found, after booting that the networking would not work. When I ran dhclient, it would just keep on sending dhcp requests on port 67 to 255.255.255.255. I would never recieve any dhcp offers. Even after waiting for a long time, it never recieves any. In kernel 2.6.12, dhclient works fine and I am able to use networking. (I am using 2.6.12 with wireless right now )
Any ideas on how to fix this?
Last edited by notapplicable; 02-12-2006 at 11:46 PM.
Oh yes, I forgot to say that the computer is an IBM 600X without an ethernet port and I have to use a PCMCIA card to use ethernet. I think this might be part of the problem because I also tried it on a T23 and the networking worked just fine.
When I type route in 2.6.12, I get something but in 2.6.15, I get an empty table. What should I do? My dhcp server is just a wireless router... I don't know how to run a dhcpd -f or something on a router...
Yes, sorry. I dont have permanent internet access, sorry again.
Now, how you access the ethernet is not important at this point. If they transmit IP, the routing tables and ipchains are valid means of manipulating traffic.
You need to add a route from your machine in and out of the network. try typing this ($ is the prompt):
$route add -net 192.168.0.0 netmask 255.255.255.0 dev eth0
Now the kernel knows that everything from and to 192.168.0.1-255 is to be fed through eth0. Adjust the values to your network (copy those from 2.6.12?).
For info about what route is and does, type ($ is the prompt):
You dont habe to read it all, but it could give you a hint as to how to use route as syntax. If you have questions or if it doesn't work, post. I will try to be on more frequently...
By copy I meant "look what settings that kernel had while booting and apply them to the new one".
Is the pcmcia ethernet card even recognized by the system? type
which will list the network devices available to you and it is a way to manually configure you IP and netmask. If you know the address of the router, ping it to see if the network is working at all. There is at least one device registered, the loopback device. perhaps the card is called something else than "eth0"?
If I am right, then this problem extends far beyond you dhcp problem, I think you don't have the drivers for the pcmcia card (did you even enable the support for it when compiling the kernel?). If you do not have the drivers available go to the manufacturers homepage and check if he has them. If not, write to their support and demand them (I am a bit sceptic about 3rd party drivers)!