This repository has been archived by the owner on Dec 15, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
/
README
107 lines (73 loc) · 3.39 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
This is the README file for netplug, a Linux daemon that responds to
network link events, such as a network interface losing or acquiring a
carrier signal.
You can use netplug to configure a network interface automatically
when you plug in a live network cable, and unconfigure the interface
when you unplug the cable.
Netplug is licensed under the GNU General Public License, version 2.
Copyright 2003 Pathscale, Inc.
Copyright 2003, 2004, 2005 Bryan O'Sullivan
What is netplug?
----------------
Linux already supports plugging in and configuring the likes of
Cardbus network interfaces, in the form of the hotplug subsystem.
Netplug provides the corresponding support for plugging and unplugging
cables into network interfaces.
When an Ethernet-style network interface on a host is plugged into a
powered-up switch, hub, or other host, the two use a carrier signal to
establish that the link is alive. The Linux kernel makes this
information available through its netlink interface.
The netplug daemon listens for carrier detection and loss messages
from the kernel's netlink subsystem. When a carrier signal is
detected on an interface, it runs a script to bring the interface up.
When carrier is lost, netplug runs a script to bring the interface
down.
Why use netplug?
----------------
If you use static IP addresses, or your host is always plugged into
the same port on the same network, there's not much benefit to using
netplug. Netplug comes into its own in two situations:
- If you're a laptop user who migrates from one network to another,
you can use netplug to automate the management of your network
interface as you unplug from one network and plug into another.
Without netplug, you are forced to manually run commands such as
"/sbin/ifup eth0" when you plug into a new network.
- If you have a large computing cluster, you may periodically need to
move hosts around to balance the loads among a collection of
switches and file servers. If you only need to move network
cabling, you can leave a host running, with its interfaces managed
by netplug, and netplug will reconfigure its interfaces when you
move the host from a busy switch to a less lightly loaded one.
Who ships netplug?
------------------
Netplug is distributed as part of the standard net-tools package with
the following Linux distributions:
Fedora Core 2 and above
Mandrake 10.1 and above
Red Hat Enterprise 4 and above
There are also packages available for Debian and Gentoo.
Adapting netplug for different situations
-----------------------------------------
The netplug daemon has no notion of policy or integration with a
particular Linux distribution. Those are abstracted out into a
script, /etc/netplug.d/netplug. This script is responsible for the
distro-dependent mechanics of:
- Probing for interfaces to manage
- Bringing an interface up, in response to carrier acquisition
- Bringing an interface down, in response to loss of carrier
Helping out
-----------
Patches to integrate with different Linux distributions, add features,
fix bugs, add documentation, and so on, are all welcome, as are
suggestions for improvements.
Master Mercurial repository:
hg clone http://hg.serpentine.com/netplug
Contact
-------
The author of netplug is Bryan O'Sullivan <[email protected]>.
Thanks
------
Thanks to the following people for their excellent work in making
netplug more robust:
Jeremy Fitzhardinge
Steve Grubb