--- In [email protected], "Ram Juvvadi" <[EMAIL PROTECTED]> wrote: > > > > > Hey, it works now. I am able to connect to the net and iwconfig shows > > the WEP key for wlan0. > > > > Thanks a lot friend. :-) > > > > PS: Is there a way I can test whether encryption is actually on? > > Very nice. > > If iwconfig shows essid that means WEP is on... > > You didn't mention what made it work... executable permissions on > inet1.conf or removing 0x from Key? Just curious. > > If this is a laptop I am guessing that you won't be needing this > configuration all the time, and having this configuration at the > startup will make startup a little more time consuming, particularly > when you don't need it. > > I usually have a script something like this : > /sbin/wifi: > > ############################### > #!/bin/sh > > /sbin/iwconfig wlan0 > sleep 1 > /sbin/iwconfig wlan0 essid xxxxx > sleep 1 > /sbin/iwconfig wlan0 key xxxxxxx > sleep 1 > dhclient wlan0 > > ############################### > > When I login from home and need wifi, I do sudo /sbin/wifi > >
Hi, It was working fine till I rebooted. then again iwconfig wlan0 was not showing essid. I checked the permissions for rc.inet1.conf. You were right, it was not executable. I made it executable. Then again tried the following setps - # iwconfig wlan0 # iwconfig wlan0 essid xxxxxxxx # iwconfig wlan0 key xxxxxxxxxx and I was surprised to see that the connection was not up. I struggled for 2 or 3 hours then I found that by changing WEP 64 encryption to WEP 128 encryption, the network was detected. iwconfig was showing the correct essid. Then I did the following - # ifconfig wlan0 down # iwconfig wlan0 essid xxxxxxxx # iwconfig wlan0 key xxxxxxxxxxxxxxxxxxxxxxxxxx # ifconfig wlan0 up Then the network was detected and iwconfig was showing the correct essid and I was able to browse the net. I want to see if it works after I reboot once again.
