Gentoo: Different dhclient?

[Pat Suwalski <pat suwalski net>]

Hello,

I recently installed NetworkManager 0.6.1 (-r2 in Gentoo), and went back
to my Atheros card.

I can't associate with WPA anymore for some reason, but I'll need more
time to figure that out. As fallback, I tried a good old WEP association.

Interestingly, the dhclient usage info showed up in my
/var/log/messages. I replaced the dhclient binary with a script that
catches the arguments, and I got:

-1 -lf /var/lib/dhclient/dhclient-ath0.leases -pf
/var/run/dhclient-ath0.pid -q -e dhc_dbus=31 -x -d ath0

Looking at my dhclient's help, there is no "-x" option. Where is this
from/for?

I made my wrapper script sed-out the -x and call the real dhclient with
the modified parameter list, and I still got funny results:

Apr  9 23:02:04 inspiron NetworkManager: <information>  Activation
(ath0) Stage 3 of 5 (IP Configure Start) complete.
Apr  9 23:02:04 inspiron NetworkManager: <information>  DHCP daemon
state is now 12 (successfully started) for interface ath0
Apr  9 23:02:05 inspiron dhclient: DHCPDISCOVER on ath0 to
255.255.255.255 port 67 interval 4
Apr  9 23:02:05 inspiron dhclient: DHCPOFFER from 120.7.1.1
Apr  9 23:02:05 inspiron dhclient: DHCPREQUEST on ath0 to
255.255.255.255 port 67
Apr  9 23:02:05 inspiron dhclient: DHCPACK from 120.7.1.1
Apr  9 23:02:05 inspiron dhclient: bound to 120.7.1.36 -- renewal in
17617 seconds.
Apr  9 23:02:29 inspiron NetworkManager: <information>  Device 'ath0'
DHCP transaction took too long (>25s), stopping it.
Apr  9 23:02:29 inspiron dhclient: DHCPRELEASE on ath0 to 120.7.1.1 port 67
Apr  9 23:02:30 inspiron NetworkManager: <information>  Activation
(ath0) Stage 4 of 5 (IP Configure Timeout) scheduled...
Apr  9 23:02:30 inspiron NetworkManager: <information>  DHCP daemon
state is now 14 (normal exit) for interface ath0
Apr  9 23:02:30 inspiron NetworkManager: <information>  DHCP daemon
state is now 14 (normal exit) for interface ath0

dhclient gets an IP address immediately, but NetworkManager chooses to
time out anyway. Could this be because of the wrapper script PID not
matching the real dhclient PID or something?

--Pat