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.
We (and you) will need to know the chipset of the card before we can do much.
Make sure that the card is enabled in BIOS, that it's turned on - some wireless cards have a key sequence or a physical switch, then run lspci to see what's there.
Make sure that the card is enabled in BIOS, that it's turned on - some wireless cards have a key sequence or a physical switch, then run lspci to see what's there.
Code:
#lspci -v
0000:00:12.0 Network Controller: Intersil Corporation Prism 2.5 Wavelan Chipset (rev 01)
Subsystem: Fujitsu Ltd.: Unknown device 1169
Flags: medium devsel, IRQ 9
Memory at e8103000 (32-bit, prefetchable) [size=4K]
Capabilities: [dc] Power Management version 2
Built-in WiFi is turned on, has switch on laptop....
You're in fat city. That chipset is well-supported.
modprobe orinoco_cs will load the driver you need (this assumes that the vanilla Sarge kernel includes wireless support - I'd be very surprised to learn otherwise).
The iwconfig command will list the available wireless interfaces - probably eth1 in your case. Add some options - iwconfig eth1 essid herb where "herb" is the SSID, for example - to set the wireless parameters.
Someone who knows Debian can tell you where to put those settings to make them persist after a reboot - in a network control script.
Won't know for sure till I go home and test on my WiFi network, but it
appears from what I see in terminal that it's recognized and working...
Will report back later to confirm...
THANKS for your help!
Mark
Quote:
Originally posted by 2Gnu You're in fat city. That chipset is well-supported.
modprobe orinoco_cs will load the driver you need (this assumes that the vanilla Sarge kernel includes wireless support - I'd be very surprised to learn otherwise).
The iwconfig command will list the available wireless interfaces - probably eth1 in your case. Add some options - iwconfig eth1 essid herb where "herb" is the SSID, for example - to set the wireless parameters.
Someone who knows Debian can tell you where to put those settings to make them persist after a reboot - in a network control script.
OK, the bus architecture of the card is mini-PCI so my mistake with the orinoco_cs. You want to modprobe orinoco_pci. Not sure why it's erroring when you modprobe it, though, especially if lsmod shows that it's already there.
Check your spelling. You typed orinocco - probably just a typo in your post vs. a bad command.
Irrespective of the above, assuming orinoco_pci is loaded, what does iwconfig display? eth1 or wlan0 should as active. Set the mode (managed) the ESSID and any encryption with iwconfig, then try to pull an IP from the router.
eth1 IEEE 802.11-DS ESSID: "key" Nickname: "Prism I"
Mode: Managed Access Point: 00:00:00:00:00:00 Bit Rate: 11 Mb/s
Tx-Power=15 dBm Sensitivity: 1/3
Retry min limit: 8 RTS thr: off Fragment thr: off
Encryption key: 4xxx-xxxx-xx Security mode: open
Power Management: Off
Also, did
#iwconfig eth1 essid NetworkName key xxxxxxxxx
#ifconfig eth1 up
#chclient eth1
After a bunch of text, I got:
sit0: unknown hardware address type 776
Listening on LPF/eth1/00:e0:00:d3:f4:8e
Sending on LPF/eth1/00:e0:00:d3:f4:8e
Sending on Socket/fallback/fallback-net
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database.
The all zeros for the access point says that you're not associated.
Are you running MAC address filtering by any chance? If so, turn it off.
Is the SSID being broadcast? Some configs don't work properly with it off.
Is "key" your ESSID? If so, as least that part worked.
Have you tried without WEP? If that works, maybe just a key entry error.
This line: #chclient eth1 should be dhclient eth1. Again, I'm assuming a typo, but just checking.
To automate, you can do one of several things (mostly, it's a personal preference but there can be a "right" way depending on certain timings - that is, you shouldn't be trying to ask for an IP address until you set up the wireless parameters.):
1. If there's a wireless configuration file, put the desired values there. In Slack, it's /etc/rc.d/rc.wireless.conf. Debian devotees, help us out, here.
2. There is usually a network script. In Red Hat, for example, it's /etc/sysconfig/network-scripts/ifcfg-eth1. Wireless parameters can go here, along with dhcp requests, etc.
3. Local. Be it /etc/rc.d/rc.local or similar, there's always a place of last resort to put things that happen on boot. Be sure to use the full path.
Module loading in 2.6 kernels is in /etc/modprobe.conf. For Sarge and a stock kernel, I think you're still using /etc/modules.conf.
Lastly, the dual interfaces:
I simply take one down before bringing the other up via the command line as needed. (ifconfig eth0 down. If you have a script, like RH, it might be ifup eth0) You can use both interfaces for certain situations, but generally wouldn't want to. Look around for ip masquerading HOWTOs.
Hope that helps.
edit - forgot the WEP key thing.
iwconfig eth1 key 12345abde will set it manually or in a local script. Look at the syntax in the network config or interface script for Debin to get the right setting. The Airport, IIRC, has a 0x prefix for the key to denote hex vs. ASCII. Linux assumes hex. If the Airport shows the key as 0x12345abcde, enter it in your laptop as iwconfig eth1 key 12345abcde. Some config files use hyphens: 1234-5abc-de. Strange, but true.
Happy to help. My head still hurts from the wall-banging I did trying to get wireless going under Red Hat 7.2 on a PII 266 Dell laptop when I was too new to even be able to spell Linux. (Can you say "train wreck?")
Wish I could help more with Debian, but I ran it for all of a few days several months ago. Try the LQ Debian forum or here: http://forums.debian.net/
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.