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.
Hello, I am having a small difficulty with Debian kernel 2.6.8-2-6 I could get it to work on my old 2.4 kernel with the current settings.. I have the wireless settings correct and i can get the connection up by changing the essid to the correct one, but when it boots, the essid is changed back to the default Cisco essid which is tsunami now my /etc/network/interfaces file says
auto lo
iface lo inet loopback
auto eth1
iface eth1 inet dhcp
wireless-essid (took out essid but it is correct to get the network up)
wireless-key (took out wep key but it is correct to get the network up)
The wep key is correct in iwconfig but for some reason at boot the essid stays as
tsunami
i cannot figure out why..
i am running:
IBM Thinkpad T40 Laptop
Debian kernel-image-2.6.8-2-686
Cisco 350 Series Wireless Adapter
Thanks
If you are running with /proc support, either you have a file echoing the name 'tsunami' into the ESSID dir, or you are connecting to another box in ad hoc mode.To echo a string into the ESSID, I'd do it from /etc/init.d/local, like this:
echo "string" > /proc/drivers/aironet/eth1/ESSID
Check the path first though -- I may have mixed the subdiretory order. This is my preferred method when using Aironet Cisco cards because there is a substantial amount of data available that isn't reported by the wireless tools.
ok the second suggestion given seems to work except for one thing..there is no /proc/drivers/aironet/eth1/ESSID but rather /proc/driver/aironet/eth1/SSID and i tried echoing to that and it works but it does not change the essid which was my intent..is there a way to change the ESSID in this way? thanks for the help
ive realized the reason why the essid is what it is..is because it is the default on the cisco card..and it is somehow not getting written in the /etc/network/interfaces and it stopped working when i switched kernels..so any suggestions keeping that in mind?
I have solved my problem, just not in the way that I expected..all i had to do was add a line to /etc/init.d...i chose /etc/init.d/networking being the most relevant "iwconfig eth1 essid (MY ESSID)"
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.