| View previous topic :: View next topic |
| Author |
Message |
fishsupreme
n00b
Joined: 13 Jul 2005
Posts: 5
|
 Posted: Wed Jul 13, 2005 5:43 am Post subject: [SOLVED] Wireless works manually but not automatically |
 |
|
I have a Gentoo installation on a new Dell Inspiron 600m system, using the IPW2200 driver to drive the installed Intel IPW2915 card. I am using wireless-tools to connect to networks, as my primary access point is a Netgear 802.11b wireless router configured with no SSID broadcast, 128-bit WEP, shared key.
Here's the weird issue I have... my /etc/conf.d/net file contains the following:
| Quote: | modules=( "iwconfig" )
essid_eth1="HomeLan"
mode_eth1="managed"
channel_eth1="6"
config_eth1=( "dhcp" )
preferred_aps=( "HomeLan" )
key_HomeLan="12345678901234567890123456" |
(Obviously that's not my real WEP key, but but the point is that it's 26 hex digits.) If I run "/etc/init.d/net.eth1 start", I get the error "Failed to start wireless networking." Running iwconfig shows that nothing has been configured at all... the connection has no ESSID set, no WEP key, nothing.
On the other hand, if I open up a root console and type in the following:
| Quote: | iwconfig eth1 essid HomeLan
iwconfig eth1 channel 6
iwconfig eth1 key restricted
iwconfig eth1 key 12345678901234567890123456
iwconfig eth1 key on
dhcpcd eth1 |
It associates with the access point and works perfectly. Note that leaving out any of those lines will result in it not working; I need all of them.
My eth0 interface (a Broadcom wired card using the b44 driver) works fine being started with /etc/init.d/net.eth0 start. The files /etc/init.d/net.eth0 and /etc/init.d/net.eth1 are both symlinks to /etc/init.d/net.lo.
Any ideas how to get this to work with net.eth1 rather than having to type in commands every time?
Also, it seems either way is going to be awfully inconvenient if I want to, say, use my computer on more than one wireless network, or join others. Is there a better wireless management system for Linux?
Last edited by fishsupreme on Sat Jul 16, 2005 3:39 am; edited 1 time in total |
|
| Back to top |
|
 |
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
| Posted: Wed Jul 13, 2005 6:51 am Post subject: |
|
|
Add RC_VERBOSE="yes" to /etc/conf.d/net and post the full output of net.eth1 start.
Your error message was just soooooooo helpful! 
But wait - you're doing network card to network card? And you say those exact commands work? Holy moley - I think you're an Ad-hoc user and you're config asks for managed mode!
|
|
| Back to top |
|
|
fishsupreme
n00b
Joined: 13 Jul 2005
Posts: 5
|
| Posted: Wed Jul 13, 2005 8:29 pm Post subject: |
|
|
No, I'm not connecting to another network card. As I mentioned, I'm connecting to a Linksys 802.11b access point using a shared key.
Adding RC_VERBOSE="yes" gives me this:
| Quote: | * Caching service dependencies ... [ ok ]
* Starting eth1
* Loading networking modules for eth1
* modules: iwconfig essidnet iptunnel ifconfig adsl dhcpcd apipa
* iwconfig provides wireless
* ifconfig provides interface
* dhcpcd provides dhcp
* Configuring wireless network for eth1
* Connecting to "HomeLan" (WEP enabled - open) ... [ !! ]
* Failed to configure wireless for eth1 [ !! ] |
Doesn't look like the error message gets much better. |
|
| Back to top |
|
|
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
| Posted: Wed Jul 13, 2005 8:45 pm Post subject: |
|
|
If you really need the channel command to get it to work then it's a driver bug
You may be able to work around it like so
| Code: | | iwconfig_eth1="channel 6" |
|
|
| Back to top |
|
|
fishsupreme
n00b
Joined: 13 Jul 2005
Posts: 5
|
| Posted: Sat Jul 16, 2005 3:50 am Post subject: |
|
|
Turned out to be two problems:
1.) Updated IPW2200 to 1.0.5. That took care of requiring Channel as an argument.
2.) I needed to pecify restricted mode for WEP. At the command prompt it was obvious how to do this ("iwconfig eth1 restricted") but it was not so obvious in the configuration file. Specifically, this works:
| Quote: | | key_HomeLan="restricted 012345678901234567890123456" |
while this does not:
| Quote: | key_HomeLan=restricted
key_HomeLan="012345678901234567890123456" |
Regardless of the order I put the commands in. It looks like one of the commands overrides the other if they're not on the same line. |
|
| Back to top |
|
|
|
Networking & Security
