Monday, April 29, 2024
 Popular · Latest · Hot · Upcoming
3
rated 0 times [  3] [ 0]  / answers: 1 / hits: 41974  / 2 Years ago, mon, august 29, 2022, 12:19:38

A new Kubuntu 12.04 install is not getting IP addresses from either the wired connection nor from any wireless connection. The cables / router ports / wifi adapter / access point are all known good and work with other equipment. I suspected a failed NIC but seeing how the wireless connections also aren't working via USB wifi adapter, that eliminates the NIC as a possible source of the issue. What other hardware might be shared between the wired (onboard NIC) and wireless (USB wifi adapter)? I stress that with the wifi adapter I see other networks, but cannot get an IP address from them either. Testing with a Kubuntu 11.10 LiveCD has the same results.



I notice that there is no /etc/dhcp/dhclient.conf file.


More From » networking

 Answers
7

Try sudo apt-get install isc-dhcp-client, which will install the dhcp client, though it won't explain why it wasn't installed to begin with. This also presumes that your problem is a lack of said client.



If that doesn't work, you should look into using the tcpdump command on one of the interfaces and post back here with the results. For example, sudo tcpdump -i eth0 -n should show you if there is any traffic passing over the eth0 interface, though you may need to correct for the right interface.



Since tcpdump didn't see any traffic, start the tcpcommand again, unplug your LAN connection, wait a couple seconds for the computer to realize you've unplugged it, then plug it back in and look at the tcpdump output. There should be several DHCP request sent out by you're computer, and under ideal circumstances, responses to those queries as well. If you don't see anything at all, then perhaps DHCP is request an address on the wrong port, maybe check DHCP configuration. If after checking your DHCP configuration you're sure that DHCP is requesting an address on the correct port but that you're not seeing any traffic with tcpdump, check the logs for any errors related to DHCP or errors transmitting network traffic. If nothing is obvious, post the logs here.



Beyond that, I don't know what else to do to diagnose this, perhaps your suspicions of faulty hardware were correct, or more unlikely, driver trouble.


[#37176] Tuesday, August 30, 2022, 2 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
irripri

Total Points: 164
Total Questions: 111
Total Answers: 107

Location: South Georgia
Member since Sun, Aug 8, 2021
3 Years ago
;