nysus1
asked on
How do configure /etc/network/interfaces file to work with encryption?
I have a Linksys wmp-11 wireless PCI card on my Debian system and trying to connect to a Linksys 4 port router. More accurately, I'm trying to get it to work with encryption turned on. It works fine without encryption.
Here's the relevant portion of my /etc/network/interface file:
wireless_mode Ad-Hoc
wireless_essid linksys
wireless_key 26-hex-digits
I've tried a bunch of other settings but couldn't get anything to work.
Here's the relevant portion of my /etc/network/interface file:
wireless_mode Ad-Hoc
wireless_essid linksys
wireless_key 26-hex-digits
I've tried a bunch of other settings but couldn't get anything to work.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
note that mode has to be managed if connecting to a linksys router, as ad-hoc networking is for computer to computer connections without involving a wireless router or AP
ASKER
Re the managed setting. I had it that way initially. The ad-hoc setting was there out of desperation.
The good news is I got it working. The frustrating thing is that I'm not sure what fixed it. I disabled encryption on the router and removed the encryption key from the interface file. But the 'iwconfig eth1' told me the password key was still being used; even after issuing a '/etc/init.d/networking restart' command. When I renabled encryption on the router and the interface file and did 'iwconfig eth1 key on' it started to work.
My question is: Why did I have to issue that command? Doesn't '/etc/init.d/networking restart' take care of that?
The good news is I got it working. The frustrating thing is that I'm not sure what fixed it. I disabled encryption on the router and removed the encryption key from the interface file. But the 'iwconfig eth1' told me the password key was still being used; even after issuing a '/etc/init.d/networking restart' command. When I renabled encryption on the router and the interface file and did 'iwconfig eth1 key on' it started to work.
My question is: Why did I have to issue that command? Doesn't '/etc/init.d/networking restart' take care of that?
Excerpt from http://www.linuxcommand.org/man_pages/iwconfig8.html
Some cards may not apply changes done through Wireless Extensions immediately (they may wait to aggregate the changes or apply it only when the card is brought up via ifconfig). This command (when available) forces the card to apply all pending changes. This is normally not needed, because the card will eventually apply the changes, but can be useful for debugging.
Some cards may not apply changes done through Wireless Extensions immediately (they may wait to aggregate the changes or apply it only when the card is brought up via ifconfig). This command (when available) forces the card to apply all pending changes. This is normally not needed, because the card will eventually apply the changes, but can be useful for debugging.