Thanks to all for the suggestions, will look at the details later. I don't have time to build LFS, let alone a desktop, on this machine at the moment (it's an atom, with only 1GB, so *slow*, and I want to use it on my hols next week - hopefully with wifi). So, I'll want the ability to use wifi when I'm away.
I also had a reply off-list suggesting that turning off the wifi in n-m would do the job - thought I'd tried that already, but possibly I lost it during a reboot after hibernate trashed the screen - and to remove the networks from within n-m using 'Edit Connections' - for the moment, it is behaving itself. Thanks again. ĸen On 07/06/2011, Dominic Ringuet <[email protected]> wrote: > On Mon, Jun 6, 2011 at 9:12 PM, Ken Moffat <[email protected]> wrote: > >> Technically, this is somewhat OT because I've got ubuntu installed >> on my new netbook at the moment, but since google doesn't have any >> answers, I'll try asking here... >> >> My netbook has wifi, so I'll need network-manager to use it. But, >> I don't have wifi at the moment, just wired ethernet. Using nutty >> narwhale, I keep getting dialogs because network-manager is trying >> to connect to the several wireless networks it can see. Is there >> any way to tell it "when I'm at home, do not try to connect to the >> following networks ..." ? In theory, wifi is turned off via the >> function key, but in practice, like the brightness keys, on this >> machine the key appears to work but in practice doesn't do anything. >> >> The box came with win7 (as unusable as I had imagined, but with a >> concept of "location" for network, so that I can tell it "at >> home, use the wired network"). >> >> For the moment, I can live with the extra power consumption of the >> wifi circuits, but the random invitations to enter access keys for >> networks after I wake it drive me crazy, and when I *do* have my own >> wifi I won't want to be prompted to connect to one of my neighbours' >> systems. >> > > Sometimes ago, I used Ubuntu around letter "i" as a bridge (as a router in > fact) to reach an access point too far away. To Network Manager, the > required configuration seemed out of the scope. Also, the drivers and tools > where quite immature as the madwifi project transmutated into athXk. > > The ~easy solution has been a bash script in runlevel 3, first; killing > network manager and whatever relatives he might have. Second; unloading all > kernel modules related to the network cards (it also brought down the > antenna). Then finally; modprobe, iwconfig, ifconfig, route add and all from > grounds up in proper order. For your purpose, you can easily make the script > aware of it's location at boot time using iwlist|grep, ping or 2 different > scripts/icons. > > Be warned that in the process, you'll loose your ability to easily connect > via popup to any wireless networks showing up around. IMO, a textfile > containing the relevant AP, MAC and keys is more suitable. > > Dominic. > -- After tragedy, and farce, "OMG poneys!" -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
