Tuesday, October 3, 2023
 Popular · Latest · Hot · Upcoming
rated 0 times [  6] [ 0]  / answers: 1 / hits: 19905  / 2 Years ago, sun, november 14, 2021, 10:15:26


so 2 days ago, I went to bed with my internet working but when I woke up it wasn't. When I had a closer look last night, it seems syslog suggests that DHCP request times out?!

This was not happening just a couple of days ago. I'm not sure if the computer rebooted/updated during the night, but I think it didn't (movie still playing). The ethernet port light does not blink (green is ALWAYS on now, red/orange never blinks).

What could the problem be here?

[Not at my computer right now, might take a while to print responses from terminal]

Edit1: my eth0 lists an IPv6 address but not a IPv4 address, and I've set IPv6 to 'ignore', could that be an issue?

More From » networking


You can check to see the status of a DCHP update by running this in a terminal:

sudo dhclient eth0 # assuming eth0 is your network adapter

That will try and get the network settings up and going and it will tell you what it's trying to do (so if it does make contact and then fails, you should see the result). If it doesn't make contact, you'll see it going on and on and on.

Before we get too ahead of ourselves though, you should make sure that this isn't a physical issue. That you think the lights are displaying in a strange way should be an indicator that there could be a problem either with the cable or the ports at either end of it. Some tests for you:

  • Try turning it off then on again.

  • If you have another network adapter on this computer, try it.

  • If the router has another port, try it.

  • If you have a spare cable, chuck it in.

  • If you have (or can borrow, buy or steal) another computer, try that on this network connection.

  • Make sure nobody dropped the internet. Okay, that's enough IT Crowd. Sorry, I couldn't resist.

Getting back the woes of DHCP, our DHCP server here sometimes goes flying down in a burst of flames. For the computers that are assigned IPs by it (semi-statically, in that they should always have the same IP), I moved them to fully-static configurations without much hassle.

If it's running Network Manager (as most Ubuntu desktops do) you want a configuration that looks something like the following screenshot. DNS is optional but I find using Google's DNS server lets me troubleshoot one less thing when the router has a hissy-fit. Gateway is probably the most important thing for routing traffic properly.

If it's a server or you've ripped out Network Manager, the manual configuration lives in /etc/network/interfaces so you want to run sudoedit /etc/network/interfaces and paste in a configuration like this one. If you're still running Network Manager, as soon as it starts running, it's going to alter this configuration to whatever it wants to. If you're running Network Manager, use the other config.

auto eth0
iface eth0 inet static

Same applies to the gateway. Get it right or you can't contact the outside world. As for the IP you pick. In either of these cases, you need to make sure you're picking something that isn't assigned by DHCP. An IP conflict can very quickly knacker any connectivity.

[#44859] Monday, November 15, 2021, 2 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.

Total Points: 162
Total Questions: 116
Total Answers: 108

Location: Guam
Member since Mon, May 29, 2023
5 Months ago
amelican questions
Sun, Aug 14, 22, 01:26, 1 Year ago
Mon, Apr 24, 23, 18:12, 6 Months ago
Wed, Apr 5, 23, 04:30, 6 Months ago
Thu, Sep 1, 22, 02:14, 1 Year ago
Mon, Sep 19, 22, 23:08, 1 Year ago