..I should explain where I'm coming from: I'm writing a wireless configuration
daemon with the following capabilities:
- support for multiple APs
- automatic detection of in-range APs and network reconfiguration
- capability of automatic reconfig of the network (transparently ?) in
certain situations (i.e. laptop moved, AP went down etc.)
- capability to connect to "non-preferred" (?) APs (e.g. once off cafes)
The end result of this will be a config rc script and a binary daemon. One can
see the similarity with netapplet/netdaemon..
My reasons for doing it are (in no particular order):
- d-bus looks promising (don't know if it's over-hyped)
- windows has it
- i'm tired of copying files ifup/ifdown and changing profiles
- none of the alternatives I've looked at cover the auto-part. so if your
place has multiple APs and your fav one goes belly-up (it happened to me
quite a few times now), you need to get a new profile up... and so on.
The config would be generated by a GUI and read/used by a binary and needs to
have at least 2 hierarchical levels. ..and that's why I thought of XML :)
L
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!