1
.TH ifupdown 8 "February 13, 2000"
3
ifup \- bring a network interface up
5
ifdown \- take a network interface down
8
.BI "[-sinv] [--interfaces=" file "] [--no-act]"
9
.BI "[--verbose] [-a|" ifaces "]"
12
.BI "[-sinv] [--interfaces=" file "] [--no-act]"
13
.BI "[--verbose] [-a|" ifaces "]"
16
.BR ifup " and " ifdown
17
commands may be used to configure (or, respectively, deconfigure) network
18
interfaces, based on descriptions of the interfaces entered into the file
19
.IR /etc/network/interfaces .
21
These programs follow the usual GNU command line syntax, with long
22
options starting with two dashes (`-').
23
A summary of options is included below.
26
Show summary of options.
29
Show copyright and version information.
32
Affect all interfaces marked \fBauto\fP.
34
.BR "-i" " file" ", --interfaces" " file"
35
Read interface definitions from a different file.
38
Show commands being executed.
41
Don't actually execute the commands (this doesn't disable mappings, however)
44
Don't run any mappings.
47
Force de/configuration of interface.
50
.BR ifup " and " ifdown
51
programs don't actually know anything about configuring interfaces themselves
52
but instead invoke lower-level utilities such as
53
.BR ifconfig " and " route
54
to do the actual dirtywork. The main advantages to using
55
.BR ifup " and " ifdown
56
instead of calling the lower-level utilities directy is the ability to
57
keep all your interface specifications in a single (easily parsable) file,
58
and to not have to deal with the various idiosyncracies of the lower-level
62
.B /etc/network/interfaces
63
Descriptions of all the network interfaces the system has.
65
.B /etc/network/ifstate
66
Current state of network interfaces.
68
The ifupdown suite written by Anthony Towns <aj@azure.humbug.org.au>.
added
removed
ifup.8
