Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have attempting without success to setup a DHCP client on a CLFS distro. I piggy-backed on an existing thread in the LFS forum, but it appears that it is not getting much visibility, and thus the reason for this new post.
Here's the situation... when I run "/etc/sysconfig/ifup eth0" all I get is the following output:
Code:
Bringing up the eth0 interface...
Starting dhclient on the eth0 interface...
Internet Systems Consortium DHCP Client V3.0.5
[snip]
Listening on LPF/eth0/00:30:59:02:42:ea
Sending on LPF/eth0/00:30:59:02:42:ea
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
No DHCPOFFERS received.
Unable to obtain a lease on the first try. Exiting.
The /etc/sysconfig/ifconfig.eth0/dhcpcd file looks like:
Module Size Used by
eepro100 23824 0
mii 4224 1 eepro100
evdev 6912 0
apm 15468 0
rtc 8628 0
With all of this information, can someone tell me why I cannot acquire an IP address from the Linksys router? All of my other systems (Ubuntu, Fedora Core 5, Fedora 7) work fine on my LAN, as does the actual cable running to the non-working system.
Please... I need help sorting out this issue.
Last edited by dwhitney67; 10-31-2007 at 02:41 PM.
Can you determine which kernel module is required for the ethernet controller, and whether or not that module is currently loaded.
I think this
Quote:
eth0 to 255.255.255.255
refers to local network or local host, something of the sort. You aren't getting past your firewall (if you have one) to the outside world. And, without the module refered to above, you won't.
Last edited by bigrigdriver; 10-31-2007 at 04:23 PM.
Still no joy with getting the networking up and running. Anyhow, I went back to my attempts to use DHCP because ultimately I must have a DHCP capable system/OS.
When I tried to "force" settings onto the eth0 interface using ifconfig, I still was not able to ping my router. I used a statement similar to the following:
What I cannot do is to get the eth0 to "run", or in other words have ifconfig display that it is RUNNING.
bigrigdriver-
What module are you referring to? The ethernet adapter I have requires the 'eepro100' kernel module, which is loaded (see my lsmod output). However, I cannot be certain that is being used by any service. How can I verify that it is?
The router, a Linksys WRT54G, is working just fine. I use both wired and wifi setups for my other systems. The system for which I am seeking help to configure is using a wired-connection... and yes, the CAT-5 cable it uses is fine.
I've been through the thread you posted. In fact, you may have noticed that I posted a query at the very end of it... of course, never getting a response. I was hoping the OP of that thread could help me.
notice in your static config you have the gateway, you also need that for dhcp to work. your NIC has no clue were to pull its IP from if you do not provide it with a gateway.
Are you sure about needing to specify a Gateway? That seems unusual because that is information that I would normally not be required to supply when I connect via DHCP. That information is obtained from the lease-holder (i.e. the router) and it is supposed to be inserted into /etc/resolv.conf by dhclient.
My issue is that dhclient can't talk/communicate with the router to get such information. It almost appears that a port (68) is being blocked.
Btw, from the dhclient man-page: The DHCP client normally transmits any protocol messages it sends before acquiring
an IP address to, 255.255.255.255, the IP limited broadcast address.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.