netcfg v2.1.0 beta 2
What happened to beta 1? It wasn’t properly released, it was too messy.
This release is just to stabilise netcfg2 a bit more before I really consider netcfg v3
Source Downloads
Packages will be in [testing] in the next 48 hours.
netcfg v2.1.0 beta 2
- Remove driver specific hacks/quirks, and require them to be opt-in via config option (see wireless.subr)
- Separate automagic connection code from net-profiles
- Fix various bug
- Add option to run iwconfig with whatever arguments before connecting (all wireless setups)
More details on the netcfg2 git branch on projects.archlinux.org
In other news my wireless card is sick, it does this intermittently. A quick search on LKML and a few other places found no other cards experiencing this.
From dmesg…
ipw2100: exit - failed to send CARD_DISABLE command
....
ipw2100: ipw0: No response from Symbol - hw not alive
ipw2100: ipw0: Error loading microcode: -5
ipw2100: ipw0: Failed to power on the adapter.
ipw2100: ipw0: Failed to start the firmware.
Oh and the questions:
raca: But could you add suport for wvdial and ppp connections?
ppp support is in netcfg2 already, have a look at the example config. If you’d like more, post a feature request on the Arch Bug Tracker
lloeki: also, I hope you will be keeping the unix philosophy of ‘one good tool for one precise task’ and not create some kitchensink
Definitely keeping the one tool philosophy. That’s one reason why the automagic connection stuff has been separated out.
Patogen: I would like to see that you could execute certain commands for certain profiles
Already there. Have a look at the PRE_UP/POST_UP PRE_DOWN/POST_DOWN options. You can set either a path to a script, or just some commands separated by semicolons.
Is it too late to add a question about netcfg v3? I’d love to know if I’m going to have to teach my fingers anew to start typing netcfg3, when I’m only just starting to get used to netcfg2 instead of netcfg. I’m still getting told “sudo: netcfg: command not found” more often than I’d like. Are there really people who want to keep multiple versions of netcfg installed, such that you need to differentiate the command names?
I guess what I’m really wondering is if there’s any chance netcfg v3 will move back to being /usr/bin/netcfg, or if 5 years from now we’ll be typing netcfg42.
potatoe
June 2, 2008 at 4:38 am
Must have missed that. Sorry, netcfg is a great tool! I don’t know any way you could make it better (for me at least). It’s perfect.
Patogen
June 23, 2008 at 7:39 am