Apr 23 2005, 12:37 AM
Post
#1
|
|
|
Group: Members Posts: 46 Joined: 12-April 05 Member No.: 6,861 |
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. |
|
|
|
![]() |
Apr 27 2005, 06:16 AM
Post
#2
|
|
![]() Group: Admin Posts: 3,281 Joined: 29-July 04 From: Cambridge, England Member No.: 4,149 |
QUOTE(Jacknife @ Apr 23 2005, 08:37 AM) 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 |
|
|
|
Apr 30 2005, 06:20 AM
Post
#3
|
|
|
Group: Members Posts: 46 Joined: 12-April 05 Member No.: 6,861 |
QUOTE(speculatrix @ Apr 27 2005, 09:16 AM) have you locked down the wlan AP to specific ethernet MAC addresses? Thanks for responding. I didn't have the AP restricted to known MAC addresses, and didn't have firewalling enabled on the Zaurus. check the settings; this could account. also, have you turned on firewalling on zaurus? do "iptables -L -v". 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. |
|
|
|
Jacknife Bogus Network Connection? Apr 23 2005, 12:37 AM
Ragnorok - I'm having this same problem with a shiny ne... May 4 2005, 10:11 AM
Ragnorok - In case it's relevant, here's what cardc... May 4 2005, 02:43 PM
Ragnorok - The D-Link is just problematic. May be a bogus ... May 4 2005, 04:32 PM
Jacknife Please keep in mind that I'm still new to the ... May 10 2005, 01:10 AM![]() ![]() |
|
Lo-Fi Version | Time is now: 19th June 2013 - 08:11 PM |