1
.TH ifup 8 "5 April 2004" IFUPDOWN ""
1
.TH ifup 8 "22 May 2004" IFUPDOWN ""
3
3
ifup \- bring a network interface up
5
5
ifdown \- take a network interface down
8
.BI "[\-nv] [\-i " FILE "|\-\-interfaces=" FILE "] [\-\-no\-act]"
9
.BI "[\-\-verbose] [\-a|" IFACE "]..."
11
[\fB\-i\fR \fIFILE\fR|\fB\-\-interfaces=\fR\fIFILE\fR]
12
[\fB\-e\fR \fIFILE\fR|\fB\-\-exclude=\fR\fIIFACE\fR]
13
\fB\-a\fR|\fIIFACE\fR...
16
\fB\-h\fR|\fB\-\-help\fR
19
\fB\-V\fR|\fB\-\-version\fR
12
.BI "[\-nv] [\-i " FILE "|\-\-interfaces=" FILE "] [\-\-no\-act]"
13
.BI "[\-\-verbose] [\-a|" IFACE "]..."
25
[\fB\-i\fR \fIFILE\fR|\fB\-\-interfaces=\fR\fIFILE\fR]
26
[\fB\-e\fR \fIFILE\fR|\fB\-\-exclude=\fR\fIIFACE\fR]
27
\fB\-a\fR|\fIIFACE\fR...
16
30
.BR ifup " and " ifdown
21
35
A summary of options is included below.
23
.BR "\-h" ", " "\-\-help"
24
Show summary of options.
26
.BR "\-V" ", " "\-\-version"
27
Show copyright and version information.
29
.BR "\-a" ", " "\-\-all"
30
38
If given to \fBifup\fP, affect all interfaces marked \fBauto\fP.
31
39
Interfaces are brought up in the order in which they are defined
32
40
in /etc/network/interfaces.
33
If given to \fBifdown\fP, affect all interfaces.
41
If given to \fBifdown\fP, affect all defined interfaces.
34
42
Interfaces are brought down in the order in which they are
35
currently listed in the state file.
37
.BI "\-i " FILE ", \-\-interfaces " FILE
43
currently listed in the state file. Only interfaces defined
44
in /etc/network/interfaces will be brought down.
45
Note that you can exclude some interfaces from being handled in this
50
Force configuration or deconfiguration of the interface.
53
Show summary of options.
55
\fB\-i\fR \fIFILE\fR, \fB\-\-interfaces=\fR\fIFILE\fR
38
56
Read interface definitions from
40
58
instead of from /etc/network/interfaces.
42
.BR "\-v" ", " "\-\-verbose"
43
Show commands as they are executed.
60
\fB\-e\fR \fIIFACE\fR, \fB\-\-exclude=\fR\fIIFACE\fR
61
Exclude a given interface
63
from being managed when doing an operation
64
that involves a number of interfaces. It can only be given one
65
string which is supposed to be an interface name. You can
66
exclude more than one interface if the name
67
given is a substring shared by all of them (for example
69
will exclude all ethernet interfaces)
70
This option is useful to avoid running "up" or "down"
71
commands for some interfaces when using
45
.BR "\-n" ", " "\-\-no\-act"
74
.BR \-n ", " \-\-no\-act
46
75
Don't configure any interfaces or run any "up" or "down" commands.
49
78
Don't run any mappings. See
51
80
for more information about the mapping feature.
54
Force configuration or deconfiguration of the interface.
82
.BR \-V ", " \-\-version
83
Show copyright and version information.
85
.BR \-v ", " \-\-verbose
86
Show commands as they are executed.
90
Bring up all the interfaces defined with
93
.I /etc/network/interfaces
106
Bring down all the interfaces defined with
109
.I /etc/network/interfaces
110
except for those that begin with
57
113
.BR ifup " and " ifdown
58
programs don't know much about configuring interfaces;
59
they run low level utilities such as
114
are actually the same program called by different names.
116
The program does not configure network interfaces directly;
117
it runs low level utilities such as
60
118
.BR ifconfig " and " route
61
to do their dirty work. One of the main advantages to using
62
.BR ifup " and " ifdown
63
instead of calling the low level utilities directly is that
64
.BR ifup " and " ifdown
65
allow you to keep all your interface specifications in a single
119
to do its dirty work.
69
122
.I /etc/network/interfaces
75
128
.I /etc/network/ifstate
76
129
current state of network interfaces
77
130
.SH KNOWN BUGS/LIMITATIONS
78
In some cases, the state maintained by
83
.I /etc/network/ifstate
84
might be inconsistent with the actual state of the interfaces.
85
If this happens, you might need to either modify the state file
86
directly or manually configure/deconfigure interfaces using
92
.I /etc/network/ifstate
93
file must be writable. In particular, you will not be able to run
99
is mounted read-only (for example, during a system recovery). A work-around
100
for this issue (reported in Debian bug #84074) is to make
101
.B /etc/network/ifstate
102
a symbolic link to a writable location.
106
program itself does not automatically bring up interfaces
131
The program keeps records of whether network interfaces are up or down.
132
Under exceptional circumstances these records can become
133
inconsistent with the real states of the interfaces.
134
For example, an interface that was brought up using
136
and later deconfigured using
138
will still be recorded as up.
139
To fix this you can use the
145
to run configuration or deconfiguration commands despite what
146
it considers the current state of the interface to be.
149
.I /etc/network/ifstate
155
If that location is not writable
156
(for example, because the root filesystem is mounted read-only
159
.I /etc/network/ifstate
160
should be made a symbolic link to a writable location.
161
If that is not possible then you can use the
163
option to run configuration or deconfiguration commands
164
without updating the file.
166
Note that the program does not run automatically:
168
alone does not bring up interfaces
107
169
that appear as a result of hardware being installed and
109
does not automatically bring down interfaces
171
alone does not bring down interfaces
110
172
that disappear as a result of hardware being removed.
111
If you want to monitor interface state changes you might want to
112
consider installing also
173
To automate the configuration of network interfaces you need to
174
install other packages such as
116
Note that the improper use of
120
can result in deadlock between them as described in Debian bug #231197.
122
179
The ifupdown suite was written by Anthony Towns <aj@azure.humbug.org.au>.
added
removed
ifup.8
