-
Wireless.conf slackware loosing settings
So i just got slackware setup on my laptop and got my IPW2200 card working. However, when I reboot it looses my ESSID and WEP key. I put this in /etc/rc.d/rc.wireless.conf
INFO="GOLEM"
ESSID="GOLEM"
MODE="Managed"
KEY="37392FEA52"
but I still have to manually re-enter the settings after each boot. any ideas?
soule
Anarchism is founded on the observation that since few men are wise enough to rule themselves, even fewer are wise enough to rule others. - Edward Abbey
IRC #linuxn00b
Support your Distro.
Slackware Store
Archlinux Schwag
-
Perhaps it's /etc/rc.d/rc.wireless that is not executed at startup. Try to run it manually and if it works this way add it to /etc/rc.d/rc.local
-
restart: unknown interface: No such device
restart: error fetching interface information: Device not found
/etc/rc.d/rc.wireless: /sbin/iwconfig restart mode Managed
Error for wireless request "Set Mode" (8B06) :
SET failed on device restart ; No such device.
/etc/rc.d/rc.wireless: /sbin/iwconfig restart nick ranger
Error for wireless request "Set Nickname" (8B1C) :
SET failed on device restart ; No such device.
/etc/rc.d/rc.wireless: /sbin/iwconfig restart key ************
Error for wireless request "Set Encode" (8B2A) :
SET failed on device restart ; No such device.
/etc/rc.d/rc.wireless: /sbin/iwconfig restart essid GOLEM
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device restart ; No such device.
when i manully restart the rc.wirless i get this error. It seems to be reading rc.wirless.conf, but it can not determine the interface. I tried add the line
INTERFACE="eth1" with no effect
soule
Anarchism is founded on the observation that since few men are wise enough to rule themselves, even fewer are wise enough to rule others. - Edward Abbey
IRC #linuxn00b
Support your Distro.
Slackware Store
Archlinux Schwag
-
Are you running ifconfig to bring up the device before you run rc.wireless?
I noticed that there was a change in the way networking starts up as of my last swaret upgrade. rc.wireless no longer works for me and now it wants to start the wireless through rc.inet1, but I haven't figured out the syntax yet.
Anyway, as my temoporary, and very unsecure, workaround, I put the actual iwconfig commands in rc.local, preceded by ifconfig ath0 up, and followed by dhcpcd ath0.
It's not secure, as my wep key is in plain text, but it is working until I can figure out the rc.inet1 thing.
Let's see, we now have your ESSID and key, what's your address?
-
like i wouldnt have changed a couple of digits in my key
why do you use ath0?
soule
Anarchism is founded on the observation that since few men are wise enough to rule themselves, even fewer are wise enough to rule others. - Edward Abbey
IRC #linuxn00b
Support your Distro.
Slackware Store
Archlinux Schwag
-
Mine is an Atheros-based card running via the madwifi driver. It automatically gets assigned ath0. I assume yours is wlan0 or eth1 or something like that?
-
i tried you approach by making a script to run in rc.local
#!/bin/sh
echo "Connecting to <GOLEM> Wireless Network"
modprobe ipw2200
iwconfig eth1 essid GOLEM
iwlist eth1 scan
iwconfig eth1 mode Managed
iwconfig eth1 key restricted 37392FEA64
iwconfig eth1 essid GOLEM
ifconfig eth1 up
iwconfig
but no dice, when i run it manually it doesnt work any ideas
Anarchism is founded on the observation that since few men are wise enough to rule themselves, even fewer are wise enough to rule others. - Edward Abbey
IRC #linuxn00b
Support your Distro.
Slackware Store
Archlinux Schwag
-
2 things:
-I didn't make a script, I actually placed the commands directly in rc.local.
-I discovered that I couldn't enter the commands by themsleves, but needed the whole path, i.e. /sbin/iwconfig. (I think)
If that doesn't work, I'll reboot to Linux and grab my actual rc.local file for you to look at.
-
pretty please
ive been playing with iwconfig commands for awhile now and am missing something
soule
Anarchism is founded on the observation that since few men are wise enough to rule themselves, even fewer are wise enough to rule others. - Edward Abbey
IRC #linuxn00b
Support your Distro.
Slackware Store
Archlinux Schwag
-
Here you go:
Code:
#!/bin/sh
#
# /etc/rc.d/rc.local: Local system initialization script.
#
# Put any local setup commands in here:
/sbin/ifconfig ath0 up
/sbin/iwconfig ath0 essid "StuartWay"
/sbin/iwconfig ath0 mode "Managed"
/sbin/iwconfig ath0 rate "auto"
/sbin/iwconfig ath0 enc "my_hex_key"
/sbin/dhcpcd ath0
You should be able to issue these commands individually from a console to get online, then add them to rc.local for boot-time happiness. If they don't work as entered individually, then you have another issue.
Also. kde has a wireless config app that is pretty good that applies settings at login. Gnome may have something similar, but I wouldn't know as I keep my slack install pure, as Pat intended...
-
okay tried that but i cant get rid of
eth1 unassociated ESSID:"GOLEM" Nickname:"ranger"
Mode:Managed Channel:0 Access Point: 00:00:00:00:00:00
Bit Rate=0kb/s Tx-Power=20 dBm
Retry limit:7 RTS thr ff Fragment thr ff
Encryption key ff
Power Management ff
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
The "unassociated" part. when i configure it though the network tool in gnome that part changes, but i dont know what command to use to change that.Everything else i can configure throught iwconfig/ipconfig
soule
Anarchism is founded on the observation that since few men are wise enough to rule themselves, even fewer are wise enough to rule others. - Edward Abbey
IRC #linuxn00b
Support your Distro.
Slackware Store
Archlinux Schwag
-
Are you trying to get rid of the nickname, or just change it to something of your choosing?
I believe it's manipulated via iwconfig eth1 nickname "foo"
Or you can omit it entirely.
-
okay this is driving me nuts. i can use inconfig to get the settings exactly like they are when i use the gnome networking tool, but my connection still wont come up.
the only difference is in iwconfig eth1
I get
eth1 unassociated - when i manually do it
and
eth1 ieee80211g - when i let gnome do it.
i cant seem to figure out how to 'associate' the device
soule
Anarchism is founded on the observation that since few men are wise enough to rule themselves, even fewer are wise enough to rule others. - Edward Abbey
IRC #linuxn00b
Support your Distro.
Slackware Store
Archlinux Schwag
-
Have you checked your router logs? I had a connectivity issue the other day and when going from Windows to Linux on the same card/mac address/ip address, it thought the mac address was spoofed and was refusing the connection.
-
let me clarify my problem.
When i boot up my wireless card is detected and eth1 is setup (including the static address). However, the ssid and wep key are not entered. I can go into gnome and enter the ssid and key. and i have access. when i reboot, I have to go through the same process. In theory entering the settings in gnome should "stick" but they dont.
I have been trying to add the settings with ifconfig/iwconfig but can get the connection established. iwconfig shows the correct settings for eth1(ssid, key, channel, ap, etc) but no connectivity. If i can get iwconfig settings to work i will just make a script to do it or do as you suggested and just put it in rc.local.
Im wondering if something like udev or pam is changing settings on boot up.
I will post what commands i am using in order when i boot back into slack.
btw thanks for the help so far
soule
Anarchism is founded on the observation that since few men are wise enough to rule themselves, even fewer are wise enough to rule others. - Edward Abbey
IRC #linuxn00b
Support your Distro.
Slackware Store
Archlinux Schwag
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|