64-Bit Wireless Help

hi everyone,

right off the bat I should let everyone know I'm very new to linux. I couldn't stand Pindows anymore, so I am finding Suse to be my laptop OS alternative.

So far, isntallation has been fine for most of my hardware, except for wireless.

I've been following the instructions for ndiswrapper given here: 64-Bit Wireless Suse 9.1 wiki

I've followed the instructions right to the end, everything has been going off without a hitch. But when I try to ping my router, I get:

connect: Network is unreachable

.

2 things I haven't down though... get my wireless card to pick up my router via DHCP. I am unsure of how to do that.

I also didn't edit the /etc/sysconfig/network/ifcfg-wlan0 file because it's not there when I look for it.

I haven't installed the card via YaST either because it's not picking it up, unless I'm no install it manually?

I set my essid, but that's about it.

Am I missing any steps here? Any help would be appricated, thank you very much.

Hi,
If you are unsure about editing files when setting up ndiswrapper then there's an easier walkthrough to follow. Take a peak at this: http://nextgen.no-ip.org/~andrew/linux/ndi...wrapperinfo.php

The only thing it doesn't cover is setting the card up in Yast and as a rule I follow this set of guidelines:
Yast - Network Devices - Network Card - Add. On the screen that follows:
Device Type: Wireless
Configuration Name: 0
Hardware Configuration Name: static-1 (This is there by default)
Module Name: ndiswrapper

Then left USB & PCMCIA unchecked and options blank.

On the next screen the only thing I altered was: Advanced - Detailed Settings - Device Activation, and changed this to 'At boot time'. I also edited the same setting for thevethernet adapter(and any others) and set this to 'Never', but you can set these to use different adapters depending which one is plugged in at the time, from what I've read it works really well in 9.3 but I don't use the ethernet so this suits me just fine.

On the following screen I entered the essid, mode and WEP key but as you are not using any encryption just the essid and mode will do.

The card should then be configured.

Let us know how you get on.

OH MY GOODNESS!

IT WORKED! Thank you Weaner!

Let my linux experiment begin!


Oh just one thing, when I reboot my computer, the wireless card tries to connect to connect to my neighbours wireless network by default. How can I make it automatically connect to my wireless network when I reboot my computer?

What are the names of your and your neighbours essid?

Originally posted by weaner@Sep 27 2005, 10:21 PM
What are the names of your and your neighbours essid?

[snapback]93047[/snapback]

my essid is "wlnet"
the other's that are being listed are:
BEACHCOMBER
default
StikiNet

When you configured the card in Yast did you set the essid there? It might be worth having a look there to see if the essid is still 'wlnet'
Network Devices - Network Card, then highligtht the wlan0 entry then edit and choose next until you get the essid config screen.

Originally posted by weaner@Sep 28 2005, 12:03 AM
When you configured the card in Yast did you set the essid there? It might be worth having a look there to see if the essid is still 'wlnet'
Network Devices - Network Card, then highligtht the wlan0 entry then edit and choose next until you get the essid config screen.

[snapback]93059[/snapback]

Yes the ESSID in YaST is wlnet.

BTW, I have to select which network to connect to in KInternet - InternetTool when I boot my computer. Just thought I would throw that in.

Originally posted by mcrexx@Sep 28 2005, 04:49 AM
Yes the ESSID in YaST is wlnet.

BTW, I have to select which network to connect to in KInternet - InternetTool when I boot my computer. Just thought I would throw that in.

[snapback]93062[/snapback]

That was my next question
I'm certain Kinternet is at fault here, right click the Kinternet icon and choose close. A pop-up should appear asking you if you want Kinternet to start when you next boot the computer (or something like that) - choose no and restart.
Hopefully it will ignore Kinternets settings and you can check that you are connected to the right access point with:
Open a console and as root,
iwconfig

Look at the output for wlan0.

You know what, after a reboot, KInternet is actually acting perfectly!

OK, my next question is, how do I enable WEP security? I had it off before just so I get get the wireless to work. Now that it does, how can I get WEP security enabled on my wireless connection?

In YaST am I to enter the Passphrase or KEY 1?

Originally posted by mcrexx@Sep 29 2005, 02:30 AM
You know what, after a reboot, KInternet is actually acting perfectly!

OK, my next question is, how do I enable WEP security? I had it off before just so I get get the wireless to work. Now that it does, how can I get WEP security enabled on my wireless connection?

In YaST am I to enter the Passphrase or KEY 1?

[snapback]93157[/snapback]

Glad to hear it's behaving as it should.
Just enter the WEP key in the box under passphrase then choose what kind of key it is and check the box, if you're using multiple keys you can assign them by clicking the 'WEP keys' icon, you'll also notice that the one you entered in the box is WEP key 0.
(This might be a little bit different for you as I'm using Super Suse and can't remember what 9.3's configure screen looked like)