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#5590 - autodetect support for netcfg 0.1.99

Attached to Project: Arch Linux
Opened by Christ Schlacta (aarcane) - Saturday, 14 October 2006, 20:38 GMT
Last edited by James Rayner (iphitus) - Friday, 09 March 2007, 07:48 GMT
Task Type Feature Request
Category System
Status Closed
Assigned To James Rayner (iphitus)
Architecture not specified
Severity Very Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I have written a patch to add auto detection for wireless networks to netcfg version 0.1.99.

there is an alternate version I could write and submit which will run quicker, but is also more likely to malfunction in a system with multiple wireless interfaces.
This task depends upon

Closed by  James Rayner (iphitus)
Sunday, 01 April 2007, 07:53 GMT
Reason for closing:  Fixed
Additional comments about closing:  fixed in network-scripts git
http://wiki.archlinux.org/index.php/Netw ork_Scripts
Comment by James Rayner (iphitus) - Sunday, 15 October 2006, 07:33 GMT
you can already do this, using /etc/rc.d/network to try all profiles. slower, but far more reliable than this setup.

iwlist is buggy for some cards, sometimes will not report available networks and doesnt list networks which do not advertise essid.

netcfg is internally undergoing a rewrite and included in this, is better detection support.
Comment by Christ Schlacta (aarcane) - Monday, 16 October 2006, 00:35 GMT
this patch was written against the current netcfg scripts pre-release, 0.1.99, the "rewrite" as it were. I made the patch for apeiro, but since I couldn't locate him, it was suggested to post it here. as for iwlist and it's unreliability, that can be resolved in a few ways:

first of all, autodetection is never 100%, but it always works better than none does

second: if the profiles were modified slightly to include an optional MAC address for networks without ESSID broadcast, that could be resolved, as well as a flag for AUTODETECT=1 and AUTODETECT_METHOD=MAC, ESSID etc.

iwlist is greatly more reliable on listing all available networks when you sleep 1 second before bringing it up.

The reason I chose to submit a version with an iwlist for EACH profile instead of once, or for each device is because some people have multiple cards for A, B/G, and N/M networks. I felt that to match any available MAC/ESSID against profiles would result in inconvenience to those people, and that a working version for everyone was better than a fast version for most, however that could be provided as well, or easily modified.

loading all network profiles results in alot of errors or malfunctions when you have multiple DHCP profiles in the area. they result in hanging on DHCP attempts, which the last time I had that occur, it took 60 seconds before it timed out. most cards result in no error when issuing IW commands if the AP doesn't exist and will associate without error.

Most cards DO work with IWLIST, however, it does have it's minor issues which could be easily worked around.

I still feel this is a valuable contribution, and would be much obliged if you could take this further information into consideration.
Comment by James Rayner (iphitus) - Saturday, 23 December 2006, 03:24 GMT
this will be included in the new scripts, which will have support for both the iwlist, and dhcp detections, with iwlist enabled by default under the name FAST_SCAN or something like that.

James

Loading...