Bogus Network Connection?, Zaurus Connects - but doesn't? Options

[Jacknife]

I'm able to connect to my WAP with 100% signal strength/quality, but am not able to see the Zaurus from my network nor the network from my Zaurus. I've never seen an issue like this before, and I'm kind of at a loss. I'm hoping that someone has seen this type of issue before and found a way to fix it.

Anyway, here's some network configuration dumps from both my Zaurus and Linux desktop:

Zaurus:

CODE

home/zaurus>/sbin/route;/sbin/route -n;/sbin/ifconfig
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     0      0        0 wlan0
default         192.168.1.1     0.0.0.0         UG    1      0        0 wlan0
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 wlan0
0.0.0.0         192.168.1.1     0.0.0.0         UG    1      0        0 wlan0
lo        Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:848 errors:0 dropped:0 overruns:0 frame:0
         TX packets:848 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:89821 (87.7 Kb)  TX bytes:89821 (87.7 Kb)

wlan0     Link encap:Ethernet  HWaddr 00:10:7A:58:C9:D9
         inet addr:192.168.1.104  Bcast:192.168.1.255  Mask:255.255.255.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:100
         RX bytes:0 (0.0 b)  TX bytes:864 (864.0 b)
         Interrupt:135

Work station:

CODE

/home/jacknife>/sbin/route;/sbin/route -n;/sbin/ifconfig
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0
169.254.0.0     *               255.255.0.0     U     0      0        0 eth0
127.0.0.0       *               255.0.0.0       U     0      0        0 lo
default         router          0.0.0.0         UG    0      0        0 eth0
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
eth0      Link encap:Ethernet  HWaddr 00:A0:C9:A5:DD:BB  
         inet addr:192.168.1.111  Bcast:192.168.1.255  Mask:255.255.255.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:463174 errors:0 dropped:0 overruns:0 frame:0
         TX packets:1935924 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:100
         RX bytes:86686511 (82.6 Mb)  TX bytes:266125014 (253.7 Mb)
         Interrupt:9 Base address:0xccc0 Memory:f7000000-f7000038

lo        Link encap:Local Loopback  
         inet addr:127.0.0.1  Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:68549 errors:0 dropped:0 overruns:0 frame:0
         TX packets:68549 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:16182631 (15.4 Mb)  TX bytes:16182631 (15.4 Mb)

I know that at least my WAP can see the Zaurus connecting, because there is an entry in the logs with the connect time and MAC addresss. Despite this fact, I'm not able to ping the WAP from my Zaurus.

[speculatrix]

I'm able to connect to my WAP with 100% signal strength/quality, but am not able to see the

have you locked down the wlan AP to specific ethernet MAC addresses?

check the settings; this could account.

also, have you turned on firewalling on zaurus? do "iptables -L -v".

Paul

[Jacknife]

have you locked down the wlan AP to specific ethernet MAC addresses?

check the settings; this could account.

also, have you turned on firewalling on zaurus? do "iptables -L -v".

Thanks for responding. I didn't have the AP restricted to known MAC addresses, and didn't have firewalling enabled on the Zaurus.

Since my original posting, I've spent multiple hours reviewing various configuration settings on the Zaurus as well as testing the CF wireless card in other devices. To make a very long story short, I tracked the problem down to a bug in the WEP keys on the Zaurus. I also had to change my AP's authentication type from supporting both Open System and Shared Key to just the Open System option.

I have the feeling that WEP won't work with my Zaurus until I flash it with the newer ROM (currently running v1.00 on the SL-C3000). However I'm new to the Zaurii and am concerned about "bricking" it on a bad flash attempt. I've been trying to follow the ROM related threads and become intimate/comfortable with the flashing process.

Anyway, I hope that this thread will prove useful to anyone else that may be experiencing a similar issue. I'll post an update once/if I find a way to get WEP working properly on the SL-C3000.

[Ragnorok]

- I'm having this same problem with a shiny new C1000 running the default Sharp ROM (1.1jp, i think, converted to engrish of course) with a DLink DCF-660W. It connectes, it works for about one web page load, maybe two, then it just stops. When that happens, it won't ping anything, not even the WAP. A netstat -a freezes after the third entry, and has to be CTRL-C to stop it or it'll sit there forever. Haven't done routing tables or anything yet.
- If I keep playing, the Z will ultimate "fade to white". Then *entire* screen slowly washes out until everything is full white. If the unit is suspended and the card pulled before it gets to full white, it will recover when turned back on, otherwise the reset button must be employed.
- I also have a somewhat flakey LinkSys WCF12 that behaves in precisely the same manner.
- Serious weirdness. I'll try the things Jacknife suggests and see what that does...

[Ragnorok]

- In case it's relevant, here's what cardctl ident says:
Socket 0:
product info: "D-Link", "DCF-660W", ""
manfid: 0xd601, 0x0005
function: 6 (network)

It doesn't typically work long enough to get a routing table, the one time I got one, it was essentially what Jackknife shows, only 0.1 instead of 1.1. (grin)

[Ragnorok]

- The D-Link is just problematic. May be a bogus card ... it's not consistent in what's wrong each time, except that it often ends in a crash. (smirk) It is properly detected (usually) and has configuration in wlan.conf, but I haven't done a modprobe to see if prism_cs is loaded. It finally just refused to even be recognized as anything but a generic CF card, so I gave up on it.
- The LinkSys works perfectly, until it doesn't. (giggle) Route, netstat, cardctl, ifconfig, iwconfig, all give the same results before it doesn't work, and after. The only difference is that under Network, the SSID is garbulated (looks like a mix of random chars, with some boxes like Japanese chars appear), and the Quality is nothing. Signal is good, and loading the Network to see this crashes the Z.
- Comments? Suggestions? I'd like to have WiFi on this guy...

[Jacknife]

Please keep in mind that I'm still new to the Zaurii, so my comments are only slightly educated guesses... However it sounds like you may have a bad D-Link card. I had an issue where my first Ambicom Wireless Lan card would only work for about a minute before dropping connection. The next day it wouldn't even register with cardctl.

Since the card was less than 3 days old, I took it back to the store and swapped it out for another one of the same model. My new card has been working great with no issues. I still haven't gotten WEP working, but that's not a problem with the card.

The situation you described may aslo be related to a configuration issue. After avoiding the fade to white scenario, have you tried running a dmesg on the Zaurus to see what may have caused the lock?

There is also the possibility that it could be the type/model of wireless card that you're using. It seems like a lot of people are able to use the AmbiCom and AUS cards with little or no issues on the C series.