Wireless Under SuSE 8.1

[kbb0927@cs.com]

David,

I get the beep... beep. I am using a WAP on it's own IP in infra-
structure (managed) mode and the SuSE 8.1 setup GUI asks for a key.
The WAP uses 128 bit WEP key because I am using a mixed wired/wireless
home lan.  This is what I symlinked:  ln -s /etc/sysconfig/network/ifcfg-eth-pcmcia  /etc/sysconfig/network/ifcfg-wlan0. Once I did that ifconfig
showed the correct info about the wireless pcmcia card, including the
set IP. iwconfig shows it as wlan0 but fails to find the WAP, it just
gives 44:44:44:44:44 as the WAP, but this is not it's MAC. 

It is not a big deal as I have a eth0 using e100 for this laptop, but
wanted to use wireless to move about my house with it. It is a dual
boot machine.  SuSE 8.1 insmods the card as yenta_socket but SuSE 8.0
insmods it as i82365, which the card worked wirelessly under SuSE 8.0.
I think I may go back to SuSE 8.0 since it worked. The only reason, I
upgraded to 8.1 was for my Zaurus 5500 PDA, but I have found a way to
sync it using a wireless CF card in it.

What's most frustrating is that given a GUI to set it up and it not
working. Also, no one else has posted any issues, so I have nothing 
to work from to see if it is a SuSE8.1-UnitedLinux thing.

Thanks for your responses, unfortunately, my card does everything you
say it should except, connect to the WAP. I will try again with
no key to see if it takes it that way before I go back to SuSE 8.0

Best Regards,

Keith B.

"David A. Bandel" <david at pananix.com> wrote:

[snip]

>exactly _what_ are you symlinking? ?
>
>When you insert the pcmcia card, you should hear "beep ... beep". ?The
>first beep means cardmanager recognized a card insertion, the second beep
>means the driver has been installed. ?When the driver is installed, you
>will have available either an eth# (eth0, eth1, etc) or a wlan# (wlan0,
>wlan1, etc). ?You just use that.
>
>Your commands for ifconfig and iwconfig use this eth or wlan device as the
>first argument.
>
>You don't have to have a key. ?All will work without it.
>
>If you're running two linux boxes that are talking to each other you must
>use ad-hoc mode. ?If you have an AP you're talking to, you'll probably
>need managed mode.
>
>The rest is per my previous post.
>
>[snip]
>
>Ciao,
>
>David A. Bandel
>-- 
>Focus on the dream, not the competition.
> ? ? ? ?-- Nemesis Racing Team motto
>_______________________________________________
>Linux-users mailing list
>Linux-users at linux-sxs.org
>Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users
>