Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
<conceited-statement>
This is one of those rare occasions where I can't do something
myself.
</conceited-statement>
I've recently purchased a Netgear MA401. Why I didn't simply look online to discover the fact that this particular card is raw un-adulturated crap, I'll never know. However, it DOES use the PrismII chipset, which is the reason that I purchased this POS. I installed pcmcia, wlan-ng, and kismet. I've been trying to get the prism2 drivers to work with kismet, however, I've had no such luck. Apparently, the prism2 drivers work, but kismet_server throws this exception:
"FATAL: Prism2 open socket() failed. (Address family not supported by protocol)"
It's a Netgear MA401RA....does this mean I'm forced to use the orinoco cards? if so, how do I apply Snax's patch?
I'm running kernel 2.2.21, pcmcia 3.1.34, and wlan-ng 0.1.14
Apparently, a Netgear MA401 and a Netgear MA401RA are TOTALLY different. Netgear MA401 uses the prism2_cs driver from wlan-ng, whereas MA401RA uses the orinoco driver from the pcmcia package. I found Snax's patch, and it seems to add the monitor function to my card, which will now work with libpcap and the orinoco option under kismet
The solution: apply snax's patch and edit kismet.conf to reflect device=eth0, captype=pcap, and cardtype=orinoco
I have the same card (MA401) except I'm an extreme Newbie and I don't know where to start. Would ANYONE know how to install drivers for my wireless card. I'm running RedHat 8.0
Okay, for when we get there, what's the type of wireless Router, are you using WEP, and do you get your IP from the router using dhcp (in windows land, that's setting the card to "obtain settings automagically"), or are you hand configuring the thing with static IPs?
I'm having a hell of a time actually getting to any sites here at work as they're monkeying about with the firewall and I can get to Tournhilles page, but not bloody shmoo.org to check any of the mailing lists!!!
First off, when the machine boots, with the wireless card in, does it give the two happy beeps, or the one happy beep and then a well... bonk?
The first beep is it seeing the pcmcia bus and loading its driver, the second sound is it seeing the card, if its the happy beep, it loaded the drivers, if its a hard toned bonk, it couldn't figure the card.
Yeah, I know, sounds juvenile, but its pretty smart in the long run.
Now, if you've got two happy beeps, or even if you don't, try and post the output of the last dozen or so lines outputed by the command:
I'm using a Netgear MR314 Wireless router, no WEP yet and it configured for DHCP. I did however lock access to the router to the MAC address of the wireless card that I have (MA401).
I only get one beep and on the boot up it "failed" to activate the Orinoco_cs driver on eth1 because the device does not seem to be present......delay initilizaiton.
It also fails to detect an IP address for the first (built in) ethernet device. I don't have this one plugged in.
Is there any way I can view that long startup log that the system goes through?
the last 12 lines of the command dmesg go something like this:
socket status: 30000010
yenta IRQ list 0a98, PCI irq10
socket status 300000006
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0c00-0x04ff: excluding 0x170-0x177 0x370-0x37F 0x398-0x39F 0x4d0-0x4d7
cs: IO port probe 0x0c00-0x0aff: clean.
cs: IO port probe 0xa0000000-oxa0ffffff: clean.
maestro3: version 1.22 built at 13:45:29 Sept 4 2002
PCI: Found IRQ 5 for device 00:0d.0
maestro3: Configuration ESS Maestro3(i) found at I0 0x1800 IRQ 5
maestro3: subvendor id: 0x0010103c
ac97_codec: AC97 Audio codec, id: 0x8384:0x7609 (SigmaTel STAC9721/23)
hope I got it all right!!
Do you need specific lines from the output?
1) breathe real deeply, because things are about to suck....
2) log in as root and type "cardctl ident 0" and "cardctl ident 1", then post the output
3) type "lsmod" and paste in the output
we already have your pertinent dmesg output.
you may have some problems with the hermes driver :X
I think I may have your solution. I'm using Redhat 8.0 and a Netgear MA401RA. In order to get it to work, I had to add the following to /etc/pcmcia/config (from the linux-wlan mailing list):
eth1 IEEE 802.11-DS ESSID:"" Nickname:"Prism I"
Mode:Managed Frequency:42.9497GHz
Access Point: 00:00:00:00:00:00
Bit Rate:11Mb/s Tx-Power=15 dBm Sensitivity:1/3
Retry min limit:8 RTS thrff Fragment thrff
Encryption keyff
Power Managementff
Link Quality:0/92 Signal level:-68 dBm Noise level:-122 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Also noticed this in /var/log/messages
kernel: eth1: channel out of range (0)!
Where do I set the channel??
Also, my encryption key 1 that is entered in windows is for the 64bit mode, is 1011121314 - i tried iwconfig eth1 enc 1011121314 and the encryption mode appeared as open and the key appear next to encryption key - hyphenated every 4 digits.
Also, my encryption key 1 that is entered in windows is for the 64bit mode, is 1011121314 - i tried iwconfig eth1 enc 1011121314 and the encryption mode appeared as open and the key appear next to encryption key - hyphenated every 4 digits.
That's fine, it should be how the key looks. It just occured to me, I don't think you've actually brought this device up yet.
ifconfig eth1 up
then assign it an essid (usually called the network name in wireless land).
iwconfig eth1 essid whatever
then add the encryption.
I'm thinking you don't have a channel setting because the device is down right now. Regardless, if this is an infrastructure network, as most are, you don't need to set a channel, it'll scan through the 11 available.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.