First post, apologies to all if I get the etiquette wrong. A relative n00b to the world of linux, I am running SuSE 9.1 and attempting to climb the himalayas. Sorry, I meant get my wireless adaptor to connect to the network. Two weeks in the ndiswrapper foothills, I find myself at a dead end. In a nutshell, no matter what I do, (iwconfig, YAST, editing the ifcfg-wlan0 file directly), ssid cannot be set. (See iwconfig below). Please help, I'm not sure I can take any more of this. dmesg, ifconfig and iwconfig as follows. dmesg ndiswrapper: unsupported module, tainting kernel. ndiswrapper version 0.8 loaded ndiswrapper adding rtl8180.sys wlan0: ndiswrapper ethernet device 00:50:fc:bd:fb:62 using driver rtl8180.sys wlan0: no IPv6 routers present ifconfig wlan0 Link encap:Ethernet HWaddr 00:50:FC:BD:FB:62 inet6 addr: fe80::250:fcff:febd:fb62/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:34 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:16980 (16.5 Kb) Interrupt:11 Memory:ee000000-ee0000ff wlan0 IEEE 802.11b ESSID:"" Nickname:"HOME" Mode:Auto Frequency:2.412GHz Access Point: FF:FF:FF:FF:FF:FF Bit Rate=11Mb/s Tx-Power:20 dBm Sensitivity=0/3 RTS thr=2432 B Fragment thr=2432 B Encryption key:off Power Management:off Link Quality:100/100 Signal level:-95 dBm Noise level:-256 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
On Friday 08 October 2004 11:42, Nick Davies wrote:
First post, apologies to all if I get the etiquette wrong.
A relative n00b to the world of linux, I am running SuSE 9.1 and attempting to climb the himalayas. Sorry, I meant get my wireless adaptor to connect to the network. Two weeks in the ndiswrapper foothills, I find myself at a dead end. In a nutshell, no matter what I do, (iwconfig, YAST, editing the ifcfg-wlan0 file directly), ssid cannot be set. (See iwconfig below). Please help, I'm not sure I can take any more of this.
have you tried iwconfig wlan0 mode managed? If it's an access point you'll want to set that to managed. if you want to set that in ifcfg-wlan0 it will look like: WIRELESS_MODE="Managed" Can you paste your ifcfg-wlan0???? I'd like to see it. It looks to me like you're not even getting the MAC address of the AP, so it's not connecting.
dmesg, ifconfig and iwconfig as follows.
dmesg ndiswrapper: unsupported module, tainting kernel. ndiswrapper version 0.8 loaded ndiswrapper adding rtl8180.sys wlan0: ndiswrapper ethernet device 00:50:fc:bd:fb:62 using driver rtl8180.sys wlan0: no IPv6 routers present
ifconfig wlan0 Link encap:Ethernet HWaddr 00:50:FC:BD:FB:62 inet6 addr: fe80::250:fcff:febd:fb62/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:34 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:16980 (16.5 Kb) Interrupt:11 Memory:ee000000-ee0000ff
wlan0 IEEE 802.11b ESSID:"" Nickname:"HOME" Mode:Auto Frequency:2.412GHz Access Point: FF:FF:FF:FF:FF:FF Bit Rate=11Mb/s Tx-Power:20 dBm Sensitivity=0/3 RTS thr=2432 B Fragment thr=2432 B Encryption key:off Power Management:off Link Quality:100/100 Signal level:-95 dBm Noise level:-256 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
-- Jake Sallee spark@breathdedeeply.com www.breathedeeply.com Hate viruses? Hate Microsoft? Try Linux! SuSE Linux 9.1 Professional www.suse.com Registered Linux User #358012 http://counter.li.org
Hello, Another thing I'm noticing is that you don't have your encryption key set. (You are using encryption, right??....right???? :D ) iwconfig wlan0 key XXXXXXXXXX I've noticed that sometimes the essid _has_ to be the first thing set, otherwise iwconfig wouldn't accept the change there. There is a program kwifimanager that allows you to set this stuff up, but I haven't played with it very much. Keep us posted on your progress. Mike Sacco -----Original Message----- From: Jake Sallee [mailto:spark@breathedeeply.com] Sent: Friday, October 08, 2004 1:07 PM To: suse-linux-e@suse.com Subject: Re: [SLE] unconfigurable iwconfig On Friday 08 October 2004 11:42, Nick Davies wrote:
First post, apologies to all if I get the etiquette wrong.
A relative n00b to the world of linux, I am running SuSE 9.1 and attempting to climb the himalayas. Sorry, I meant get my wireless adaptor to connect to the network. Two weeks in the ndiswrapper foothills, I find myself at a dead end. In a nutshell, no matter what I do, (iwconfig, YAST, editing the ifcfg-wlan0 file directly), ssid cannot be set. (See iwconfig below). Please help, I'm not sure I can take any more of this.
have you tried iwconfig wlan0 mode managed? If it's an access point you'll want to set that to managed. if you want to set that in ifcfg-wlan0 it will look like: WIRELESS_MODE="Managed" Can you paste your ifcfg-wlan0???? I'd like to see it. It looks to me like you're not even getting the MAC address of the AP, so it's not connecting.
dmesg, ifconfig and iwconfig as follows.
dmesg ndiswrapper: unsupported module, tainting kernel. ndiswrapper version 0.8 loaded ndiswrapper adding rtl8180.sys wlan0: ndiswrapper ethernet device 00:50:fc:bd:fb:62 using driver rtl8180.sys wlan0: no IPv6 routers present
ifconfig wlan0 Link encap:Ethernet HWaddr 00:50:FC:BD:FB:62 inet6 addr: fe80::250:fcff:febd:fb62/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:34 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:16980 (16.5 Kb) Interrupt:11 Memory:ee000000-ee0000ff
wlan0 IEEE 802.11b ESSID:"" Nickname:"HOME" Mode:Auto Frequency:2.412GHz Access Point: FF:FF:FF:FF:FF:FF Bit Rate=11Mb/s Tx-Power:20 dBm Sensitivity=0/3 RTS thr=2432 B Fragment thr=2432 B Encryption key:off Power Management:off Link Quality:100/100 Signal level:-95 dBm Noise level:-256 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
-- Jake Sallee spark@breathdedeeply.com www.breathedeeply.com Hate viruses? Hate Microsoft? Try Linux! SuSE Linux 9.1 Professional www.suse.com Registered Linux User #358012 http://counter.li.org -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Hi,
Another thing I'm noticing is that you don't have your encryption key set. (You are using encryption, right??....right???? :D )
I don't have encryption set, figuring that I would get it going without first. (Also, I am in the middle of a medeival town in southern france where computers are scare, let alone wireless networks, so no worries there).
I've noticed that sometimes the essid _has_ to be the first thing set, otherwise iwconfig wouldn't accept the change there.
No difference
There is a program kwifimanager that allows you to set this stuff up, but I haven't played with it very much.
I have played with it a bit but the only thing it seems to add is some kind of graphical display of the signal strength. I'm not so keen on adding a fourth element into the mix. Also, I notice that using iwconfig I can change my nickname, i.e., the next iwconfig reports the changed name. However, my ifcfg-wlan0 file is not changed, the old nickname is still there. It seems that some values (but not all) are refected in iwconfig but changes made in iwconfig are not reflected in the file at all.What is going on here? Where is the master record held and what governs it's contents?
I've noticed that sometimes the essid _has_ to be the first thing set, otherwise iwconfig wouldn't accept the change there.
No difference
when you use ifup, if it can't find ifcfg-wlan0 then it's going to use its generic script to bring up the interface. I've located this in /etc/sysconfig/network/scrips/ifup-wireless Reading through the script, I found this, which I rememeber skimming through back when I created my ifcfg-wlan0: setup_iwdev() { # Mode need to be first : some settings apply only in a specific mode ! run_iw_tool config mode $WIRELESS_MODE # This is a bit hackish, but should do the job right... if [ -n "$WIRELESS_ESSID" -o -n "$WIRELESS_MODE" ] ; then test -z "$WIRELESS_NICK" && WIRELESS_NICK=`/bin/hostname` fi # Regular stuff... while read OPT ARG; do run_iw_tool config $OPT "$ARG" done <<-EOL nick $WIRELESS_NICK nwid $WIRELESS_NWID freq $WIRELESS_FREQ channel $WIRELESS_CHANNEL sens $WIRELESS_SENS rate $WIRELESS_RATE rts $WIRELESS_RTS frag $WIRELESS_FRAG $WIRELESS_IWCONFIG_OPTIONS EOL # set encryption key(s) run_iw_tool config key off if [ -z "$WIRELESS_SEC_MODE" ]; then case "$WIRELESS_AUTH_MODE" in shared|sharedkey|restricted) WIRELESS_SEC_MODE="restricted";; esac fi if [ -n "$WIRELESS_KEY_0" -a \ -z "$WIRELESS_KEY_1" -a \ -z "$WIRELESS_KEY_2" -a \ -z "$WIRELESS_KEY_3" ]; then # some drivers (at least madwifi) do not like multiple keys # so we do not use that setting method when we have only one run_iw_tool config key $WIRELESS_SEC_MODE $WIRELESS_KEY_0 elif [ -n "$WIRELESS_KEY_0" ]; then ARG="key $WIRELESS_SEC_MODE $WIRELESS_KEY_0 [1]" for i in 1 2 3 ; do eval K=\$WIRELESS_KEY_$i test -n "$K" && ARG="$ARG key $K [$((i+1))]" done run_iw_tool config $ARG if [ $RETVAL -ne 0 ]; then logerror "setting encryption key FAILED, aborting interface setup" exit $R_ERROR fi test -z "$WIRELESS_DEFAULT_KEY" && WIRELESS_DEFAULT_KEY=0 run_iw_tool config key [$((WIRELESS_DEFAULT_KEY+1))]
Reading through the script, I found this, which I rememeber skimming through back when I created my ifcfg-wlan0:
I've given up on this adaptor because I'm running out of time. I need to learn more about linux before adding scripts and that's not something I want to do under pressure - I have to have a connection up within the next 24 hours or start missing work deadline - and I wouldn't expect to be walked through it here. I will have a quick look at the smc2662w usb adaptor which I also have but it doesn't look hopeful. An hour of googling and all I see are problems, problems and more problems. However, many thanks for your efforts and when I do get around having another go at this problem I will post my results. In the meantime, it's back to richmond for me. By the way, if you do happen to know of a surefire, no problem, installs first time out of the box pci wireless adaptor, please do let me know.
Reading through the script, I found this, which I rememeber skimming through back when I created my ifcfg-wlan0:
I've given up on this adaptor because I'm running out of time. I need to learn more about linux before adding scripts and that's not something I want to do under pressure - I have to have a connection up within the next 24 hours or start missing work deadline - and I wouldn't expect to be walked through it here.
What I meant by pasting that script is that you should put WIRELESS_MODE='managed' at the first line of your ifcfg-wlan0. Have you tried that?
I will have a quick look at the smc2662w usb adaptor which I also have but it doesn't look hopeful. An hour of googling and all I see are problems, problems and more problems.
However, many thanks for your efforts and when I do get around having another go at this problem I will post my results. In the meantime, it's back to richmond for me.
By the way, if you do happen to know of a surefire, no problem, installs first time out of the box pci wireless adaptor, please do let me know.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- "The internet doesn't have walls or fences, so who needs Windows or Gates?" Jake Sallee spark@breathedeeply.com www.breathedeeply.com Say goodbye to Microsoft, switch to Linux! www.suse.com Novell's SuSE Linux 9.1 Professional
What I meant by pasting that script is that you should put WIRELESS_MODE='managed' at the first line of your ifcfg-wlan0. Have you tried that?
Yes, I've tried that but it makes no difference. I've also moved my computer to a position where signal strength cannot be an issue and that's made no difference either. I've written to the card manufacturer, (Edimax), in the vain hope they'll take an interest, but don't hold your breath. If you have any other ideas or a recommendation for a card, let me know. Thanks again.
I've given up on this adaptor because I'm running out of time.
Pulled it out of the machine then put it back because I couldn't find a blanking panel. Then, just out of curiosity, edited the ifcfg-wlan file so that mode was set to auto. The card then came to life, the ssid was picked up and I now have a blinking light for the first time. But, iwconfig shows the network as ad-hoc even though it's managed and I can't connect. Gave me a bit of hope though. What would really help me would be to understand what all the parameters in the ifcfg-wlan0 file mean. I have read info iwconfig several times but cannot see where the parameters set there appear in this file, or rather, where parameters in this file are set in iwconfig. Also, in YAST there are other parameters, (such as routing), which do not appear in iwconfig or in the ifcfg-wlan0 file.
participants (3)
-
Jake Sallee
-
Michael Sacco
-
Nick Davies