LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   getting wireless lan to work on Slackware 11.0 (http://www.linuxquestions.org/questions/slackware-14/getting-wireless-lan-to-work-on-slackware-11-0-a-573063/)

adityavpratap 07-28-2007 08:42 PM

getting wireless lan to work on Slackware 11.0
 
Hi,
I am trying to get my WA3002-g1 wireless modem/router to work on my Acer Aspire 5100 laptop. It works in Windows.
I have 2.6.17.13 kernel which load bcm43xx by default. I have installed ndiswrapper 1.47. I coppied bcmwl5.inf and bcmwl5.sys from windows onto Slackware and installed them through ndiswrapper.
The out put of ndiswrapper -l is -
Quote:

bcmwl5 : driver installed
device (14E4:4318) present (alternate driver: bcm43xx)
/etc/rc.d/netdevice loads ndiswraper.
Now, I want to know what modifications are to be made to /etc/rc.d/rc.inet1.conf and /etc/rc.d/rc.wireless.conf
Secondly, if I want to use ndiswrapper, do I have to unload bcm43xx? If so how do i do that?
Thanking in advance,

Lunate 07-28-2007 09:05 PM

You should blacklist the bcm43xx module to keep it from loading at boot. You do that by adding blacklist bcm43xx to /etc/modprobe.conf.

The modifications you make to connect to the WLAN depends on your WLAN configuration. Do you use WEP so WAP? If don't use any encryption at all or WEP, you can configure the card using the ordinary net configuration file (not sure what it's called in Slackware). For WAP you need a program called wpa_supplicant. The easiest way though, is to use Network Manager and either knetworkmanager (plugin for KDE) or nm-applet (plugin for Gnome).

But first of all you should check if the interface is really up using ifconfig and iwconfig.

2Gnu 07-28-2007 09:08 PM

Yes, you must keep the bcm43xx module from loading if using ndiswrapper.

If the system is up and running, remove the module like this:

modprobe -r bcm43xx

To keep it from loading on boot, add this line to /etc/modprobe.d/blacklist:

blacklist bcm43xx

Edit inet1.conf to include your network parameters. Here's an example:
Code:

IFNAME[4]="wlan0"
IPADDR[4]=""
NETMASK[4]=""
USE_DHCP[4]="yes"
DHCP_HOSTNAME[4]=""
GATEWAY="192.168.1.1"
WLAN_ESSID[4]=my_ssid
WLAN_MODE[4]=Managed
WLAN_WPA[4]="wpa_supplicant"
WLAN_WPADRIVER[4]="wext"


adityavpratap 07-28-2007 11:30 PM

Thanks a lot friends, now I have a working wireless connection :)
However there a few things that are to be set right.
When I made the following changes to inet1.conf -
Quote:

IFNAME[4]="wlan0"
IPADDR[4]=""
NETMASK[4]=""
USE_DHCP[4]="yes"
DHCP_HOSTNAME[4]=""
GATEWAY="192.168.1.1"
WLAN_ESSID[4]=my_ssid
WLAN_MODE[4]=Managed
WLAN_WPA[4]="wpa_supplicant" # wpa_supplicant is absent on my system
WLAN_WPADRIVER[4]="wext"
the wireless network was up and kicking. How ever when I rebooted, the booting process halted at -
dhcpd: mac address = xx:xx:xx:xx:xx:xx
for quite some time. And when was finally able to log onto my slack install, the wireless network was down.
I had to give the following commands to get it working
$sudo iwconfig wlan0 essid "RT2561_6"
$sudo dhclient
How can I make these changes permanent so that I don't have to issue these commands each time I boot.

mRgOBLIN 07-28-2007 11:56 PM

replace

Code:

WLAN_ESSID[4]=my_ssid

with

WLAN_ESSID[4]=RT2561_6


2Gnu 07-29-2007 01:02 AM

Quote:

Originally Posted by adityavpratap
$sudo iwconfig wlan0 essid "RT2561_6"
$sudo dhclient

Are you sure you're using Slackware? Those sound an awful lot like Ubuntuisms.

rkelsen 07-29-2007 02:40 AM

Quote:

Originally Posted by 2Gnu
Those sound an awful lot like Ubuntuisms.

Have you ever actually configured wireless under slackware?

What's "Ubuntuist" about sudo?

adityavpratap 07-29-2007 03:58 AM

2Gnu, I may sound stupid, but I am not as stupid as to get the name of my distro wrong. I am using Slackware 11.0 since the time it was released. I have been experimenting with other distros, but my 'main' distro is Slackware. I always keep coming back to it. So kindly be rest assured that I am talking of slackware when I am talking of slackware and not ubuntu, I hope you are getting what I want to convey.
As far as 'sudo' is concerned, I find it more convenient and much more safe than having to log is as root.
Are you suggesting that 'true' slackers do not use sudo?

onebuck 07-29-2007 07:11 AM

Hi,

I'll answer for myself, the sudo is a fine way to access 'root' privileges.
The 'su' command is another means to access. Your 'sudo' is better in the sense that you can control who gains 'root' via the '/etc/sudoers' file.

2Gnu 07-29-2007 09:02 AM

Quote:

Originally Posted by adityavpratap
2Gnu, I may sound stupid, but I am not as stupid as to get the name of my distro wrong. ...
Are you suggesting that 'true' slackers do not use sudo?

It was a joke, based on your use of dhclient vs. dhcpcd and sudo for every line. I use sudo too, but only for specific situations. It's simply a matter of preference.

It wasn't meant to be taken seriously.

Quote:

Originally Posted by rkelsen
Have you ever actually configured wireless under slackware?

No, never. I'm a complete noob, running a copy of SuSE 6.2 I got free in a magazine. Please post some links where I can go to become as learned as you.

adityavpratap 07-29-2007 11:06 AM

2Gnu, I am using dhclient here because I was not familiar with the use of dhcpcd. And more over I didn't realise that the use of dhclient would automatically brand me as a Ubuntu user.
MrGoblin, I have made the changes you suggested and now I don't have to manually set essid.


All times are GMT -5. The time now is 07:39 PM.