In my custom network scripts, I offered a method of automatic detection of networks for all wireless cards, including those without scan ability.
http://iphitus.loudas.com/archinit.php would it be possible to implement something like this? I ran using multiple entries in lilo in the past, and i disliked it, because i was eternally forgetting to choose the right profile. These scripts work automatically, they connect to the wireless network, but they dont try and get an IP untill they actually know the network exists. It checks if the network exists by checking if an Access Point of Cell (adhoc) has been associated with succesfully. Every wireless card I've ever used, even the ndiswrapped ones display the AP/Cell. It's not hard, just grep the output of iwconfig for 00:00:00:00:00:00, which is the Access Point/Cell it displays when it hasnt associated with one, if it's there then we know, that the network isnt available here. It's good to wait a second or two before grepping iwconfig, to give the network card time to associate, if the network does exist. My method keeps the INTERFACE/ROUTES setup and adds the wireless onto it. IMHO, if we are going to do anything to the network setup, we should revamp it with full profile support and get it working right at the start, similar to debian's. Hope this is of some use... James Rayner On 7/1/05, Judd Vinet <[EMAIL PROTECTED]> wrote: > Hey guys, > > I've made another attempt at hacking up some roaming network profiles. > > I wanted a system that could be used on top of the existing network > config in rc.conf. I saw some profile implementations that were nice, > but they actually replaced the existing INTERFACES/ROUTES setup in > rc.conf. The goal here was to keep the INTERFACES/ROUTES setup in > place, since one of Arch's most cited features is the easy > "all-in-one-file" configuration in rc.conf. I didn't want to lose that. > > The current setup is intended for laptop users who require multiple > profiles. It's not as flexible or powerful as the rc.conf network > setup, but it should suffice for most laptop/wireless users (works well > for me, anyway). > > Here's a quick setup howto: > > - In rc.conf, remove your wireless interfaces from INTERFACES and any > relevant routes from ROUTES. Leave "lo" stuff in place. > - Add a NET_PROFILES array to rc.conf and in it, put the name of the > profile(s) you wish to start at bootup. Profiles are found in > /etc/network-profiles. > > That's it, pretty much. When rc.d/network is started, it will look for > a non-empty NET_PROFILES array, and if found, it will use the netcfg > script to activate them. You can also set NET_PROFILES to "menu" and it > will present a dialog/ncurses menu at bootup where you can pick the > profile you want. Alternatively, you can pass a NET= value on the > kernel boot line, telling netcfg which profile you wish to start with. > > eg, vmlinuz root=/dev/hda3 vga=773 devfs=nomount ro NET=school > > A new initscripts package is available in Testing. If you are a > wireless laptop user, please try it out and give me some feedback. > > > - J > > > _______________________________________________ > arch mailing list > [email protected] > http://www.archlinux.org/mailman/listinfo/arch > -- iphitus - www.iphitus.tk _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
