|
Slackware 10 dhcpcd MAC address on a laptop questions
Trust me, I have been scanning all of the prior LQ dhcpcd posts and I still can't solve my issue. I have validated that my network card in the laptop does work, since it will work with a static IP address.
Therefore, I am sorry that I have to ask this question again.. I am running Slackware 10, kernel: 2.4.26. After selecting DHCP in netconfig: 1. If I run ifconfig, I only get the 'lo' entry. If I run ifconfig -a then I get my eth0 entry. As I understand, this means that my eth0 is not seen. What are the steps to correct this? I do have eth0 showing up at start up and eepro100.c is there as well. 2. During netconfig; should I choose DHCP or loopback? 3. I don't have a DHCP Hostname available to me, is this causing the issue? 4. When I type the following in the directory: /etc/rc.d/ ./rc.inet1 stop I get the message: **** /sbin/dhcpcd: not running If I type: ./rc.inet1 start I get the message: dhcpcd: MAC address = 00:d059:c5:1e:b5 What does all this mean? 5. I assume that I need to set-up the client daemon (dhcpcd), thus I followed DHCP mini-HOWTO at: http://www.tldp.org/HOWTO/DHCP/x74.html#NAMESERVER However, how do I setup my dhcpd.conf file? SiegeX post on LQ is really good, however this still is very confusing. Any direction would be helpful, I like Slackware 10, everything runs great except DHCP as of right now... Thank you for reading this post. |
It sounds like you may have the same problem I did.
If after you bootup and you see only your 'lo' then it's because it didn't init your eth0 network card properly. Reasons could be, 1) failed negotiation, 2) bad cable 3) wrong driver or no driver loaded or 4) nothing. I have a wireless card WP11 and I had to add a line to my /etc/rc.d/rc.local file to have dhcpcd load using my eth0 card as follows: /sbin/dhcpd eth0 that's all. I also had to add my ESSID and WEP Key but that's more than you need to worry about. from the command line just type 'dhcpcd eth0' as root and see what happens.. Providing you could get it to work with just a static address, this hopefully will help. |
Thanks for the reply Oderus.
From the /sbin directory, I ran ./dhcpcd eth0 And I did not get anything returned, plus it took about 20 seconds for my shell prompt to return. I typed ifconfig again and I still only saw the 'lo' entry. I have tried googling this subject as well without much luck. |
Your 20 second delay tells me you have no support for your network card..
what network card have you got? try dmesg and look for that card name if at all... dmseg | grep name of card works great. i.e.: to check usb stuff, dmseg | grep usb also check out /etc/inetd.conf and make sure you have eth0 setup for dhcp .. you can also enable debug mode there by saying YES to the last line... (cant remember the syntax off-hand) |
I think the nic module is loaded and that the problem is more likely with the dhcp server/dhcp client communications. If the dhcpcd client doesn't see a nic to configure it starts complaining about that and not showing the MAC address of the card :D
man dhcpcd had a good suggestion : turn on logging to see what's happening. Code:
-d With this flag dhcpcd will syslog(LOG_DEBUG,...) messages for about every step it does. It's recom_ |
No firewall enabled and ports are open on dhcp server. The only reason I know this is because the SuSE 9.1 Professional is using DHCP without any issues.
I will run the debugging first thing in the morning. I guess the million dollar question is 'Do I setup my dhcpd.conf file?' Again, SiegeX post on LQ is really good, however this still is very confusing. Thank you for reading this post. |
I wouldn't bother with the dhcpcd.conf file ..
You may want to check out the /etc/rc.d/rc.inet1.conf config and make you have a DHCP hostname and that DHCP is enabled for eth0. You can also enable debug mode for DHCP in the same file at the bottom, just say YES to the debug DHCP option. |
We don't use DHCP hostname at my office. I know, I have asked over and over. At home, I do have a DHCP hostname from my ISP Cable Modem provider and everything works fine.
|
It may be that the kernel module your NIC needs has not been loaded. What exact NIC are you using, and what is the output from lsmod?
Also, have you tried manually bouncing your eth0 interface? Sometimes that's all it takes Code:
ifconfig |
dhcpcd eth0 -d log results
I ran:
dhcpcd eth0 -d and the log file came back with: broadcasting DHCP_DISCOVER timed out waiting for a valid DHCP server response The NIC card I have is: Module Size Used by eepro100 19252 0 mii 2272 0 [eepro100] Is this correct? Because my specs are: The Evo N400c comes with the following interface: 1 RJ-45 (NIC): Ethernet - The integrated combo card NIC is an Intel EEPRO100 supported. Yes, I have tried to manually shutdown and I get the following: ifconfig -> The lo listing only ifconfig eth0 down ifconfig eth0 up ifconfig -> The lo and eth0 listings However, the eth0 does not have an IP address, but states: UP BROADCAST NOTRAILERS RUNNING MULTICAST Do I need to turn off Multicast? How would I do that? Thank you for all of the responses so far... we're getting there.... |
I think it's still autonegotiation failing ..
how is your home network setup?? One cable/dsl router or direct to the internet? I would either try to force it to 10Mb or power off, then power back on with the network cable plugged in. That helped for me on my server, but it's a little older then your system seems to be. |
Another thing to try would be to manually restart DHCP
Code:
dhcpcd -r eth0 |
Thread Closed
This turned out to be the subnet DHCP scope was out of addresses to distribute. THANK YOU TO ALL WHOM HAVE TOOK THE TIME TO READ THIS! Thread Closed |
| All times are GMT -5. The time now is 12:05 AM. |