]> git.ipfire.org Git - people/ms/network.git/blob - man/network-zone.xml
Implement using Linux's SMP affinity
[people/ms/network.git] / man / network-zone.xml
1 <?xml version="1.0"?>
2 <!DOCTYPE refentry PUBLIC "-//OASIS/DTD DocBook XML V4.2//EN"
3 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
4
5 <refentry id="network-zone">
6 <refentryinfo>
7 <title>network-zone</title>
8 <productname>network</productname>
9
10 <authorgroup>
11 <author>
12 <contrib>Developer</contrib>
13 <firstname>Michael</firstname>
14 <surname>Tremer</surname>
15 <email>michael.tremer@ipfire.org</email>
16 </author>
17 </authorgroup>
18 </refentryinfo>
19
20 <refmeta>
21 <refentrytitle>network-zone</refentrytitle>
22 <manvolnum>8</manvolnum>
23 </refmeta>
24
25 <refnamediv>
26 <refname>network-zone</refname>
27 <refpurpose>Network Configuration Control Program</refpurpose>
28 </refnamediv>
29
30 <refsynopsisdiv>
31 <cmdsynopsis>
32 <command>network zone <arg choice="plain">[new|destroy]</arg> <replaceable>ZONE</replaceable> ...</command>
33 </cmdsynopsis>
34
35 <cmdsynopsis>
36 <command>network zone <replaceable>ZONE</replaceable> <arg choice="plain">command</arg> ...</command>
37 </cmdsynopsis>
38 </refsynopsisdiv>
39
40 <refsect1>
41 <title>Description</title>
42
43 <para>
44 With help of the <command>zone</command> command, it is very easy to
45 configure network zones.
46 </para>
47 <para>
48 It is possible to create zones and remove them. Zones may also
49 be brought up and down and reconfigured. Their status may be viewed
50 as well.
51 </para>
52 </refsect1>
53
54 <refsect1>
55 <title>Commands</title>
56
57 <para>
58 The following commands are understood:
59 </para>
60
61 <variablelist>
62 <varlistentry>
63 <term>
64 <command>new <replaceable>ZONE</replaceable> <replaceable>HOOK</replaceable> <arg choice="opt" rep="repeat">OPTIONS</arg></command>
65 </term>
66
67 <listitem>
68 <para>
69 A new zone may be created by the <command>create</command>
70 command. There are at least two arguments required.
71 </para>
72 <para>
73 <replaceable>ZONE</replaceable> must be valid name for a
74 zone which does not already exist.
75 <replaceable>HOOK</replaceable> is a valid zone hook which
76 may require additional options.
77 </para>
78 </listitem>
79 </varlistentry>
80
81 <varlistentry>
82 <term>
83 <command>destroy <replaceable>ZONE</replaceable></command>
84 </term>
85
86 <listitem>
87 <para>
88 A zone can be destroyed with this command.
89 </para>
90 <para>
91 There are two possible ways to remove a zone. The case
92 is when the zone is not up. Then, it will be removed
93 immediately. When the zone is current up and used, it
94 will tagged to be remove later, after it has been brought
95 down.
96 </para>
97 </listitem>
98 </varlistentry>
99 </variablelist>
100
101 <para>
102 For all other commands, the name of the zone needs to be passed first:
103 </para>
104
105 <variablelist>
106 <varlistentry>
107 <term>
108 <command><replaceable>ZONE</replaceable> edit <arg choice="opt" rep="repeat">OPTIONS</arg></command>
109 </term>
110
111 <listitem>
112 <para>
113 The settings of a zone may be edited after it has been created.
114 The options that can be passed depend on the hook that is used
115 for the zone.
116 Run <command>network zone <replaceable>ZONE</replaceable> edit --help</command>
117 to learn more about that.
118 </para>
119 <para>
120 It usually is required to restart/reload the zone until
121 the new settings are taken into account.
122 </para>
123 </listitem>
124 </varlistentry>
125
126 <varlistentry>
127 <term>
128 <command><replaceable>ZONE</replaceable> [up|down]</command>
129 </term>
130
131 <listitem>
132 <para>
133 These commands will bring the zone up/down. This is done
134 without control of systemd, therefore not intended to be
135 done in a productive environment.
136 However, these commands may be used for debugging.
137 </para>
138 </listitem>
139 </varlistentry>
140
141 <varlistentry>
142 <term>
143 <command><replaceable>ZONE</replaceable> [enable|disable]</command>
144 </term>
145
146 <listitem>
147 <para>
148 These commands will enable or disable the zone. An enabled
149 zone will automatically be started either during the boot process
150 or a hotplug event of an associated port or other device.
151 </para>
152 </listitem>
153 </varlistentry>
154
155 <varlistentry>
156 <term>
157 <command><replaceable>ZONE</replaceable> status</command>
158 </term>
159
160 <listitem>
161 <para>
162 This will show some detailed information about the state
163 if the specified zone.
164 </para>
165 </listitem>
166 </varlistentry>
167
168 <varlistentry>
169 <term>
170 <command><replaceable>ZONE</replaceable> identify</command>
171 </term>
172
173 <listitem>
174 <para>
175 This command will make all ports of the zone flash for
176 a few seconds so that you can identify the correct network
177 adapters in the system.
178 </para>
179 </listitem>
180 </varlistentry>
181
182 <varlistentry>
183 <term>
184 <command><replaceable>ZONE</replaceable> rename <replaceable>NAME</replaceable></command>
185 </term>
186
187 <listitem>
188 <para>
189 Renames the zone to <replaceable>NAME</replaceable>.
190 </para>
191 <para>
192 The command will shut down the zone if it is up and
193 start it again with the new name. If the zone is not
194 up it won't be started.
195 </para>
196 <para>
197 Zones that are marked to be destroyed cannot be renamed.
198 </para>
199 </listitem>
200 </varlistentry>
201 </variablelist>
202 </refsect1>
203
204 <refsect1>
205 <title>See Also</title>
206
207 <para>
208 <citerefentry>
209 <refentrytitle>network</refentrytitle>
210 <manvolnum>8</manvolnum>
211 </citerefentry>
212 </para>
213 </refsect1>
214 </refentry>