Openmoko Bug #1904: om2008.8 wifi don't get always an ipv4 ip
Openmoko Public Trac
bugs at docs.openmoko.org
Tue Sep 16 21:52:17 CEST 2008
#1904: om2008.8 wifi don't get always an ipv4 ip
------------------------+---------------------------------------------------
Reporter: dolfje | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
------------------------+---------------------------------------------------
Comment(by danielhedblom):
Replying to [comment:17 andy]:
> Can you define a simple test that shows it, which is easily repeatable,
then?
On my phone a simple test is to just try to get packets out over wifi.
Since the high packetloss makes getting a DHCP conversation trough very
hard i recommend setting a static ip.
>
> For example, just pinging something on local network at one packet a
second shows high packetloss? Or we need to do bulk transfer?
Set the AP as an open system and try to ping it. Also try to ping the FR
from another computer on the same wired network as the AP. The packetloss
is very high, sometimes 100%.
The thing that strikes me as rather strange is this output from ifconfig
after trying to unsuccessfully ping my AP:
eth0 Link encap:Ethernet HWaddr 00:12:CF:8E:FC:12
inet addr:192.168.1.66 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::212:cfff:fe8e:fc12/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:3103 errors:0 dropped:0 overruns:0 frame:0
TX packets:758 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1430550 (1.3 MiB) TX bytes:32423 (31.6 KiB)
The packets are registered but somewhere sent to the bitbucket.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1904#comment:18>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
More information about the devel
mailing list