2 <!DOCTYPE refentry PUBLIC
"-//OASIS/DTD DocBook XML V4.2//EN"
3 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
5 <refentry id=
"network-zone">
7 <title>network-zone
</title>
8 <productname>network
</productname>
12 <contrib>Developer
</contrib>
13 <firstname>Michael
</firstname>
14 <surname>Tremer
</surname>
15 <email>michael.tremer@ipfire.org
</email>
21 <refentrytitle>network-zone
</refentrytitle>
22 <manvolnum>8</manvolnum>
26 <refname>network-zone
</refname>
27 <refpurpose>Network Configuration Control Program
</refpurpose>
32 <command>network zone
<arg choice=
"plain">[create|remove]
</arg> <replaceable>ZONE
</replaceable> ...
</command>
36 <command>network zone
<arg choice=
"plain">list-hooks
</arg></command>
40 <command>network zone
<replaceable>ZONE
</replaceable> <arg choice=
"plain">command
</arg> ...
</command>
45 <title>Description
</title>
48 With help of the
<command>zone
</command> command, it is very easy to
49 configure network zones.
52 It is possible to create zones and remove them. Zones may also
53 be brought up and down and reconfigured. Their status may be viewed
59 <title>Commands
</title>
62 The following commands are understood:
68 <command>create
<replaceable>ZONE
</replaceable> <replaceable>HOOK
</replaceable> <arg choice=
"opt" rep=
"repeat">OPTIONS
</arg></command>
73 A new zone may be created by the
<command>create
</command>
74 command. There are at least two arguments required.
77 <replaceable>ZONE
</replaceable> must be valid name for a
78 zone which does not already exist.
79 <replaceable>HOOK
</replaceable> is a valid zone hook which
80 may require additional options.
87 <command>remove
<replaceable>ZONE
</replaceable></command>
92 A zone can be simple removed with this command.
95 There are two possible ways to remove a zone. The case
96 is when the zone is not up. Then, it will be removed
97 immediately. When the zone is current up and used, it
98 will tagged to be remove later, after it has been brought
106 <command>list-hooks
</command>
111 Outputs a list of all eligible hooks for the zones.
118 For all other commands, the name of the zone needs to be passed first:
124 <command><replaceable>ZONE
</replaceable> edit
<arg choice=
"opt" rep=
"repeat">OPTIONS
</arg></command>
129 The settings of a zone may be edited after it has been created.
130 The options that can be passed depend on the hook that is used
132 Run
<command>network zone
<replaceable>ZONE
</replaceable> edit --help
</command>
133 to learn more about that.
136 It usually is required to restart/reload the zone until
137 the new settings are taken into account.
144 <command><replaceable>ZONE
</replaceable> [up|down]
</command>
149 These commands will bring the zone up/down. This is done
150 without control of systemd, therefore not intended to be
151 done in a productive environment.
152 However, these commands may be used for debugging.
159 <command><replaceable>ZONE
</replaceable> [enable|disable]
</command>
164 These commands will enable or disable the zone. An enabled
165 zone will automatically be started either during the boot process
166 or a hotplug event of an associated port or other device.
173 <command><replaceable>ZONE
</replaceable> status
</command>
178 This will show some detailed information about the state
179 if the specified zone.
187 <title>See Also
</title>
191 <refentrytitle>network
</refentrytitle>
192 <manvolnum>8</manvolnum>