Re: WLAN connection problems w. static IP

2012-06-04 Thread Radek Polak
On Sunday, June 03, 2012 10:07:56 PM Neil Jerram wrote:

 If my reading of the QtMoko source is correct, QtMoko simply uses
 'udhcpc' to do client-side DHCP.  So what you've described may be a
 known bug with the Debian squeeze version of udhcpc (which is part of
 busybox).
 
 Therefore, you might like to:
 
 - see if you can reproduce the same problem with Debian squeeze udhcpc,
   running independently of QtMoko
 
 - investigate if that problem has since been fixed in busybox upstream
 
 - build and install a modified busybox package that adds that udhcpc
   fix.

Yes and it would be also nice if you could try connect to your router from 
command line. Something like:

iwfconfig essid eth0 your_ap_essid
udhcpc eth0

and you can also try with dhclient:

iwfconfig essid eth0 your_ap_essid
dhclient eth0

Regards

Radek

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: WLAN connection problems w. static IP

2012-06-03 Thread Neil Jerram
Thomas Pantzer tho@pantzer.net writes:

 I can't use DHCP with my home network since my DHCP server
 refuses to send IP address to clients that send too short
 request.  This is another bug in the QtMoko. According to
 the RFC a DHCP-request needs to be padded up to 300 chars.

If my reading of the QtMoko source is correct, QtMoko simply uses
'udhcpc' to do client-side DHCP.  So what you've described may be a
known bug with the Debian squeeze version of udhcpc (which is part of
busybox).

Therefore, you might like to:

- see if you can reproduce the same problem with Debian squeeze udhcpc,
  running independently of QtMoko

- investigate if that problem has since been fixed in busybox upstream

- build and install a modified busybox package that adds that udhcpc
  fix.

Regards,
Neil

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community