On Thursday 05 February 2009, Dylan Semler wrote: > On Wed, Feb 4, 2009 at 7:47 AM, Al Johnson <openm...@mazikeen.demon.co.uk>wrote: > > I often get the above even with a working wpa_supplicant.conf because the > > dhcp > > discover starts being sent immediately, not after association, so dhcp > > times > > out before association is complete. Bringing the interface down then > > immediately up again will often get association faster, so the last dhcp > > request succeeds. > > Do you mean, after SetResourcePolicy WiFi enabled, you can do ifdown eth0, > ifup eth0, and it works? Or do you cycle the SetResourcePolicy WiFi? > Neither seems to work for me.
I've been looking at this on recent SHR which I think is largely similar to MS5, but it's possible there are differences in this area. 'SetResourcePolicy WiFi enabled' tells FSO to power up the WiFi irrespective of whether any apps have issued 'RequestResource WiFi'. Before I do this I have no eth0 available. To get dhcp working I would often have to do: ifup eth0 ifdown eth0 ifup eth0 On the second ifup the association often completes a little quicker so dhcp has a chance of completing before timeout. Another method is to manually start dhcp after the first ifup using something like: udhcpc -i eth0 This assumes wpa_supplicant is making the association fine. You can check that with wpa_cli which accepts a 'help' command to tell you what other options it has. This has worked for me on everything I've tried since 2007.2, but I've not tried it on the recent SHR or MS5 yet. SHR, and probably MS5, have the added complication of connman running. This tries to manage the network connections, but at least for usb0 it is overridden by the ifup and ifdown commands. Assuming connman actually works, the other option would be to use the connman dbus interface to set the network parameters. Don't ask me how though ;-) _______________________________________________ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
