By user12820842 on Sep 24, 2008
The Network Auto-Magic project, which aims to simplify and automate network configuration needs to do a couple of things:
- catch, handle (and sometimes generate) network-related events, handling transitioning from one network environment to another etc.
- provide a data repository for configuration preferences for various network environments, with a set of default preferences that lean towards automatic configuration (e.g. use DHCP to get an address)
- provide a set of user interfaces to allow for manual configuration as well as inspection of network state
This high-level description maps quite nicely onto the set of core components we plan to deliver for phase 1 of NWAM:
- nwamd - the core daemon at the heart of network autoconfiguration. It is this daemon's job to handle network-related events, assess network conditions and respond to changes in conditions
- libnwam is the library that provides storage of NWAM-related configuration
- Finally commandline tools such as nwamcfg and nwamadm and the GUI component of NWAM allow user interaction with network configuration
In a follow-up set of blog posts, I'm going to try and describe these components, starting with the set of events that nwamd needs to monitor and respond to and how that is (and will be) done.
In the meantime, why not give NWAM phase 0.5 a try - it alleviates many of the usability issues that applied to NWAM and works really nicely. Kudos to Jim and Darren (and Michael for his work on spec'ing out a set of candidate solutions to usability issues).