Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#10469 - netcfg2 autodetection doesn't stop after right wifi network is found

Attached to Project: Arch Linux
Opened by Ivan N. Veselov (dying_sphynx) - Thursday, 22 May 2008, 09:07 GMT
Last edited by James Rayner (iphitus) - Wednesday, 06 August 2008, 07:40 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To James Rayner (iphitus)
Architecture i686
Severity Medium
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

I've set up two network profiles for different wi-fi networks.

After this I'm trying to use autodetection as said here in the wiki:

http://wiki.archlinux.org/index.php/Network_Profiles

"Alternatively, for detection on boot, you may set SCAN="yes" in each profile, and add them to NETWORKS=() in /etc/rc.conf. This will check each network if it is available, and connect if it is, then ignore others."

So I have NETWORKS=(supernova tts ethernet) in my rc.conf.
After restarting net-profiles I have the following:

sphynx@behexen:/etc/network.d% sudo /etc/rc.d/net-profiles restart
Password:
:: supernova down [DONE]
:: supernova up [DONE]
:: tts up - Interface eth1 already in use [FAIL]
- Network unavailable [FAIL]
:: ethernet up - No connection available [FAIL]


So, the first network is connected succesfully but after trying the second network (tts) - eth1 (my wireless interface) is in down state and network is unavaiable at all.

I've tried another approach suggested in wiki: NETWORKS=("auto-wireless eth1" ethernet) and it works fine.

Additional info:
* package version(s)
netcfg2 2.0.6-1

* config and/or log files etc.

/etc/network.d/supernova:

CONNECTION="wireless"
INTERFACE=eth1
SCAN="yes"
SECURITY="wpa"
ESSID="supernova"
KEY="censored"
IP="dhcp"
TIMEOUT=20

/etc/network.d/tts:

CONNECTION="wireless"
INTERFACE=eth1
SCAN="yes"
ESSID="256"
SECURITY="none"
IP="dhcp"
TIMEOUT=10

/etc/network.d/ethernet:

CONNECTION="ethernet"
DESCRIPTION="A very basic ethernet profile, using dhcp"
INTERFACE=eth0
IP="dhcp"
DHCP_TIMEOUT=5


Steps to reproduce:

1. Create two wireless network profiles (net1 and net2) in /etc/network.d with SCAN="yes" for both
2. Set NETWORKS=(net1 net2)
3. Make sure that net1 is available and net2 is NOT
4. Run sudo /etc/rc.d/net-profiles restart
This task depends upon

Closed by  James Rayner (iphitus)
Wednesday, 06 August 2008, 07:40 GMT
Reason for closing:  None
Comment by James Rayner (iphitus) - Thursday, 22 May 2008, 10:44 GMT
That's terribly odd.

<quote... code>
err_append "Interface $INTERFACE already in use"
stat_fail && return 1
</quote>

See the return 1? It should see that interface is in use and just stop right there.

The return 1 will always be executed whenever that message is displayed.

I havn't got a clue why it gets to the Network Unavailable stage... -- and the setup you describe works for me. You sure you havn't modified the scripts?
Comment by Aaron Griffin (phrakture) - Thursday, 22 May 2008, 16:40 GMT
You sure it should be 'return 1' and not 'exit 1' ? I haven't looked at the code at all
Comment by Ivan N. Veselov (dying_sphynx) - Thursday, 22 May 2008, 23:05 GMT
James, I haven't modified the scripts.
Comment by James Rayner (iphitus) - Friday, 23 May 2008, 00:33 GMT
phrak: nop, this is inside a function, so return 1 is correct.

I wouldn't have a clue why this is happening. I'll do what I can to try and replicate it...

Phrak's right though, i've probably made some really silly mistake or missing something dead obvious.
Comment by James Rayner (iphitus) - Saturday, 28 June 2008, 03:55 GMT
try the new version in [testing]
Comment by James Rayner (iphitus) - Tuesday, 05 August 2008, 23:54 GMT
working?
Comment by Ivan N. Veselov (dying_sphynx) - Wednesday, 06 August 2008, 06:53 GMT
This problem seems to be related to my wireless driver ipw2200 (after 'rmmod ipw2200 && modprobe ipw2200' all bugs disappear), so netcfg2 works good now.

Loading...