View previous topic :: View next topic |
Author |
Message |
Rede n00b
Joined: 03 Jun 2007 Posts: 67
|
Posted: Thu Oct 02, 2008 2:24 am Post subject: eth0 problem... |
|
|
I don't know what happened but I restarted my computer this morning (all was working fine till I did this) and when it came back online I can no longer connect to the internet.
When booting up it displays the following:
Code: |
eth0: dhcpcd 4.0.1 starting
eth0: waiting for carrier
eth0: carrier acquired
eth0: broadcasting for a lease
eth0: offered 192.168.1.3 from 192.168.1.1 '?'
eth0: checking 192.168.1.3 is available on attached networks
eth0: NAK: (null)
eth0: broadcasting for a lease
eth0: offered 192.168.1.3 from 192.168.1.1 '?'
eth0: checking 192.168.1.3 is available on attached networks
eth0: acknowledged 192.168.1.3 from 192.168.1.1 '?'
eth0: leased 192.168.1.3 for 259200 sceonds
* eth0 received address 192.168.1.3/24
|
If anyone has a clue what I may have done please let me know. |
|
Back to top |
|
|
ZeuZ_NG Guru
Joined: 10 Sep 2008 Posts: 453 Location: Near /dev/urandom | /dev/null
|
Posted: Thu Oct 02, 2008 3:44 am Post subject: |
|
|
Well, what's the output of ifconfig -a about it?
Also, is your nameserver located at /etc/resolv.conf ?
have you tried running dhcpd/dhclient again after you finished the boot-up process? Perhaps it's a problem of some daemon/process not behing ready...
EDIT:
Also, can you ping your router? or any other host on the lan? _________________ | Intel Core i7 920. | Intel DX58SO Extreme. |
| 8gb DDR3 1666mHz | 1TB 7200 RPM WD HDD.|
Unix´s guru view of sex:
unzip ; strip ; touch ; grep ; finger ; \
mount ; fsck ; more ; yes ; umount ; sleep. |
|
Back to top |
|
|
Rede n00b
Joined: 03 Jun 2007 Posts: 67
|
Posted: Thu Oct 02, 2008 3:55 am Post subject: |
|
|
Output of ifconfig -a
Code: |
eth0 Link encap:Ethernet HWaddr 00:1f:c6:43:5a:05
inet addr:192.168.1.3 Bcast:255.255.255.255 Mask:255.255.255.0
inet6 addr: fe80::21f:c6ff:fe43:5a05/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:86313 errors:0 dropped:0 overruns:0 frame:0
TX packets:60869 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:122536252 (116.8 MiB) TX bytes:5922745 (5.6 MiB)
Interrupt:18
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:31 errors:0 dropped:0 overruns:0 frame:0
TX packets:31 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:954 (954.0 B) TX bytes:954 (954.0 B)
|
There is nothing in my /etc/resolve.conf file other then comments.
Well after killing it and rerunning it. I get the same output exactly but now I can connect to the internet
Beforehand I could connect to the other computers on my network. |
|
Back to top |
|
|
ZeuZ_NG Guru
Joined: 10 Sep 2008 Posts: 453 Location: Near /dev/urandom | /dev/null
|
Posted: Thu Oct 02, 2008 3:58 am Post subject: |
|
|
Well, first of all just to clear it was not a typo: it's /etc/resolv.conf
And then, if you can ping hosts in your network, or even the router, but can't get out to the internet, you're lacking to have your nameserver located in /etc/resolv.conf
The syntax of resolv.conf is single:
nameserver XXX.XXX.XXX.XXX
One entry per DNS server, and replace XXX.XXX.XXX.XXX with the corresponding data _________________ | Intel Core i7 920. | Intel DX58SO Extreme. |
| 8gb DDR3 1666mHz | 1TB 7200 RPM WD HDD.|
Unix´s guru view of sex:
unzip ; strip ; touch ; grep ; finger ; \
mount ; fsck ; more ; yes ; umount ; sleep. |
|
Back to top |
|
|
Rede n00b
Joined: 03 Jun 2007 Posts: 67
|
Posted: Thu Oct 02, 2008 4:27 am Post subject: |
|
|
Sorry was a typo on my behalf. It was not there before but after rerunning dhcpcd eth0 I believe it added it.
I am not sure if I will have to kill it and restart it each time I log in though. I am going to restart now. Hopefully not as that will be quite annoying. |
|
Back to top |
|
|
Rede n00b
Joined: 03 Jun 2007 Posts: 67
|
Posted: Thu Oct 02, 2008 1:54 pm Post subject: |
|
|
Still having this problem. I can do a quick fix by killing it and restarting it. But if any one has found a fix for this please let me know. |
|
Back to top |
|
|
ZeuZ_NG Guru
Joined: 10 Sep 2008 Posts: 453 Location: Near /dev/urandom | /dev/null
|
Posted: Thu Oct 02, 2008 5:44 pm Post subject: |
|
|
What about adding a "sleep 5" to the top of the script? this will deay it's execution, and therefore, allow us to check if it's something not ready when the daemon is issued. _________________ | Intel Core i7 920. | Intel DX58SO Extreme. |
| 8gb DDR3 1666mHz | 1TB 7200 RPM WD HDD.|
Unix´s guru view of sex:
unzip ; strip ; touch ; grep ; finger ; \
mount ; fsck ; more ; yes ; umount ; sleep. |
|
Back to top |
|
|
Rede n00b
Joined: 03 Jun 2007 Posts: 67
|
Posted: Fri Oct 03, 2008 12:37 am Post subject: |
|
|
To what script? |
|
Back to top |
|
|
ZeuZ_NG Guru
Joined: 10 Sep 2008 Posts: 453 Location: Near /dev/urandom | /dev/null
|
Posted: Fri Oct 03, 2008 3:19 am Post subject: |
|
|
to net.eth0 or the one regarding the troublesome part... _________________ | Intel Core i7 920. | Intel DX58SO Extreme. |
| 8gb DDR3 1666mHz | 1TB 7200 RPM WD HDD.|
Unix´s guru view of sex:
unzip ; strip ; touch ; grep ; finger ; \
mount ; fsck ; more ; yes ; umount ; sleep. |
|
Back to top |
|
|
Rede n00b
Joined: 03 Jun 2007 Posts: 67
|
Posted: Fri Oct 03, 2008 3:28 am Post subject: |
|
|
I added "sleep 5" to net.eth0, restarted and the problem still exists.
Would this have anything to do with running dhcpcd-4.0.1? |
|
Back to top |
|
|
jamapii l33t
Joined: 16 Sep 2004 Posts: 637
|
Posted: Sat Oct 04, 2008 1:24 pm Post subject: |
|
|
As we have seen, the problem is that resolv.conf is empty.
I think it will be overwritten on any restart, so this must be prevented or something useful injected.
It also seems that an older version of dhcpcd does not have the problem.
So your options are:
- revert to dhcpcd-3
- (if your nameserver does not change) have a static /etc/resolv.conf, by inserting this at the top of /etc/resolvconf/update.d/libc if you use openresolv Code: | exit # keep this line on dispatch-conf, or DNS resolution will fail! |
- (if your nameserver does not change) put the line in /etc/conf.d/net Code: | dns_servers_eth0=( "probably your router" ) |
|
|
Back to top |
|
|
psyic n00b
Joined: 18 Nov 2007 Posts: 3
|
Posted: Mon Oct 20, 2008 6:50 pm Post subject: |
|
|
I am having essentially the exact same problem, except I am running dhcpcd 4.0.2.
I have to kill -9 the pid of dhcpcd running and then renew the lease on eth0 to get it to work at all past a fresh reboot.
Cheers |
|
Back to top |
|
|
logginski n00b
Joined: 21 Oct 2008 Posts: 1
|
Posted: Tue Oct 21, 2008 2:52 am Post subject: |
|
|
I am having exactly teh same problem.
Its caused by dhcpcd when it tries to get a new lease. It overwrites /etc/resolv.conf even if it gets no DNS info. This kills the DNS I got via pppoe.
I regard this as a bug, or at least as a optional feature, to turn dhcpcd in a state where it will only overwrite (better: append) /etc/resolv.conf if it gets an actual DNS server.
*Please* someone, could you help me? Its a laptop and it travels a lot between home, working app., and different work grounds. |
|
Back to top |
|
|
tylerwylie Guru
Joined: 19 Sep 2004 Posts: 458 Location: /US/Georgia/Atlanta
|
Posted: Tue Oct 21, 2008 2:55 am Post subject: |
|
|
Do you have nodns specified in your network configuration file? |
|
Back to top |
|
|
|