NetworkManager man page on Scientific

Man page or keyword search:  
man Server   26626 pages
apropos Keyword Search (all sections)
Output format
Scientific logo
[printable version]

NETWORKMANAGER(8)					     NETWORKMANAGER(8)

NAME
       NetworkManager - network management daemon

SYNOPSIS
       NetworkManager		[--no-daemon]	       [--pid-file=<filename>]
       [--state-file=<filename>]    [--config=<filename>]    [--plugins=<plug‐
       in1>,plugin2>,...]				 [--log-level=<level>]
       [--log-domains=<domain1>,<domain2>,...]

DESCRIPTION
       The NetworkManager daemon attempts to  make   networking	 configuration
       and  operation  as  painless  and automatic as possible by managing the
       primary network connection and other network interfaces, like Ethernet,
       WiFi,  and  Mobile  Broadband devices.  NetworkManager will connect any
       network device when a connection for  that  device  becomes  available,
       unless  that  behavior  is  disabled.   Information about networking is
       exported via a D-Bus interface to any interested application, providing
       a rich API with which to inspect and control network settings and oper‐
       ation.

       NetworkManager will execute  scripts  in	 the  /etc/NetworkManager/dis‐
       patcher.d  directory  in	 alphabetical  order  in  response  to network
       events.	Each script should be (a) a regular file, (b) owned  by	 root,
       (c) not writable by group or other, (d) not set-uid, (e) and executable
       by the owner.  Each script receives two arguments, the first being  the
       interface name of the device just activated, and second an action.

       up     The interface has been activated.	 The environment contains more
	      information about the interface;	CONNECTION_UUID	 contains  the
	      UUID of the connection.  Other variables are IP4_ADDRESS_N where
	      N is a number from 0 to (# IPv4 addresses - 1),  in  the	format
	      "address/prefix gateway".	 IP4_NUM_ADDRESSES contains the number
	      addresses the script may	expect.	  IP4_NAMESERVERS  contains  a
	      space-separated  list  of	 the DNS servers, and IP4_DOMAINS con‐
	      tains a space-separated list of the search domains.  Routes  use
	      the  format  IP4_ROUTE_N	where  N is a number from 0 to (# IPv4
	      routes - 1), in the format "address/prefix next-hop metric", and
	      IP4_NUM_ROUTES  contains the number of routes to expect.	If the
	      connection used DHCP for	address	 configuration,	 the  received
	      DHCP  configuration  is passed in the environment using standard
	      DHCP   option    names,	 prefixed    with    "DHCP4_",	  like
	      "DHCP4_HOST_NAME=foobar".

       down   The interface has been deactivated.

       vpn-up A	 VPN  connection has been activated.  The environment contains
	      the connection UUID in the variable CONNECTION_UUID.

       vpn-down
	      A VPN connection has been deactivated.

       hostname
	      The system hostname has been  updated.   Use  gethostname(2)  to
	      retrieve it.

       dhcp4-change
	      The DHCPv4 lease has changed (renewed, rebound, etc).

       dhcp6-change
	      The DHCPv6 lease has changed (renewed, rebound, etc).

OPTIONS
       The following options are supported:

       --no-daemon
	      Do not daemonize.	 This is useful for debugging, and directs log
	      output to the controlling terminal in addition to syslog.

       --pid-file=<filename>
	      Specify location of a PID file.  The PID file is used for	 stor‐
	      ing  PID	of  the running proccess and prevents running multiple
	      instances.

       --state-file=<filename>
	      Specify file for storing state  of  the  NetworkManager  persis‐
	      tently.	If  not	 specified, the default value of '<LOCALSTATE‐
	      DIR>/lib/NetworkManager/NetworkManager.state'  is	 used;	 where
	      <LOCALSTATEDIR>  is dependent on your distribution (usually it's
	      /var).

       --config=<filename>
	      Specify configuration file to set up various settings  for  Net‐
	      workManager.    If   not	 specified,   the   default  value  of
	      '<SYSCONFDIR>/NetworkManager/NetworkManager.conf' is used with a
	      fallback	to  the	 older 'nm-system-settings.conf' if located in
	      the same directory; where <SYSCONFDIR> is dependent on your dis‐
	      tribution	 (usually  it's /etc).	See NetworkManager.conf(5) for
	      more information on configuration file.

       --plugins=<plugin1>,<plugin2>, ...
	      List plugins used to  manage  system-wide	 connection  settings.
	      This  list has preference over plugins specified in the configu‐
	      ration  file.   Currently	 supported   plugins   are:   keyfile,
	      ifcfg-rh,	 ifcfg-suse, ifupdown.	See NetworkManager.conf(5) for
	      more information on the plugins.

       --log-level=<level>
	      Sets how much information NetworkManager sends to the log desti‐
	      nation  (usually	syslog's "daemon" facility).  By default, only
	      informational, warning, and error messages are logged.  See Net‐
	      workManager.conf(5)  for	more  information  on  log  levels and
	      domains.

       --log-domains=<domain1>,<domain2>, ...
	      Sets which operations are logged to the log destination (usually
	      syslog).	 By  default,  most  domains are logging-enabled.  See
	      NetworkManager.conf(5) for more information on  log  levels  and
	      domains.

DEBUGGING
       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.

       NM_PPP_DEBUG
	      When  set	 to  anything,	causes	NetworkManager	to turn on PPP
	      debugging in pppd, which	logs  all  PPP	and  PPTP  frames  and
	      client/server exchanges.

SEE ALSO
       nm-tool(1), NetworkManager.conf(5).

			       January 29, 2010		     NETWORKMANAGER(8)
[top]

List of man pages available for Scientific

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net