2011-06-26 13:13:10 +04:00
<?xml version="1.0"?>
2007-07-24 13:19:40 +04:00
<!-- A Relax NG schema for the libvirt network XML format -->
2010-11-11 22:48:51 +03:00
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
2007-07-24 13:19:40 +04:00
datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes">
2010-11-11 22:48:51 +03:00
<start>
<ref name="network"/>
</start>
2011-06-26 13:13:10 +04:00
<include href='basictypes.rng'/>
conf: support abstracted interface info in network XML
The network XML is updated in the following ways:
1) The <forward> element can now contain a list of forward interfaces:
<forward .... >
<interface dev='eth10'/>
<interface dev='eth11'/>
<interface dev='eth12'/>
<interface dev='eth13'/>
</forward>
The first of these takes the place of the dev attribute that is
normally in <forward> - when defining a network you can specify
either one, and on output both will be present. If you specify
both on input, they must match.
2) In addition to forward modes of 'nat' and 'route', these new modes
are supported:
private, passthrough, vepa - when this network is referenced by a
domain's interface, it will have the same effect as if the
interface had been defined as type='direct', e.g.:
<interface type='direct'>
<source mode='${mode}' dev='${dev}>
...
</interface>
where ${mode} is one of the three new modes, and ${dev} is an interface
selected from the list given in <forward>.
bridge - if a <forward> dev (or multiple devs) is defined, and
forward mode is 'bridge' this is just like the modes 'private',
'passthrough', and 'vepa' above. If there is no forward dev
specified but a bridge name is given (e.g. "<bridge
name='br0'/>"), then guest interfaces using this network will use
libvirt's "host bridge" mode, equivalent to this:
<interface type='bridge'>
<source bridge='${bridge-name}'/>
...
</interface>
3) A network can have multiple <portgroup> elements, which may be
selected by the guest interface definition (by adding
"portgroup='${name}'" in the <source> element along with the
network name). Currently a portgroup can only contain a
virtportprofile, but the intent is that other configuration items
may be put there int the future (e.g. bandwidth config). When
building a guest's interface, if the <interface> XML itself has no
virtportprofile, and if the requested network has a portgroup with
a name matching the name given in the <interface> (or if one of the
network's portgroups is marked with the "default='yes'" attribute),
the virtportprofile from that portgroup will be used by the
interface.
4) A network can have a virtportprofile defined at the top level,
which will be used by a guest interface when connecting in one of
the 'direct' modes if the guest interface XML itself hasn't
specified any virtportprofile, and if there are also no matching
portgroups on the network.
2011-07-20 07:01:09 +04:00
<include href='networkcommon.rng'/>
2011-06-26 13:13:10 +04:00
2010-11-11 23:17:34 +03:00
<define name="network">
2010-11-11 22:48:51 +03:00
2010-11-11 23:17:34 +03:00
<element name="network">
2012-08-07 00:17:58 +04:00
<optional>
<attribute name="connections">
<data type="unsignedInt"/>
</attribute>
</optional>
2012-12-03 20:13:36 +04:00
<!-- Enables IPv6 guest-to-guest communications on a network
with no gateways addresses specified -->
<optional>
<attribute name="ipv6">
2014-09-08 10:06:35 +04:00
<ref name="virYesNo"/>
</attribute>
</optional>
2010-11-11 23:17:34 +03:00
<interleave>
2009-10-09 16:48:22 +04:00
2010-11-11 23:17:34 +03:00
<!-- The name of the network, used to refer to it through the API
and in virsh -->
<element name="name">
2009-10-09 16:48:22 +04:00
<text/>
2010-11-11 23:17:34 +03:00
</element>
2009-10-09 16:48:22 +04:00
2010-11-11 23:17:34 +03:00
<!-- <uuid> element -->
<optional>
2011-06-26 13:13:10 +04:00
<element name="uuid"><ref name="UUID"/></element>
2010-11-11 23:17:34 +03:00
</optional>
2009-10-09 16:48:22 +04:00
2010-11-11 23:17:34 +03:00
<!-- <bridge> element -->
<optional>
<!-- The name of the network to be set up; this will back
the network on the host -->
<element name="bridge">
<optional>
<attribute name="name">
2011-06-26 13:13:10 +04:00
<ref name="deviceName"/>
2010-11-11 23:17:34 +03:00
</attribute>
</optional>
2009-10-09 16:48:22 +04:00
2010-11-11 23:17:34 +03:00
<optional>
<attribute name="stp">
2014-09-08 10:06:35 +04:00
<ref name="virOnOff"/>
2010-11-11 23:17:34 +03:00
</attribute>
</optional>
2009-10-09 16:48:22 +04:00
2010-11-11 23:17:34 +03:00
<optional>
<attribute name="delay">
2014-09-15 12:42:15 +04:00
<data type="unsignedLong"/>
2010-11-11 23:17:34 +03:00
</attribute>
</optional>
2009-10-09 16:48:22 +04:00
2010-11-11 23:17:34 +03:00
</element>
</optional>
2009-10-09 16:48:22 +04:00
Give each virtual network bridge its own fixed MAC address
This fixes https://bugzilla.redhat.com/show_bug.cgi?id=609463
The problem was that, since a bridge always acquires the MAC address
of the connected interface with the numerically lowest MAC, as guests
are started and stopped, it was possible for the MAC address to change
over time, and this change in the network was being detected by
Windows 7 (it sees the MAC of the default route change), so on each
reboot it would bring up a dialog box asking about this "new network".
The solution is to create a dummy tap interface with a MAC guaranteed
to be lower than any guest interface's MAC, and attach that tap to the
bridge as soon as it's created. Since all guest MAC addresses start
with 0xFE, we can just generate a MAC with the standard "0x52, 0x54,
0" prefix, and it's guaranteed to always win (physical interfaces are
never connected to these bridges, so we don't need to worry about
competing numerically with them).
Note that the dummy tap is never set to IFF_UP state - that's not
necessary in order for the bridge to take its MAC, and not setting it
to UP eliminates the clutter of having an (eg) "virbr0-nic" displayed
in the output of the ifconfig command.
I chose to not auto-generate the MAC address in the network XML
parser, as there are likely to be consumers of that API that don't
need or want to have a MAC address associated with the
bridge.
Instead, in bridge_driver.c when the network is being defined, if
there is no MAC, one is generated. To account for virtual network
configs that already exist when upgrading from an older version of
libvirt, I've added a %post script to the specfile that searches for
all network definitions in both the config directory
(/etc/libvirt/qemu/networks) and the state directory
(/var/lib/libvirt/network) that are missing a mac address, generates a
random address, and adds it to the config (and a matching address to
the state file, if there is one).
docs/formatnetwork.html.in: document <mac address.../>
docs/schemas/network.rng: add nac address to schema
libvirt.spec.in: %post script to update existing networks
src/conf/network_conf.[ch]: parse and format <mac address.../>
src/libvirt_private.syms: export a couple private symbols we need
src/network/bridge_driver.c:
auto-generate mac address when needed,
create dummy interface if mac address is present.
tests/networkxml2xmlin/isolated-network.xml
tests/networkxml2xmlin/routed-network.xml
tests/networkxml2xmlout/isolated-network.xml
tests/networkxml2xmlout/routed-network.xml: add mac address to some tests
2011-02-09 11:28:12 +03:00
<!-- <mac> element -->
<optional>
<element name="mac">
2012-03-19 20:49:17 +04:00
<attribute name="address"><ref name="uniMacAddr"/></attribute>
Give each virtual network bridge its own fixed MAC address
This fixes https://bugzilla.redhat.com/show_bug.cgi?id=609463
The problem was that, since a bridge always acquires the MAC address
of the connected interface with the numerically lowest MAC, as guests
are started and stopped, it was possible for the MAC address to change
over time, and this change in the network was being detected by
Windows 7 (it sees the MAC of the default route change), so on each
reboot it would bring up a dialog box asking about this "new network".
The solution is to create a dummy tap interface with a MAC guaranteed
to be lower than any guest interface's MAC, and attach that tap to the
bridge as soon as it's created. Since all guest MAC addresses start
with 0xFE, we can just generate a MAC with the standard "0x52, 0x54,
0" prefix, and it's guaranteed to always win (physical interfaces are
never connected to these bridges, so we don't need to worry about
competing numerically with them).
Note that the dummy tap is never set to IFF_UP state - that's not
necessary in order for the bridge to take its MAC, and not setting it
to UP eliminates the clutter of having an (eg) "virbr0-nic" displayed
in the output of the ifconfig command.
I chose to not auto-generate the MAC address in the network XML
parser, as there are likely to be consumers of that API that don't
need or want to have a MAC address associated with the
bridge.
Instead, in bridge_driver.c when the network is being defined, if
there is no MAC, one is generated. To account for virtual network
configs that already exist when upgrading from an older version of
libvirt, I've added a %post script to the specfile that searches for
all network definitions in both the config directory
(/etc/libvirt/qemu/networks) and the state directory
(/var/lib/libvirt/network) that are missing a mac address, generates a
random address, and adds it to the config (and a matching address to
the state file, if there is one).
docs/formatnetwork.html.in: document <mac address.../>
docs/schemas/network.rng: add nac address to schema
libvirt.spec.in: %post script to update existing networks
src/conf/network_conf.[ch]: parse and format <mac address.../>
src/libvirt_private.syms: export a couple private symbols we need
src/network/bridge_driver.c:
auto-generate mac address when needed,
create dummy interface if mac address is present.
tests/networkxml2xmlin/isolated-network.xml
tests/networkxml2xmlin/routed-network.xml
tests/networkxml2xmlout/isolated-network.xml
tests/networkxml2xmlout/routed-network.xml: add mac address to some tests
2011-02-09 11:28:12 +03:00
<empty/>
</element>
</optional>
2010-11-11 23:17:34 +03:00
<!-- <forward> element -->
<optional>
<!-- The device through which the bridge is connected to the
rest of the network -->
<element name="forward">
<optional>
<attribute name="dev">
2011-06-26 13:13:10 +04:00
<ref name="deviceName"/>
2010-11-11 23:17:34 +03:00
</attribute>
</optional>
2009-10-09 16:48:22 +04:00
2010-11-11 23:17:34 +03:00
<optional>
<attribute name="mode">
<choice>
<value>nat</value>
<value>route</value>
conf: support abstracted interface info in network XML
The network XML is updated in the following ways:
1) The <forward> element can now contain a list of forward interfaces:
<forward .... >
<interface dev='eth10'/>
<interface dev='eth11'/>
<interface dev='eth12'/>
<interface dev='eth13'/>
</forward>
The first of these takes the place of the dev attribute that is
normally in <forward> - when defining a network you can specify
either one, and on output both will be present. If you specify
both on input, they must match.
2) In addition to forward modes of 'nat' and 'route', these new modes
are supported:
private, passthrough, vepa - when this network is referenced by a
domain's interface, it will have the same effect as if the
interface had been defined as type='direct', e.g.:
<interface type='direct'>
<source mode='${mode}' dev='${dev}>
...
</interface>
where ${mode} is one of the three new modes, and ${dev} is an interface
selected from the list given in <forward>.
bridge - if a <forward> dev (or multiple devs) is defined, and
forward mode is 'bridge' this is just like the modes 'private',
'passthrough', and 'vepa' above. If there is no forward dev
specified but a bridge name is given (e.g. "<bridge
name='br0'/>"), then guest interfaces using this network will use
libvirt's "host bridge" mode, equivalent to this:
<interface type='bridge'>
<source bridge='${bridge-name}'/>
...
</interface>
3) A network can have multiple <portgroup> elements, which may be
selected by the guest interface definition (by adding
"portgroup='${name}'" in the <source> element along with the
network name). Currently a portgroup can only contain a
virtportprofile, but the intent is that other configuration items
may be put there int the future (e.g. bandwidth config). When
building a guest's interface, if the <interface> XML itself has no
virtportprofile, and if the requested network has a portgroup with
a name matching the name given in the <interface> (or if one of the
network's portgroups is marked with the "default='yes'" attribute),
the virtportprofile from that portgroup will be used by the
interface.
4) A network can have a virtportprofile defined at the top level,
which will be used by a guest interface when connecting in one of
the 'direct' modes if the guest interface XML itself hasn't
specified any virtportprofile, and if there are also no matching
portgroups on the network.
2011-07-20 07:01:09 +04:00
<value>bridge</value>
<value>passthrough</value>
<value>private</value>
<value>vepa</value>
2012-08-16 19:41:41 +04:00
<value>hostdev</value>
</choice>
</attribute>
</optional>
<optional>
<attribute name="managed">
2014-09-08 10:06:35 +04:00
<ref name="virYesNo"/>
2010-11-11 23:17:34 +03:00
</attribute>
</optional>
2011-12-14 14:50:23 +04:00
<interleave>
2012-08-16 19:41:41 +04:00
<choice>
<group>
<zeroOrMore>
<element name='interface'>
<attribute name='dev'>
<ref name='deviceName'/>
</attribute>
<optional>
<attribute name="connections">
<data type="unsignedInt"/>
</attribute>
</optional>
</element>
</zeroOrMore>
</group>
<group>
<zeroOrMore>
<element name='address'>
<attribute name='type'>
<value>pci</value>
</attribute>
<ref name="pciaddress"/>
<optional>
<attribute name="connections">
<data type="unsignedInt"/>
</attribute>
</optional>
</element>
</zeroOrMore>
</group>
</choice>
2011-12-14 14:50:23 +04:00
<optional>
<element name='pf'>
<attribute name='dev'>
<ref name='deviceName'/>
</attribute>
</element>
</optional>
2013-03-15 23:15:14 +04:00
<optional>
<element name="driver">
<attribute name="name">
<choice>
<value>kvm</value>
<value>vfio</value>
</choice>
</attribute>
<empty/>
</element>
</optional>
2013-09-05 13:08:38 +04:00
<optional>
<element name='nat'>
<interleave>
<optional>
<element name='address'>
<attribute name='start'>
<ref name='ipv4Addr'/>
</attribute>
<attribute name='end'>
<ref name='ipv4Addr'/>
</attribute>
</element>
</optional>
<optional>
<element name='port'>
<attribute name='start'>
<ref name='port'/>
</attribute>
<attribute name='end'>
<ref name='port'/>
</attribute>
</element>
</optional>
</interleave>
</element>
</optional>
2011-12-14 14:50:23 +04:00
</interleave>
2007-07-24 13:19:40 +04:00
</element>
2010-11-11 23:17:34 +03:00
</optional>
conf: support abstracted interface info in network XML
The network XML is updated in the following ways:
1) The <forward> element can now contain a list of forward interfaces:
<forward .... >
<interface dev='eth10'/>
<interface dev='eth11'/>
<interface dev='eth12'/>
<interface dev='eth13'/>
</forward>
The first of these takes the place of the dev attribute that is
normally in <forward> - when defining a network you can specify
either one, and on output both will be present. If you specify
both on input, they must match.
2) In addition to forward modes of 'nat' and 'route', these new modes
are supported:
private, passthrough, vepa - when this network is referenced by a
domain's interface, it will have the same effect as if the
interface had been defined as type='direct', e.g.:
<interface type='direct'>
<source mode='${mode}' dev='${dev}>
...
</interface>
where ${mode} is one of the three new modes, and ${dev} is an interface
selected from the list given in <forward>.
bridge - if a <forward> dev (or multiple devs) is defined, and
forward mode is 'bridge' this is just like the modes 'private',
'passthrough', and 'vepa' above. If there is no forward dev
specified but a bridge name is given (e.g. "<bridge
name='br0'/>"), then guest interfaces using this network will use
libvirt's "host bridge" mode, equivalent to this:
<interface type='bridge'>
<source bridge='${bridge-name}'/>
...
</interface>
3) A network can have multiple <portgroup> elements, which may be
selected by the guest interface definition (by adding
"portgroup='${name}'" in the <source> element along with the
network name). Currently a portgroup can only contain a
virtportprofile, but the intent is that other configuration items
may be put there int the future (e.g. bandwidth config). When
building a guest's interface, if the <interface> XML itself has no
virtportprofile, and if the requested network has a portgroup with
a name matching the name given in the <interface> (or if one of the
network's portgroups is marked with the "default='yes'" attribute),
the virtportprofile from that portgroup will be used by the
interface.
4) A network can have a virtportprofile defined at the top level,
which will be used by a guest interface when connecting in one of
the 'direct' modes if the guest interface XML itself hasn't
specified any virtportprofile, and if there are also no matching
portgroups on the network.
2011-07-20 07:01:09 +04:00
<!-- <virtualport> element -->
<optional>
<ref name="virtualPortProfile"/>
</optional>
<!-- <portgroup> elements -->
<zeroOrMore>
<element name="portgroup">
<attribute name="name">
<ref name="deviceName"/>
</attribute>
<optional>
<attribute name="default">
2014-09-08 10:06:35 +04:00
<ref name="virYesNo"/>
conf: support abstracted interface info in network XML
The network XML is updated in the following ways:
1) The <forward> element can now contain a list of forward interfaces:
<forward .... >
<interface dev='eth10'/>
<interface dev='eth11'/>
<interface dev='eth12'/>
<interface dev='eth13'/>
</forward>
The first of these takes the place of the dev attribute that is
normally in <forward> - when defining a network you can specify
either one, and on output both will be present. If you specify
both on input, they must match.
2) In addition to forward modes of 'nat' and 'route', these new modes
are supported:
private, passthrough, vepa - when this network is referenced by a
domain's interface, it will have the same effect as if the
interface had been defined as type='direct', e.g.:
<interface type='direct'>
<source mode='${mode}' dev='${dev}>
...
</interface>
where ${mode} is one of the three new modes, and ${dev} is an interface
selected from the list given in <forward>.
bridge - if a <forward> dev (or multiple devs) is defined, and
forward mode is 'bridge' this is just like the modes 'private',
'passthrough', and 'vepa' above. If there is no forward dev
specified but a bridge name is given (e.g. "<bridge
name='br0'/>"), then guest interfaces using this network will use
libvirt's "host bridge" mode, equivalent to this:
<interface type='bridge'>
<source bridge='${bridge-name}'/>
...
</interface>
3) A network can have multiple <portgroup> elements, which may be
selected by the guest interface definition (by adding
"portgroup='${name}'" in the <source> element along with the
network name). Currently a portgroup can only contain a
virtportprofile, but the intent is that other configuration items
may be put there int the future (e.g. bandwidth config). When
building a guest's interface, if the <interface> XML itself has no
virtportprofile, and if the requested network has a portgroup with
a name matching the name given in the <interface> (or if one of the
network's portgroups is marked with the "default='yes'" attribute),
the virtportprofile from that portgroup will be used by the
interface.
4) A network can have a virtportprofile defined at the top level,
which will be used by a guest interface when connecting in one of
the 'direct' modes if the guest interface XML itself hasn't
specified any virtportprofile, and if there are also no matching
portgroups on the network.
2011-07-20 07:01:09 +04:00
</attribute>
</optional>
2012-08-12 20:01:32 +04:00
<interleave>
<optional>
<ref name="virtualPortProfile"/>
</optional>
<optional>
<ref name="bandwidth"/>
</optional>
2012-08-12 11:51:30 +04:00
<optional>
<ref name="vlan"/>
</optional>
2012-08-12 20:01:32 +04:00
</interleave>
conf: support abstracted interface info in network XML
The network XML is updated in the following ways:
1) The <forward> element can now contain a list of forward interfaces:
<forward .... >
<interface dev='eth10'/>
<interface dev='eth11'/>
<interface dev='eth12'/>
<interface dev='eth13'/>
</forward>
The first of these takes the place of the dev attribute that is
normally in <forward> - when defining a network you can specify
either one, and on output both will be present. If you specify
both on input, they must match.
2) In addition to forward modes of 'nat' and 'route', these new modes
are supported:
private, passthrough, vepa - when this network is referenced by a
domain's interface, it will have the same effect as if the
interface had been defined as type='direct', e.g.:
<interface type='direct'>
<source mode='${mode}' dev='${dev}>
...
</interface>
where ${mode} is one of the three new modes, and ${dev} is an interface
selected from the list given in <forward>.
bridge - if a <forward> dev (or multiple devs) is defined, and
forward mode is 'bridge' this is just like the modes 'private',
'passthrough', and 'vepa' above. If there is no forward dev
specified but a bridge name is given (e.g. "<bridge
name='br0'/>"), then guest interfaces using this network will use
libvirt's "host bridge" mode, equivalent to this:
<interface type='bridge'>
<source bridge='${bridge-name}'/>
...
</interface>
3) A network can have multiple <portgroup> elements, which may be
selected by the guest interface definition (by adding
"portgroup='${name}'" in the <source> element along with the
network name). Currently a portgroup can only contain a
virtportprofile, but the intent is that other configuration items
may be put there int the future (e.g. bandwidth config). When
building a guest's interface, if the <interface> XML itself has no
virtportprofile, and if the requested network has a portgroup with
a name matching the name given in the <interface> (or if one of the
network's portgroups is marked with the "default='yes'" attribute),
the virtportprofile from that portgroup will be used by the
interface.
4) A network can have a virtportprofile defined at the top level,
which will be used by a guest interface when connecting in one of
the 'direct' modes if the guest interface XML itself hasn't
specified any virtportprofile, and if there are also no matching
portgroups on the network.
2011-07-20 07:01:09 +04:00
</element>
</zeroOrMore>
2010-11-11 23:17:34 +03:00
<!-- <domain> element -->
<optional>
<element name="domain">
2011-06-26 13:13:10 +04:00
<attribute name="name"><ref name="dnsName"/></attribute>
2009-07-02 18:02:18 +04:00
</element>
2010-11-11 23:17:34 +03:00
</optional>
2011-06-24 14:04:36 +04:00
<!-- Define the DNS related elements like TXT records
and other features in the <dns> element -->
<optional>
2013-09-13 20:31:07 +04:00
<element name="dns">
<optional>
<attribute name="forwardPlainNames">
2014-09-08 10:06:35 +04:00
<ref name="virYesNo"/>
2013-09-13 20:31:07 +04:00
</attribute>
</optional>
<interleave>
<zeroOrMore>
<element name="forwarder">
<attribute name="addr"><ref name="ipAddr"/></attribute>
</element>
</zeroOrMore>
2011-06-24 14:04:36 +04:00
<zeroOrMore>
<element name="txt">
2011-06-26 13:13:10 +04:00
<attribute name="name"><ref name="dnsName"/></attribute>
2011-06-24 14:04:36 +04:00
<attribute name="value"><text/></attribute>
</element>
</zeroOrMore>
2012-01-02 18:23:54 +04:00
<zeroOrMore>
<element name="srv">
<attribute name="service"><text/></attribute>
2013-09-13 20:31:07 +04:00
<attribute name="protocol">
<ref name="protocol"/>
</attribute>
2012-01-02 18:23:54 +04:00
<optional>
<attribute name="domain"><ref name="dnsName"/></attribute>
<attribute name="target"><text/></attribute>
2013-09-13 20:31:07 +04:00
<attribute name="port">
<ref name="unsignedShort"/>
</attribute>
<attribute name="priority">
<ref name="unsignedShort"/>
</attribute>
<attribute name="weight">
<ref name="unsignedShort"/>
</attribute>
2012-01-02 18:23:54 +04:00
</optional>
</element>
</zeroOrMore>
2011-06-24 14:04:40 +04:00
<zeroOrMore>
<element name="host">
2012-12-06 21:20:38 +04:00
<attribute name="ip"><ref name="ipAddr"/></attribute>
2011-06-24 14:04:40 +04:00
<oneOrMore>
2011-06-26 13:13:10 +04:00
<element name="hostname"><ref name="dnsName"/></element>
2011-06-24 14:04:40 +04:00
</oneOrMore>
</element>
</zeroOrMore>
2013-09-13 20:31:07 +04:00
</interleave>
</element>
2011-06-24 14:04:36 +04:00
</optional>
2013-09-13 20:31:07 +04:00
<optional>
<ref name="bandwidth"/>
</optional>
<optional>
2012-08-12 11:51:30 +04:00
<ref name="vlan"/>
2013-09-13 20:31:07 +04:00
</optional>
<optional>
<element name="link">
<attribute name="state">
<choice>
<value>up</value>
<value>down</value>
</choice>
</attribute>
<empty/>
</element>
2011-09-06 12:08:15 +04:00
</optional>
2011-06-24 14:04:36 +04:00
2010-11-11 23:17:34 +03:00
<!-- <ip> element -->
2010-11-17 21:36:19 +03:00
<zeroOrMore>
2010-11-11 23:17:34 +03:00
<!-- The IP element sets up NAT'ing and an optional DHCP server
local to the host. -->
<element name="ip">
<optional>
2011-06-26 13:13:10 +04:00
<attribute name="address"><ref name="ipAddr"/></attribute>
2010-11-17 21:36:19 +03:00
</optional>
<optional>
<choice>
2011-06-26 13:13:10 +04:00
<attribute name="netmask"><ref name="ipv4Addr"/></attribute>
<attribute name="prefix"><ref name="ipPrefix"/></attribute>
2010-11-17 21:36:19 +03:00
</choice>
2010-11-11 23:17:34 +03:00
</optional>
<optional>
2010-11-17 21:36:19 +03:00
<attribute name="family"><ref name="addr-family"/></attribute>
2010-11-11 23:17:34 +03:00
</optional>
2009-10-28 17:57:49 +03:00
<optional>
2010-11-11 23:17:34 +03:00
<element name="tftp">
<attribute name="root"><text/></attribute>
</element>
2009-10-28 17:57:49 +03:00
</optional>
2010-12-16 20:36:19 +03:00
<optional>
<!-- Define the range(s) of IP addresses that the DHCP
server should hand out -->
<element name="dhcp">
<zeroOrMore>
<element name="range">
2012-12-06 21:20:38 +04:00
<attribute name="start"><ref name="ipAddr"/></attribute>
<attribute name="end"><ref name="ipAddr"/></attribute>
2010-12-16 20:36:19 +03:00
</element>
</zeroOrMore>
<zeroOrMore>
<element name="host">
2013-02-15 23:02:25 +04:00
<choice>
<group>
2013-02-15 23:02:26 +04:00
<choice>
<attribute name="mac"><ref name="uniMacAddr"/></attribute>
<attribute name="id"><ref name="DUID"/></attribute>
</choice>
2013-02-15 23:02:25 +04:00
<optional>
<attribute name="name"><text/></attribute>
</optional>
</group>
<attribute name="name"><text/></attribute>
</choice>
2012-12-06 21:20:38 +04:00
<attribute name="ip"><ref name="ipAddr"/></attribute>
2010-12-16 20:36:19 +03:00
</element>
</zeroOrMore>
<optional>
<element name="bootp">
2011-06-26 13:13:10 +04:00
<attribute name="file"><ref name="filePath"/></attribute>
2010-12-16 20:36:19 +03:00
<optional>
2011-06-26 13:13:10 +04:00
<attribute name="server"><ref name="dnsName"/></attribute>
2010-12-16 20:36:19 +03:00
</optional>
</element>
</optional>
</element>
</optional>
2010-03-01 22:09:26 +03:00
</element>
2010-11-17 21:36:19 +03:00
</zeroOrMore>
Support for static routes on a virtual bridge
network: static route support for <network>
This patch adds the <route> subelement of <network> to define a static
route. the address and prefix (or netmask) attribute identify the
destination network, and the gateway attribute specifies the next hop
address (which must be directly reachable from the containing
<network>) which is to receive the packets destined for
"address/(prefix|netmask)".
These attributes are translated into an "ip route add" command that is
executed when the network is started. The command used is of the
following form:
ip route add <address>/<prefix> via <gateway> \
dev <virbr-bridge> proto static metric <metric>
Tests are done to validate that the input data are correct. For
example, for a static route ip definition, the address must be a
network address and not a host address. Additional checks are added
to ensure that the specified gateway is directly reachable via this
network (i.e. that the gateway IP address is in the same subnet as one
of the IP's defined for the network).
prefix='0' is supported for both family='ipv4' address='0.0.0.0'
netmask='0.0.0.0' or prefix='0', and for family='ipv6' address='::',
prefix=0', although care should be taken to not override a desired
system default route.
Anytime an attempt is made to define a static route which *exactly*
duplicates an existing static route (for example, address=::,
prefix=0, metric=1), the following error message will be sent to
syslog:
RTNETLINK answers: File exists
This can be overridden by decreasing the metric value for the route
that should be preferred, or increasing the metric for the route that
shouldn't be preferred (and is thus in place only in anticipation that
the preferred route may be removed in the future). Caution should be
used when manipulating route metrics, especially for a default route.
Note: The use of the command-line interface should be replaced by
direct use of libnl so that error conditions can be handled better. But,
that is being left as an exercise for another day.
Signed-off-by: Gene Czarcinski <gene@czarc.net>
Signed-off-by: Laine Stump <laine@laine.org>
2013-05-07 21:42:55 +04:00
<!-- <route> element -->
<zeroOrMore>
<!-- The (static) route element specifies a network address and gateway
address to access that network. Both the network address and
the gateway address must be specified. -->
<element name="route">
<optional>
<attribute name="family"><ref name="addr-family"/></attribute>
</optional>
<attribute name="address"><ref name="ipAddr"/></attribute>
<optional>
<choice>
<attribute name="netmask"><ref name="ipv4Addr"/></attribute>
<attribute name="prefix"><ref name="ipPrefix"/></attribute>
</choice>
</optional>
<attribute name="gateway"><ref name="ipAddr"/></attribute>
<optional>
<attribute name="metric"><ref name="unsignedInt"/></attribute>
</optional>
</element>
</zeroOrMore>
2010-11-11 23:17:34 +03:00
</interleave>
2007-07-24 13:19:40 +04:00
</element>
2010-11-11 23:17:34 +03:00
</define>
2010-11-11 22:48:51 +03:00
</grammar>
