Wireless Problems

[Merardon]

I've been unable to connect to the internet yet on my Zaurus 5500, in Opie, with an Ambicom CF card. The same kind a lot of others use. I've run Wellenreiter successfully, but I can't seem to be able to connect to my home network. (I've been too busy to test it out on an open network) It recognizes the card just fine, I can actually start it, but here's where the problems arise. First off, when connected, the speed is sometimes 1 MBPS, sometimes 2, sometimes 11, but it remains constant, and it will vary when I go to connect. The SSID flashes on and off repeatedly, sometimes with a bunch of garbage, and at other times with the SSID followed by a bunch of garbage. Opera won't connect to anything aside from itself.

I'm wondering if this ties into my second problem, which is DSL. I've been unable to locate a method of entering my username and password. I've added a "modem" account properly, attempted to point it to my wireless connection, with no avail. Is there something terribly obvious that I'm missing? I'm at the point of just giving wireless the finger, and I've tried everything I can think of. Any help would be greatly appreciated.

[dino]

I've had a similar problem with a Pretec card.
It takes about 5 minutes for the card to establish a connection.
During this time the light blinks and the channel is changing, but it usually keeps hitting one particular channel longer and more frequent than the others.
I've had the card use the Orinoco and hostap drivers.  The hostap drivers cause the SSID to appear followed by garbage charecters.

[Merardon]

For me, the LED isn't blinking once I tell it to connect, it stays on. Additionally, the channel remains constant. Any advice?

[Merardon]

Nobody has any suggestions to help fix this?

[jnmonteiro]

I use an Ambicon WL-1100C.  I connect to DSL through my wireless router.       I seem to remember disabling all security on my router and then establishing a connection using wlan0.  I believe wifi0 does nothing from the users point of view.  For this I used checked the DHCP and "Automatically Bring Up"  boxes in TCP/IP.

Once you have your unsecure connection working turn on WEP (it seems that 3.5.2 is only able to use WEP 64-bit, I may be wrong).   I had to explicity state my IP address, subnet & gateway in the TCP/IP settings.  Once I restarted the network I had to eject the wireless card, pull it out and reinsert it and my connection worked with WEP.

The extraction & re-insertion of the card probably restarted the interfaces and there may be a nifty script out there that does the same thing, but until I search & find it, this is what I did.

Maybe there is a logical explanatio why all this works.  Check around the newsgroup.