| View previous topic :: View next topic |
| Author |
Message |
paluszak
Apprentice
Joined: 28 Jun 2004
Posts: 274
Location: Warsaw, Poland
|
 Posted: Sun Sep 02, 2007 3:23 pm Post subject: init script can't detect my wlan0 is wireless |
 |
|
Hi,
I've got a problem like this, my /etc/conf.d/net is set more or less properly:
| Code: |
...
essid_wlan0="xxxxxx"
mode_wlan0="Managed"
config_wlan0=("192.168.1.201/24")
routes_wlan0=("default via 192.168.1.103")
dns_servers_wlan0=("194.204.159.1" "217.98.63.164")
...
|
UDEV starts /etc/init.d/net.wlan0 automatically, but it fails to connect to access point (verbose output):
| Code: |
* Starting wlan0
* Loading networking modules for wlan0
* modules: apipa arping ccwgroup macchanger macnet rename iwconfig essidnet iptunnel ifconfig system dhcpcd ip6to4
* iwconfig provides wireless
* ifconfig provides interface
* dhcpcd provides dhcp
* Configuring wlan0 for MAC address 00:40:F4:9D:A2:DB ... [ ok ]
* Wireless extensions not found for wlan0
* Bringing up wlan0
* 192.168.1.201/24 [ ok ]
* Adding routes
* default via 192.168.1.103 ... [ ok ]
|
Of course, there's no link established between my adapter and access point. I think the problem is that the init scripts don't recognize that wlan0 interface is a wireless device. With iwconfig output like this:
| Code: |
...
wlan0 IEEE 802.11b Mode:Managed Frequency:2.472 GHz
Access Point: Not-Associated Bit Rate:11 Mb/s Sensitivity=80/85
Retry:on Fragment thr:off
Encryption key:off
...
|
I fugured out that setting access point name manually should work, and after typing
| Code: |
iwconfig wlan0 essid xxxxxx
|
the link LED on my wireless device lit up and everything started to work fine. I use gentoo kernel 2.6.21-r4 with rtl8180 PCMCIA wireless device. I wonder if somebody knows what to do? I think that, as everything works fine if I issue the commands manually, it's some kind of problem with automated scripts.
Oh, and I use wireless-tools-29_pre22, but the same problem was with previous versions.
J. |
|
| Back to top |
|
 |
didymos
Advocate
Joined: 10 Oct 2005
Posts: 4798
Location: California
|
| Posted: Mon Sep 03, 2007 3:20 am Post subject: |
|
|
It shouldn't matter, but try adding the iwconfig line:
| Code: |
modules=( "iwconfig" )
essid_wlan0="xxxxxx"
mode_wlan0="Managed"
config_wlan0=( "192.168.1.201/24" )
routes_wlan0=( "default via 192.168.1.103" )
dns_servers_wlan0=( "194.204.159.1" "217.98.63.164" )
|
I'm pretty sure that won't work, but what the hell.
_________________
Thomas S. Howard |
|
| Back to top |
|
|
paluszak
Apprentice
Joined: 28 Jun 2004
Posts: 274
Location: Warsaw, Poland
|
| Posted: Mon Sep 03, 2007 5:30 am Post subject: |
|
|
| didymos wrote: | It shouldn't matter, but try adding the iwconfig line:
| Code: |
modules=( "iwconfig" )
essid_wlan0="xxxxxx"
mode_wlan0="Managed"
config_wlan0=( "192.168.1.201/24" )
routes_wlan0=( "default via 192.168.1.103" )
dns_servers_wlan0=( "194.204.159.1" "217.98.63.164" )
|
I'm pretty sure that won't work, but what the hell. |
Unfortunately, it doesn't change much. |
|
| Back to top |
|
|
didymos
Advocate
Joined: 10 Oct 2005
Posts: 4798
Location: California
|
| Posted: Mon Sep 03, 2007 5:40 am Post subject: |
|
|
Umm, alright, I just noticed that it's udev starting the service. So, edit /etc/conf.d/rc and make this change:
| Code: |
RC_PLUG_SERVICES="!net.wlan0"
|
then do:
| Code: |
rc-update -a net.wlan0 default
|
It could be udev is starting the device too early, which is why it works by the time you login and set things manually.
_________________
Thomas S. Howard |
|
| Back to top |
|
|
|
Networking & Security
