Section: Network management daemons (8)
NetworkManager will execute scripts in the /etc/NetworkManager/dispatcher.d directory or subdirectories in alphabetical order in response to network events. Each script should be a regular executable file owned by root. Furthermore, it must not be writable by group or other, and not setuid.
Each script receives two arguments, the first being the interface name of the device an operation just happened on, and second the action.
The actions are:
The environment contains more information about the interface and the connection. The following variables are available for the use in the dispatcher scripts:
IP6_<name> and DHCP6_<name>
In case of VPN, VPN_IP_IFACE is set, and IP4_*, IP6_* variables with VPN prefix are exported too, like VPN_IP4_ADDRESS_0, VPN_IP4_NUM_ADDRESSES.
Dispatcher scripts are run one at a time, but asynchronously from the main NetworkManager process, and will be killed if they run for too long. If your script might take arbitrarily long to complete, you should spawn a child process and have the parent return immediately. Also beware that once a script is queued, it will always be run, even if a later event renders it obsolete. (Eg, if an interface goes up, and then back down again quickly, it is possible that one or more "up" scripts will be run after the interface has gone down.)
The following options are understood:
--version | -V
--help | -h
--no-daemon | -n
--debug | -d
--pid-file | -p
The following environment variables are supported to help debugging. When used in conjunction with the --no-daemon option (thus echoing PPP and DHCP helper output to stdout) these can quickly help pinpoint the source of connection issues. Also see the --log-level and --log-domains to enable debug logging inside NetworkManager itself.
Tutoriais de Tecnologia Web