You are not logged in.
Pages: 1
Hello, whenever I acquire my network information from my ISP I get the following output:
:: Starting Network [BUSY]
eth0: wrong state 9
Everything works, but it's a tad annoying and I haven't been successful in finding out more information about it.
Anyone know what this means? Or how to find out what state 9 is? And possibly fix it.
My interface for the connection is simply:
eth0="dhcp"
INTERFACES=(eth0)
and I use dhcpd.
Regards,
vesz
Offline
Offline
This is an output you required:
bash-3.2# killall dhcpcd
bash-3.2# dhcpcd eth0
eth0: dhcpcd 4.0.10 starting
eth0: broadcasting for a lease
eth0: offered 192.168.44.76 from 192.168.0.4
eth0: ignoring offer of 192.168.44.76 from 192.168.0.6
eth0: acknowledged 192.168.44.76 from 192.168.0.4
eth0: checking 192.168.44.76 is available on attached networks
eth0: wrong state 9
eth0: checking 192.168.44.76 is available on attached networks
eth0: leased 192.168.44.76 for 86400 seconds
Offline
And with the debug flag '-d' on dhcpcd:
eth0: dhcpcd 4.0.10 starting
eth0: hardware address = 00:xx:xx:xx:xx:xx
eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT
eth0: broadcasting for a lease
eth0: sending DHCP_DISCOVER with xid 0x7df1487f, next in 3.69 seconds
eth0: offered 193.xx.xx.108 from 193.xx.xx.2
eth0: sending DHCP_REQUEST with xid 0x7df1487f, next in 4.36 seconds
eth0: acknowledged 193.xx.xx.108 from 193.xx.xx.2
eth0: checking 193.11.251.108 is available on attached networks
eth0: sending ARP probe (1 of 3), next in 1.73 seconds
eth0: ignoring offer of 193.xx.xx.108 from 193.xx.xx.3
eth0: wrong state 9
eth0: checking 193.xx.xx.108 is available on attached networks
eth0: sending ARP probe (1 of 3), next in 1.33 seconds
eth0: sending ARP probe (2 of 3), next in 1.73 seconds
eth0: sending ARP probe (3 of 3), next in 2.00 seconds
eth0: leased 193.xx.xx.108 for 18000 seconds
eth0: adding IP address 193.xx.xx.108/24
eth0: adding route to 0.0.0.0/0 via 193.xx.xx.1
eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason BOUND
eth0: forking to background
Seems dhcpcd has an added feature 'acquired taste'. My IP-address doesn't look so bad the second time it comes around :)
ARP probes got to do with IP Conflict Detection, seems the IP is not properly released at some point. Someone tried waiting for the lease to expire and see if they still get the wrong state 9?
Looks harmless enough that I won't worry about it and see if it goes away with the next dhcpcd update.
Note: I know nothing! Just speculation :)
Last edited by vesz (2009-02-18 19:31:22)
Offline
Same problem here -- its harmless enough, but adds a fair few seconds onto my boot time
Offline
(I was about to post a new topic but I think I have the same problem
Hi
Since yesterday I can't connect to the internet on Archlinux (but it works on Windows).
I tried both network-manager and netcfg, bith didn't work.
netcfg tell me "DHCP lease attempt failed" (or something like this).
Here's my 'dhcbd -d' output:
eth0: broadcasting for a lease
eth0: sending DHCP_DISCOVER with xid 0x3be1c24d, next in 4.01 seconds
eth0: offered 10.133.11.14 from 10.4.1.18
eth0: sending DHCP_REQUEST with xid 0x3be1c24d, next in 4.79 seconds
eth0: ignoring offer of 10.133.11.14 from 10.4.1.21
eth0: acknowledged 10.133.11.14 from 10.4.1.18
eth0: checking 10.133.11.14 is available on attached networks
eth0: sending ARP probe (1 of 3), next in 1.51 seconds
eth0: wrong state 9
eth0: checking 10.133.11.14 is available on attached networks
eth0: sending ARP probe (1 of 3), next in 1.18 seconds
eth0: ignoring offer of 192.168.0.235 from 10.100.0.1
eth0: NAK: (null) from 10.100.0.1
(it keeps tell me this again and again)
What I can I do? Is it a known bug?
it's a big problem for me to not have internet so please give me a hand .
Thanks
Edit:
Wow, I didn't do anything and it works now... what a weird problem .
Last edited by zakora (2009-02-26 13:52:01)
Offline
Just wanted to mention I have the same problem. No idea what state 9 is. dhcpcd seems to work just fine after boot, no unusual errors from running it with -d.
Offline
I get the same error, has anyone figured this out yet? It keeps arch assistant from working. Not to hard to do things manually, but it would be a nice fix.
Offline
I had the same problem. Although I got an IP I wasnt able to ping any addresses afterwards. I killed the dhcpcd and ran dhclient eth1 instead. Worked like a charm
Offline
I have the same problem wth the RaLink wireless card in my MSI Wind. Everything works, but sometimes when I try to connect with netcfg/wpa_supplicant it will show wrong stare: error 9. However it will still connect
Offline
I have an Aspire One, and I also get that message! Yet I have no problems with access to the internet.
Offline
I have noticed a similar problem while using virtualbox, dhcpcd can get everything right except the dns servers, dhclient works fine.
Although I think this is a vbox problem as there are reports about this it is still curious that dhclient works fine when dhcpcd doesn't.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Huh? I just connected my computer on my home network, and I did not get that error message. So, it happens only on my work network =\
Offline
Pages: 1