So how do I do this ? I want the machine to figure out whether X or Y is available on its own (whether I am at home or at work) without me telling it and I want any hostname changes not to mess up display. If in the process it comes across other networks, it should just ignore them. If I need to connect to them, I can do *that* manually.
I saw an interesting approach to this on bugzilla, you might want to have a look at that although it is more of an RFE than an actual bug. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=132661 That does sound like something like what you are after though.
That is actually my patch, glad somebody took notice. ;-). I have an updated version that I haven't submitted yet, that cleans up a lot of the parsing and has some security precautions in it. I should have that update this week.
Unfortunately my patch won't help people trying to connect to accesspoints with non-broadcast ESSIDS. I actually specifically exclude those from my scanned ap list. I have thought about how to include support this case, but haven't come up with a sure fire method.
My best idea would be to use the iwlist ap command to get the HW addresses of available access points and then look for ACCESSPOINT=value in the different ifcfg- scripts. The big drawback with this, is to properly implement it system-config-network would have to be changed to add an ACCESSPOINT option under the wireless config. This should not be too hard, but I haven't had the time in the last week to really get my hands dirty.
If people are interested in this funtionality please let me know. I definitely see this as a place where linux in general is a bit behind the curve.
-Jon
Unfortunately my patch won't help people trying to connect to accesspoints with non-broadcast ESSIDS. I actually specifically exclude those from my scanned ap list. I have thought about how to include support this case, but haven't come up with a sure fire method.
My best idea would be to use the iwlist ap command to get the HW addresses of available access points and then look for ACCESSPOINT=value in the different ifcfg- scripts. The big drawback with this, is to properly implement it system-config-network would have to be changed to add an ACCESSPOINT option under the wireless config. This should not be too hard, but I haven't had the time in the last week to really get my hands dirty.
If people are interested in this funtionality please let me know. I definitely see this as a place where linux in general is a bit behind the curve.
There is a definite niche for this sort of functionality. I believe it will be at least partly addressed by NetworkManager in FC3. Kwifi manager also allows for multiple profiles to be set up and is also, AFIK, going to be included in FC3.
Bests, Jon ----
<((((º>`·.¸¸.·´¯`·.¸.·´¯`·...¸><((((º>¸.
·´¯`·.¸. , . .·´¯`·.. ><((((º>`·.¸¸.·´¯`·.¸.·´¯`·...¸><((((º>>