dhcpcd doesn't hook and pacman wild

inXistant · 2008-04-23 15:52:01

Hi all,

My install has been finished for a time now but I wanted to ask this:

1) During the installation, when trying to connect to the net with dhcpcd, my router proposed an address but dhcpcd did not hook. I had to use -d (debug/verbose) to see it and connect with the -r (request option). Did I do something wrong or there is a bug?

2) Pacman doesn't take wild cards i.e. '*' ? If not it makes it tedious is some app has many optional sub-packages.

Thanks,

inXistant · 2008-04-23 16:23:25

More info on dhcpcd -- it is griberish to me, don't know more about networks...:

info, wlan0: dhcpcd 3.2.1 starting
info, wlan0: hardware address = 00:1a:73:f2:7a:d1
info, wlan0: broadcasting for a lease
debug, wlan0: sending DHCP_DISCOVER with xid 0x5e054a01
debug, wlan0: waiting on select for 20 seconds
debug, wlan0: got a packet with xid 0x5e054a01
info, wlan0: offered 192.168.1.110 from 192.168.1.1
debug, wlan0: sending DHCP_REQUEST with xid 0x5e054a01
debug, wlan0: waiting on select for 19 seconds
debug, wlan0: sending DHCP_REQUEST with xid 0x5e054a01
debug, wlan0: sending DHCP_REQUEST with xid 0x5e054a01
debug, wlan0: sending DHCP_REQUEST with xid 0x5e054a01
debug, wlan0: sending DHCP_REQUEST with xid 0x5e054a01
debug, wlan0: sending DHCP_REQUEST with xid 0x5e054a01
debug, wlan0: sending DHCP_REQUEST with xid 0x5e054a01
err, wlan0: timed out
info, wlan0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-wlan0.info'
err, wlan0: lease expired 424216 seconds ago
info, wlan0: probing for an IPV4LL address
debug, wlan0: sending ARP probe #1
debug, wlan0: sending ARP probe #2
debug, wlan0: sending ARP probe #3
debug, wlan0: sending ARP claim #1
debug, wlan0: sending ARP claim #2
warn, wlan0: using IPV4LL address 169.254.216.103
info, wlan0: adding IP address 169.254.216.103/16
debug, wlan0: no dns information to write
debug, wlan0: writing /var/lib/dhcpcd/dhcpcd-wlan0.info
debug, wlan0: forking to background

I'm using dhclient now and have no problems...

ybotspawn · 2008-04-23 17:51:18

Well it certainly seems that your dhcp router didn't report back an IP at all. what happens when you try getting a wired address using dhcpcd? Can you give that a go and post the results?

inXistant · 2008-04-23 18:28:53

Isn't

offered 192.168.1.110 from 192.168.1.

Is an offer from the router? I'm not sure I'm following but note that it works with dhclient... Anyway, here are the result from the wired:

info, eth0: dhcpcd 3.2.1 starting
info, eth0: hardware address = 00:1e:68:0a:22:cb
info, eth0: broadcasting for a lease
debug, eth0: sending DHCP_DISCOVER with xid 0x3d97d58a
debug, eth0: waiting on select for 20 seconds
debug, eth0: got a packet with xid 0x3d97d58a
info, eth0: offered 192.168.1.104 from 192.168.1.1
debug, eth0: sending DHCP_REQUEST with xid 0x3d97d58a
debug, eth0: waiting on select for 19 seconds
debug, eth0: sending DHCP_REQUEST with xid 0x3d97d58a
debug, eth0: sending DHCP_REQUEST with xid 0x3d97d58a
debug, eth0: sending DHCP_REQUEST with xid 0x3d97d58a
debug, eth0: sending DHCP_REQUEST with xid 0x3d97d58a
debug, eth0: sending DHCP_REQUEST with xid 0x3d97d58a
debug, eth0: sending DHCP_REQUEST with xid 0x3d97d58a
err, eth0: timed out
info, eth0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-eth0.info'
debug, eth0: sending ARP probe #1
debug, eth0: sending ARP probe #2
debug, eth0: sending ARP probe #3
debug, eth0: sending ARP claim #1
debug, eth0: sending ARP claim #2
warn, eth0: using IPV4LL address 169.254.200.16
info, eth0: adding IP address 169.254.200.16/16
debug, eth0: no dns information to write
debug, eth0: forking to background

Pretty much the same thing...

tomk · 2008-04-23 18:38:35

2) See man pacman for your search options, and any other pacman details. You can use regexp in searches, and you can also pipe the output through grep if you wish.

ybotspawn · 2008-04-23 18:49:57

hmmm missed that part... apologies... just to be sure but you're running this as root right? Sounds like a dumb question but anyway... So dhclient works... but not dhcpcd. What is the ip address u get when you use dhclient?

inXistant · 2008-04-23 18:50:02

For 2), yes, I saw that. But my question was much more about issuing

pacman -Sy packa*

to install all packages starting by the string 'packa' and it seems that the answer is 'no'.

Thanks anyway!

inXistant · 2008-04-23 18:52:52

ybotspawn wrote:

hmmm missed that part... apologies... just to be sure but you're running this as root right? Sounds like a dumb question but anyway... So dhclient works... but not dhcpcd. What is the ip address u get when you use dhclient?

yes, running this as root. It is DHCP so any address that is proposed by the router si of the form 192.168.1.* where '*' ranges from 100 to 110 typically. Mh... Perhaps I should file a bug.

phrakture · 2008-04-23 19:27:03

inXistant wrote:

For 2), yes, I saw that. But my question was much more about issuing
pacman -Sy packa*
to install all packages starting by the string 'packa' and it seems that the answer is 'no'.
Thanks anyway!

Installing packages by wildcards makes no sense (this would allow someone to "pacman -S *" which is a terrible idea). We have package "groups" which cover this base well enough, and as we intend it. Take a look at the output of "pacman -Sg"

inXistant · 2008-04-23 19:41:08

phrakture wrote:

Installing packages by wildcards makes no sense (this would allow someone to "pacman -S *" which is a terrible idea). We have package "groups" which cover this base well enough, and as we intend it. Take a look at the output of "pacman -Sg"

Arf! Thats write that "pacman -S *" would be no fun! But thanks for the cue about '-Sg', this is great! I even found what I was searching for.

TheBodziO · 2008-04-23 21:11:23

inXistant wrote:

Isn't
offered 192.168.1.110 from 192.168.1.1
Is an offer from the router? I'm not sure I'm following but note that it works with dhclient... Anyway, here are the result from the wired:

<cut />

Seems like it to me, as long as your dhcp server has the ip 192.168.1.1.

inXistant wrote:

Pretty much the same thing...

Could you maybe post dhcpcd parameters that you've used and a fragment of /var/log/everything.log after running dhcpcd? Perhaps this will help to solve your problem. I think that we should refrain from filing a bug before more detailed investigation.

Also… if you don't have time (or will) to deal with the situation (AFAICU it's an installation issue only) you can also set and use static ip as long as there are no other hosts using the same ip in your lan. In your case I assume correct setting should be: 192.168.1.110, netmask 255.255.255.0. It should work just as good as getting the ip via dhcp.

inXistant · 2008-04-23 21:44:16

TheBodziO wrote:

Could you maybe post dhcpcd parameters that you've used and a fragment of /var/log/everything.log after running dhcpcd? Perhaps this will help to solve your problem. I think that we should refrain from filing a bug before more detailed investigation.
Also… if you don't have time (or will) to deal with the situation (AFAICU it's an installation issue only) you can also set and use static ip as long as there are no other hosts using the same ip in your lan. In your case I assume correct setting should be: 192.168.1.110, netmask 255.255.255.0. It should work just as good as getting the ip via dhcp.

I think it is important to deal with the situation as if somebody else runs in it, he can find relevant info to solve it which is important *especially* during the installation process... Here is the tail of the log concerning the last use of dhcpcd:

Apr 23 17:40:12 komuso dhcpcd[7158]: wlan0: dhcpcd 3.2.1 starting
Apr 23 17:40:12 komuso dhcpcd[7158]: wlan0: hardware address = 00:1a:73:f2:7a:d1
Apr 23 17:40:12 komuso dhcpcd[7158]: wlan0: broadcasting for a lease
Apr 23 17:40:12 komuso dhcpcd[7158]: wlan0: sending DHCP_DISCOVER with xid 0x2ec0bcba
Apr 23 17:40:12 komuso dhcpcd[7158]: wlan0: waiting on select for 20 seconds
Apr 23 17:40:13 komuso dhcpcd[7158]: wlan0: got a packet with xid 0x2ec0bcba
Apr 23 17:40:13 komuso dhcpcd[7158]: wlan0: offered 192.168.1.110 from 192.168.1.1
Apr 23 17:40:13 komuso dhcpcd[7158]: wlan0: sending DHCP_REQUEST with xid 0x2ec0bcba
Apr 23 17:40:13 komuso dhcpcd[7158]: wlan0: waiting on select for 19 seconds
Apr 23 17:40:16 komuso dhcpcd[7158]: wlan0: sending DHCP_REQUEST with xid 0x2ec0bcba
Apr 23 17:40:19 komuso dhcpcd[7158]: wlan0: sending DHCP_REQUEST with xid 0x2ec0bcba
Apr 23 17:40:22 komuso dhcpcd[7158]: wlan0: sending DHCP_REQUEST with xid 0x2ec0bcba
Apr 23 17:40:25 komuso dhcpcd[7158]: wlan0: sending DHCP_REQUEST with xid 0x2ec0bcba
Apr 23 17:40:28 komuso dhcpcd[7158]: wlan0: sending DHCP_REQUEST with xid 0x2ec0bcba
Apr 23 17:40:31 komuso dhcpcd[7158]: wlan0: sending DHCP_REQUEST with xid 0x2ec0bcba
Apr 23 17:40:32 komuso dhcpcd[7158]: wlan0: timed out
Apr 23 17:40:32 komuso dhcpcd[7158]: wlan0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-wlan0.info'
Apr 23 17:40:32 komuso dhcpcd[7158]: wlan0: probing for an IPV4LL address
Apr 23 17:40:32 komuso dhcpcd[7158]: wlan0: sending ARP probe #1
Apr 23 17:40:33 komuso dhcpcd[7158]: wlan0: sending ARP probe #2
Apr 23 17:40:33 komuso dhcpcd[7158]: wlan0: sending ARP probe #3
Apr 23 17:40:33 komuso dhcpcd[7158]: wlan0: sending ARP claim #1
Apr 23 17:40:33 komuso dhcpcd[7158]: wlan0: sending ARP claim #2
Apr 23 21:40:34 komuso avahi-daemon[5832]: Joining mDNS multicast group on interface wlan0.IPv4 with address 169.254.53.209.
Apr 23 17:40:34 komuso dhcpcd[7158]: wlan0: using IPV4LL address 169.254.53.209
Apr 23 17:40:34 komuso dhcpcd[7158]: wlan0: adding IP address 169.254.53.209/16
Apr 23 21:40:34 komuso avahi-daemon[5832]: New relevant interface wlan0.IPv4 for mDNS.
Apr 23 21:40:34 komuso avahi-daemon[5832]: Registering new address record for 169.254.53.209 on wlan0.IPv4.
Apr 23 17:40:34 komuso dhcpcd[7158]: wlan0: no dns information to write
Apr 23 17:40:34 komuso dhcpcd[7158]: wlan0: writing /var/lib/dhcpcd/dhcpcd-wlan0.info
Apr 23 17:40:34 komuso dhcpcd[7158]: wlan0: forking to background
Apr 23 17:40:34 komuso dhcpcd[7158]: wlan0: exiting
Apr 23 17:40:34 komuso dhcpcd[7178]: wlan0: waiting on select for 10 seconds

phrakture · 2008-04-23 21:53:06

inXistant wrote:

Apr 23 21:40:34 komuso avahi-daemon[5832]: Joining mDNS multicast group on interface wlan0.IPv4 with address 169.254.53.209.
Apr 23 21:40:34 komuso avahi-daemon[5832]: New relevant interface wlan0.IPv4 for mDNS.
Apr 23 21:40:34 komuso avahi-daemon[5832]: Registering new address record for 169.254.53.209 on wlan0.IPv4.

avahi-daemon is doing this.

inXistant · 2008-04-23 22:13:04

Avahi was not installed when I just finished installing the system... To install the packages, one needs to be connected. I had to use dhcpcd -d and then dhcpcd -r 192.186.1.* to hook to the address proposed I saw with '-d'.

Last edited by inXistant (2008-04-23 22:14:26)

TheBodziO · 2008-04-23 23:11:36

inXistant wrote:

Avahi was not installed when I just finished installing the system... To install the packages, one needs to be connected. I had to use dhcpcd -d and then dhcpcd -r 192.186.1.* to hook to the address proposed I saw with '-d'.

I'm assuming that you've used following sentence of commands:

dhcpcd -d wlan0
dhcpcd -r 192.168.1.* wlan0

It appears that the problem could be within your dhcp server. Could you kindly check if the following code assings ip properly:

dhcpd -d wlan0 && dhcpcd -d wlan0

or

dhcpd -S wlan0

on some other implementations. The thing is that some dhcp servers wants you to send DHCP_DISCOVER twice even if they've send DHCP_OFFER. Only then they'll reply to DHCP_REQUEST. It seems that this is the case here as you've received DHCP_OFFER ("Apr 23 17:40:13 komuso dhcpcd[7158]: wlan0: offered 192.168.1.110 from 192.168.1.1") but never received reply for DHCP_REQUEST ("Apr 23 17:40:32 komuso dhcpcd[7158]: wlan0: timed out"). You've also said that you've got the ip properly configured after issuing dhcpcd command twice which is what is done in the above code proposed by me. If it'll work we've got both cause and solution.

I hope this will get rid of your problem!

Last edited by TheBodziO (2008-04-23 23:13:20)

Arch Linux

#1 2008-04-23 15:52:01

dhcpcd doesn't hook and pacman wild

#2 2008-04-23 16:23:25

Re: dhcpcd doesn't hook and pacman wild

#3 2008-04-23 17:51:18

Re: dhcpcd doesn't hook and pacman wild

#4 2008-04-23 18:28:53

Re: dhcpcd doesn't hook and pacman wild

#5 2008-04-23 18:38:35

Re: dhcpcd doesn't hook and pacman wild

#6 2008-04-23 18:49:57

Re: dhcpcd doesn't hook and pacman wild

#7 2008-04-23 18:50:02

Re: dhcpcd doesn't hook and pacman wild

#8 2008-04-23 18:52:52

Re: dhcpcd doesn't hook and pacman wild

#9 2008-04-23 19:27:03

Re: dhcpcd doesn't hook and pacman wild

#10 2008-04-23 19:41:08

Re: dhcpcd doesn't hook and pacman wild

#11 2008-04-23 21:11:23

Re: dhcpcd doesn't hook and pacman wild

#12 2008-04-23 21:44:16

Re: dhcpcd doesn't hook and pacman wild

#13 2008-04-23 21:53:06

Re: dhcpcd doesn't hook and pacman wild

#14 2008-04-23 22:13:04

Re: dhcpcd doesn't hook and pacman wild

#15 2008-04-23 23:11:36

Re: dhcpcd doesn't hook and pacman wild

Board footer