|
| Link: Link
Downloads: 4191
| Submitted: Mar 31 2008
Updated: Nov 18 2009
| |
Description:
Update:
* [nuts] added support for wildcard and regexp device names
* [libnut*] switch to dynamic linked client library
+ added development lib
* [qnut] made settings more "standardized"
+ added support for compile flag to be not compatible with old settings: QNUT_SETTINGS_NOCOMPAT
* [qnut] changed scripting settings to more general device settings
+ device details cleanup
+ Former scripts witch were executed on device state change are substituted by command lists. In each list the user can now specify witch commands will be executed and each entry can either be a specific command or a directory with executables.
* some gerenal polishing, cleanup and as always: bugfixes
What NUT does:
* manages your network devices (dhcp with fallback, static, zeroconf); currently only supports IPv4 on Linux
* executes admin and user defined scripts for each device state
* manages your wireless connections (WPA supplicant)
* supports multiple network configurations (environments) for each device
* supports multiple ip-addresses (interfaces) for each environment
The idea behind:
If you have different working places, for example at home and university you have to mount network shares etc. manualy.
With NUT you don't have to do that anymore.
You can define environments that get selected by the server according to different statements.
So far the following statements are supported:
check for essid, check for ip, check for ip with mac-address.
Those statements can be combined with boolean operators.
Every time an event occures, scripts are executed accordingly (like the /etc/network scripts in debian).
The follwing events exist:
device state change: deactivated, activated, carrier, unconfigured, up
interface changes (admin only): ifup/ifdown,deactivated, activated, carrier, unconfigured, up
Requires:
* Qt 4.x (>= 4.4.0 recommended) with D-Bus support
* resolvconf
* libnl (server): please use stable version 1.1 (from http://people.suug.ch/~tgr/libnl/)
* libiw (client)
Consists of 6 Parts:
* nuts: Server
* libnutcommon: Library needed from server and client (static)
* libnutclient: Client library (static)
* libnutwireless: Client library for wpa_supplicant (static)
* qnut: Graphical client
* cnut: Console client
For some more general information have a look in this gentoo forum thread:
http://forums.gentoo.org/viewtopic-t-631415.html
See the download section for a config example for nuts.
Gentoo related:
Nut is also in the devnull overlay. To add it (using layman) do the following:
# layman -f && layman -a devnull
(Further instructions at http://devnull.core.ws/EbuildRepository)
To get an tagged version, just rename the ebuild to net-misc/nut-"version" (i.e. net-misc/nut-0.5.0)
Arch-Linux
An installation how-to for arch can be found at:
http://chakra-project.org/wiki/index.php/Get_NET_with_NUT
Known bugs:
* a fallback timeout of less than 10 seconds does not work (you can specify a timeout of less than 10 seconds but it's going to be ignored and set to 10 seconds)
* the new wlan stack isn't supported yet. Due to the almost non-existing compatibility between the old and new wlan stack, scanning for networks returns wrong results. All other wlan related things should work
Feel free to contact us if you find other bugs.
License: GPL
|
| |
Add commentBack
|
