Codebase list network-manager / 83d084c
Rename README.Debian to network-manager.README.Debian make it obvious that it is only installed for the network-manager binary package git-svn-id: svn+ssh://svn.debian.org/svn/pkg-utopia/packages/unstable/networkmanager@1318 ceb527fc-18e6-0310-9fe2-813c157c29e7 Michael Biebl 17 years ago
2 changed file(s) with 76 addition(s) and 76 deletion(s). Raw diff Collapse all Expand all
+0
-76
debian/README.Debian less more
0 NetworkManager consists of two parts: one is on the system level daemon that
1 manages the connections and gathers information about new networks. The other
2 is a systray applet that users can use to interact with the NetworkManager
3 daemon.
4
5 Security
6 ~~~~~~~~
7 To allow users to connect to the NetworkManager daemon they have to be in the
8 group "netdev". If you want to add a user to group "netdev" use the command
9 "adduser username netdev" or one of the graphical user management frontends.
10 After that you have to reload D-Bus with the command "/etc/init.d/dbus reload".
11
12 Configuration of wireless and ethernet interfaces
13 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
14 Only devices that are *not* listed in /etc/network/interfaces or which have
15 been configured "auto" and "dhcp" (with no other options) are managed by NM.
16
17 This way you can setup a custom (static) configuration for a device and NM
18 will not try to override this setting.
19
20 After modifying /etc/network/interfaces you have to restart NM with the
21 command "/etc/dbus-1/event.d/25NetworkManager restart".
22
23 Examples:
24
25 1.)
26 auto wlan0
27 iface wlan0 inet dhcp
28 -> This device is managed by NM.
29
30 1.a)
31 allow-hotplug eth0
32 iface eth0 inet dhcp
33 -> This device is managed by NM
34
35 2.)
36 auto wlan0
37 iface wlan0 inet dhcp
38 wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
39 -> This devices is *not* managed by NM because it has additional options.
40
41 3.)
42 iface wlan0 inet dhcp
43 -> This device is *not* managed by NM because it is not set to "auto".
44
45 4.)
46 iface eth0 inet static
47 address 192.168.1.10
48 netmask 255.255.255.0
49 gateway 192.168.1.1
50 -> This device is *not* managed by NM because it is configured as "static" and
51 has additional options.
52
53 5.)
54 Device is not listed in /etc/network/interfaces.
55 -> Device is managed by NM.
56
57 Dial-up configuration
58 ~~~~~~~~~~~~~~~~~~~~~
59 After configuring your PPP interface (either manually or by using a tool like
60 "pppconfig") to work with a peer called "myisp" you should edit
61 /etc/network/interfaces and add a stanza like this:
62
63 iface ppp0 inet ppp
64 provider myisp
65
66 NM will then make it possible to dial this connection.
67 If you want to set up multiple internet service providers simply create a new
68 stanza as listed above specifying the provider and a different iface, e.g. ppp1.
69
70 After modifying /etc/network/interfaces you have to restart NM with the
71 command "/etc/dbus-1/event.d/25NetworkManager restart".
72
73 Please read the "Debian Reference Manual", section 10.6.1.4 or the "interfaces"
74 man page for further information.
75
+76
-0
debian/network-manager.README.Debian less more
0 NetworkManager consists of two parts: one is on the system level daemon that
1 manages the connections and gathers information about new networks. The other
2 is a systray applet that users can use to interact with the NetworkManager
3 daemon.
4
5 Security
6 ~~~~~~~~
7 To allow users to connect to the NetworkManager daemon they have to be in the
8 group "netdev". If you want to add a user to group "netdev" use the command
9 "adduser username netdev" or one of the graphical user management frontends.
10 After that you have to reload D-Bus with the command "/etc/init.d/dbus reload".
11
12 Configuration of wireless and ethernet interfaces
13 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
14 Only devices that are *not* listed in /etc/network/interfaces or which have
15 been configured "auto" and "dhcp" (with no other options) are managed by NM.
16
17 This way you can setup a custom (static) configuration for a device and NM
18 will not try to override this setting.
19
20 After modifying /etc/network/interfaces you have to restart NM with the
21 command "/etc/dbus-1/event.d/25NetworkManager restart".
22
23 Examples:
24
25 1.)
26 auto wlan0
27 iface wlan0 inet dhcp
28 -> This device is managed by NM.
29
30 1.a)
31 allow-hotplug eth0
32 iface eth0 inet dhcp
33 -> This device is managed by NM
34
35 2.)
36 auto wlan0
37 iface wlan0 inet dhcp
38 wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
39 -> This devices is *not* managed by NM because it has additional options.
40
41 3.)
42 iface wlan0 inet dhcp
43 -> This device is *not* managed by NM because it is not set to "auto".
44
45 4.)
46 iface eth0 inet static
47 address 192.168.1.10
48 netmask 255.255.255.0
49 gateway 192.168.1.1
50 -> This device is *not* managed by NM because it is configured as "static" and
51 has additional options.
52
53 5.)
54 Device is not listed in /etc/network/interfaces.
55 -> Device is managed by NM.
56
57 Dial-up configuration
58 ~~~~~~~~~~~~~~~~~~~~~
59 After configuring your PPP interface (either manually or by using a tool like
60 "pppconfig") to work with a peer called "myisp" you should edit
61 /etc/network/interfaces and add a stanza like this:
62
63 iface ppp0 inet ppp
64 provider myisp
65
66 NM will then make it possible to dial this connection.
67 If you want to set up multiple internet service providers simply create a new
68 stanza as listed above specifying the provider and a different iface, e.g. ppp1.
69
70 After modifying /etc/network/interfaces you have to restart NM with the
71 command "/etc/dbus-1/event.d/25NetworkManager restart".
72
73 Please read the "Debian Reference Manual", section 10.6.1.4 or the "interfaces"
74 man page for further information.
75