Re: Strange behaviour from 0.5.1 and 2006-02-21 cvs

[Dan Williams <dcbw redhat com>]

On Thu, 2006-03-02 at 07:20 -0400, Ian Campbell wrote:
> > Same configuration, same problem. It appears to be a problem with
> > wpa_supplicant; it is not associating with the AP. I'll try to get a log
> > sometime tomorrow, but the basic problem is that wpa_supplicant just
> > gets to "Trying 0C:0A:......" (the AP). I'm running the (in)famous
> > broadcom/ndiswrapper/Gentoo configuration; I've tried with NM CVS as of
> > yesterday; I haven't tried the new patches that have just got posted
> > though.
> 
> Whoops, I meant for that to go to the list.
> 
> I don't think this is the same problem, since my card *can* associate with the
> network. Until I eventually give up out of frustration and click cancel on the
> wep key prompt, I can use the network perfectly fine, ping etc. I'm also
> having the same problem with 0.5.1 which is before the wpa_supplicant
> dependency was added (I think)
> 
> I think it's just a communication error somewhere between dhcdbd and NM, but
> I'm not sure where that might be.

Does your dhclient-script have the correct magic to forward DHCP
information back to dhcdbd?

if [ -n "${dhc_dbus}" ]; then
   /bin/dbus-send \
       --system \
       --dest=com.redhat.dhcp \
       --type=method_call \
       /com/redhat/dhcp/$interface \
       com.redhat.dhcp.set \
       'string:'"`env | /bin/egrep -v '^(PATH|SHLVL|_|PWD|dhc_dbus)\='`";
       if (( ( dhc_dbus & 31 ) == 31 )); then
           exit 0;
       fi;
fi;


Dan