netcfg3
netcfg2 has been out for long enough, and i’m looking towards netcfg3.
In netcfg3 I hope to fix all that things about netcfg2 that I think _suck_.
* Move from iwconfig -> wpa_supplicant
* Access wpa_supplicant via dbus rather than crappy autogen configs
* Replace all scanning and ‘detection’ code
* Move from ifconfig/route -> iproute
* Gut existing attempts at ‘automagic’ – they all suck.
* Distro independent
* Route handling
* Not break current profile config syntax (no promises)
* More detailed status output
As for feature additions:
* A better auto connection system, packaged separately
* Possibly a daemon of some sort to monitor connection state and act upon changes
* Closing of existing feature requests on Arch bug tracker
Small goals, but should make a significant difference. The implementation will be cleaner and more flexible.
hmm, are you rewriting NetworkManager??
дамјан
May 12, 2008 at 9:34 am
“* Possibly a daemon of some sort to monitor connection state and act upon changes”
This would be awesome. There really needs to be a console NetworkManager. You might want to look into wifiroamd, which is an attempt at just that.
Andrew
May 12, 2008 at 1:54 pm
Looking forward to this sooner rather than later
Jon
May 12, 2008 at 10:25 pm
Nice
But could you add suport for wvdial and ppp connections?
raca
May 14, 2008 at 4:48 am
“daemon to monitor connection state”?
you mean, like ifplugd?
lloeki
May 20, 2008 at 6:50 pm
also, I hope you will be keeping the unix philosophy of ‘one good tool for one precise task’ and not create some kitchensink. I really like how netcfg2 is barebones.
lloeki
May 20, 2008 at 10:42 pm
I’m not sure if this is something you want to implement or not, but I would like to see that you could execute certain commands for certain profiles. Like:
Connection A:
Mount a sshfs drive, mount a nfs drive, bring up a daemon …
Connection B:
Copy a file, sync a calendar …
If there’s a smarter way of doing this, it would be nice to find out …
Patogen
May 25, 2008 at 5:54 pm