Bug 178312

Summary:	Wireless network interface switch problems
Product:	Gentoo Linux	Reporter:	Dmitrij D. Czarkoff <czarkoff>
Component:	[OLD] baselayout	Assignee:	Gentoo's Team for Core System packages <base-system>
Status:	RESOLVED FIXED
Severity:	minor
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Dmitrij D. Czarkoff 2007-05-13 10:32:59 UTC

Most of my time I use one ESSID. At the place this network is there are several ESSIDs avaliable, so I had to manually specify my ESSID in ``/etc/conf.d/net'' via essid_eth2="MyESSID" (my wireless network interface is eth2).
But every time I connect different ESSID I get timeout errors and iwlist fails to scan ESSIDs available. This happens untill I move ``/etc/init.d/net.eth2'' somewhere, reboot and scan the available networks. Then I can either join one manually or replace ESSID setting in ``/etc/conf.d/net'', move ``/etc/init.d/net.eth2'' back and start it.
I failed to find any way to make it right via Gentoo's default INIT scrips. May be there could be some appropriate solution for this?

Comment 1 Roy Marples (RETIRED) gentoo-dev

2007-05-13 12:14:08 UTC

Have you tried using preferred_aps=( "SSID" ) instead of essid_eth2=...

Also, what is your wireless hardware and driver?

Comment 2 Dmitrij D. Czarkoff 2007-05-13 12:16:56 UTC

Controller identified by lspci as:
03:09.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)

ipw2200 driver respectively. No problems with no INIT scrips applied.

Comment 3 Roy Marples (RETIRED) gentoo-dev

2007-05-13 12:39:57 UTC

Why don't you use wpa_supplicant then? It should work better with our scripts and is a proper link manager :)

Comment 4 Dmitrij D. Czarkoff 2007-05-13 12:47:30 UTC

It has somehow odd configuration. And I still would prefer to use Gentoo's default solution.
Anyway, neither of my nerworks use WPA, so I don't see a case for it.

Comment 5 Roy Marples (RETIRED) gentoo-dev

2007-05-13 12:52:17 UTC

The default solution for baselayout-2 is wpa_supplicant as wpa_supplicant can also connect to WEP and unsecured access points. The beauty is that as it's a daemon and you go out of range, it will attempt to connect to other AP's you may have configured for. Our scripts are one shot, so cannot do this.

Anyway, if you want to try and debug, then lets do it! What baselayout version are you using?

Comment 6 Dmitrij D. Czarkoff 2007-05-13 13:01:47 UTC

sys-apps/baselayout-1.12.10-r4

Comment 7 Roy Marples (RETIRED) gentoo-dev

2007-07-12 13:53:01 UTC

I have this fixed in baselayout-2.0.0_alpha4 for sure. I'm not sure I want to backport it to baselayout-1.