2020-10-02 19:24:21 +00:00
|
|
|
|
interfaces-vxlan(5)
|
|
|
|
|
|
|
|
|
|
# NAME
|
|
|
|
|
|
|
|
|
|
*interfaces-vxlan* - VXLAN extensions for the interfaces(5) file format
|
|
|
|
|
|
|
|
|
|
# DESCRIPTION
|
|
|
|
|
|
|
|
|
|
Virtual eXtensible LAN (VXLAN) is an overlay network to carry Layer 2 over
|
|
|
|
|
an IP network while accommodating a very large number of tenants. It is
|
|
|
|
|
defined in RFC 7348.
|
|
|
|
|
|
2020-10-02 20:29:01 +00:00
|
|
|
|
Be aware that VXLAN encapsulation adds 50 bytes of overhead to the IP packet
|
|
|
|
|
header (inner Ethernet header + VXLAN + UDP + IP). This should be taken into
|
|
|
|
|
consideration when setting up overlay networks, particularly on underlay
|
|
|
|
|
networks with a conventional 1500 byte MTU.
|
2020-10-02 19:24:21 +00:00
|
|
|
|
|
2020-10-02 20:29:01 +00:00
|
|
|
|
The following options set up VXLAN Tunnel EndPoints (VTEP) interfaces with
|
|
|
|
|
ifupdown-ng.
|
2020-10-02 19:24:21 +00:00
|
|
|
|
|
2020-10-02 20:29:01 +00:00
|
|
|
|
See https://www.kernel.org/doc/Documentation/networking/vxlan.rst and
|
2020-10-02 19:24:21 +00:00
|
|
|
|
https://vincent.bernat.ch/en/blog/2017-vxlan-linux for more information.
|
|
|
|
|
|
|
|
|
|
# VXLAN-RELATED OPTIONS
|
|
|
|
|
|
|
|
|
|
A VXLAN Virtual Tunnel Endpoint (VTEP) interface must an ID set. All
|
|
|
|
|
other options are optional.
|
|
|
|
|
|
|
|
|
|
*vxlan-id* _VNI ID_
|
|
|
|
|
Denotes the VXLAN Network Identifier (VNI) ID for this interface.
|
2020-10-02 20:29:01 +00:00
|
|
|
|
This parameter is required for VTEP interfaces.
|
2020-10-02 19:24:21 +00:00
|
|
|
|
|
|
|
|
|
*vxlan-physdev* _interface_
|
2020-10-02 20:29:01 +00:00
|
|
|
|
Specifies the physical ("underlay") device to use for tunnel
|
|
|
|
|
endpoint communication.
|
2020-10-02 19:24:21 +00:00
|
|
|
|
|
|
|
|
|
*vxlan-local-ip* _address_
|
|
|
|
|
Specifies the source IP address to use in outgoing packets.
|
|
|
|
|
For compatiblity with ifupdown2 _vxlan-local-tunnelip_ is an
|
|
|
|
|
alias for this parameter.
|
|
|
|
|
|
2021-10-16 13:15:35 +00:00
|
|
|
|
*vxlan-peer-ips* _list of IP addresses_
|
|
|
|
|
Specifies the unicast destination IP address(es) to use in outgoing
|
2020-10-02 19:24:21 +00:00
|
|
|
|
packets when the destination link layer address is not known in
|
2021-10-16 13:15:35 +00:00
|
|
|
|
the VXLAN device forwarding database. This option can be used to
|
|
|
|
|
form Point-to-Point as well as Point-to-Multipoint VXLAN tunnels/
|
|
|
|
|
overlays depending on how many peer IPs are given. If more than one
|
|
|
|
|
IP address is given a Point-to-Multipoint overlay is being set up
|
|
|
|
|
and ingress / head-end replication will be used by the Linux Kernel.
|
|
|
|
|
This option cannot be used together with _vxlan-peer-group_ option.
|
|
|
|
|
For compatiblity with ifupdown2 _vxlan-remoteip_ is an alias for this option
|
|
|
|
|
and for compatibility with previos versions of ifupdown-ng _vxlan-remote-ip_
|
|
|
|
|
is an alias for this option, too.
|
|
|
|
|
|
|
|
|
|
*vxlan-peer-group* _multicast group_
|
2020-10-02 20:29:01 +00:00
|
|
|
|
Specifies the multicast group IP address to join. This parameter
|
2021-10-16 13:15:35 +00:00
|
|
|
|
cannot be specified with the _vxlan-peer-ip_ parameter.
|
2020-10-02 19:24:21 +00:00
|
|
|
|
For compatibility with ifupdown2 _vxlan-svcnodeip_ is an alias for
|
2021-10-16 13:15:35 +00:00
|
|
|
|
this option and for compatibility with previos version of ifupdown-ng
|
|
|
|
|
_vxlan-remote-group_ is an alias, too.
|
2020-10-02 19:24:21 +00:00
|
|
|
|
|
|
|
|
|
*vxlan-learning* _on/off_
|
|
|
|
|
Specifies if unknown source link layer addresses and IP addresses
|
|
|
|
|
are entered into the VXLAN device forwarding database.
|
|
|
|
|
|
|
|
|
|
*vxlan-ageing* _seconds_
|
|
|
|
|
Specifies the lifetime in seconds of FDB entries learnt by the kernel.
|
|
|
|
|
|
|
|
|
|
*vxlan-dstport* _port_
|
2020-10-02 20:29:01 +00:00
|
|
|
|
Specifies the UDP destination port of the remote VXLAN tunnel endpoint.
|
|
|
|
|
The default is 4789.
|
2020-10-02 19:24:21 +00:00
|
|
|
|
|
|
|
|
|
# EXAMPLES
|
|
|
|
|
|
|
|
|
|
A VTEP with multiple peers addressed via a multicast group:
|
|
|
|
|
|
2020-10-06 18:59:23 +00:00
|
|
|
|
```
|
2020-10-02 19:24:21 +00:00
|
|
|
|
auto vx_v1001_padcty
|
|
|
|
|
iface vx_v1001_padcty
|
2020-10-06 18:59:23 +00:00
|
|
|
|
vxlan-id 655617
|
2020-10-02 19:24:21 +00:00
|
|
|
|
vxlan-physdev vlan1001
|
|
|
|
|
vxlan-remote-group 225.10.1.1
|
|
|
|
|
#
|
|
|
|
|
hwaddress f2:00:c1:01:10:01
|
|
|
|
|
mtu 1560
|
2020-10-06 18:59:23 +00:00
|
|
|
|
```
|
2020-10-02 19:24:21 +00:00
|
|
|
|
|
2021-10-16 13:15:35 +00:00
|
|
|
|
The same works just fine with IPv6 in the underlay:
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
auto vx_v1400_padcty
|
|
|
|
|
iface vx_v1400_padcty
|
|
|
|
|
vxlan-id 917505
|
|
|
|
|
vxlan-physdev vlan1400
|
|
|
|
|
vxlan-peer-group ff42:1400::1
|
|
|
|
|
#
|
|
|
|
|
hwaddress f2:00:0d:01:14:00
|
|
|
|
|
mtu 1560
|
|
|
|
|
```
|
|
|
|
|
|
2020-10-02 19:24:21 +00:00
|
|
|
|
Note that the underlay must have an MTU of at least 1610 to
|
2021-10-16 13:15:35 +00:00
|
|
|
|
carry the encapsulated packets of the two VTEPs above.
|
2020-10-02 19:24:21 +00:00
|
|
|
|
|
|
|
|
|
|
2021-10-16 13:15:35 +00:00
|
|
|
|
A VTEP with one peer (unicast point-to-point configuration):
|
2020-10-02 19:24:21 +00:00
|
|
|
|
|
2020-10-06 18:59:23 +00:00
|
|
|
|
```
|
2020-10-02 19:24:21 +00:00
|
|
|
|
auto vx_ptp1
|
|
|
|
|
iface vx_ptp1
|
2020-10-06 18:59:23 +00:00
|
|
|
|
vxlan-id 2342
|
2020-10-02 19:24:21 +00:00
|
|
|
|
vxlan-local-ip 192.0.2.42
|
2021-10-16 13:15:35 +00:00
|
|
|
|
vxlan-peer-ips 198.51.100.23
|
2020-10-02 19:24:21 +00:00
|
|
|
|
#
|
|
|
|
|
hwaddress f2:00:c1:01:10:01
|
2020-10-06 18:59:23 +00:00
|
|
|
|
```
|
2020-10-02 19:24:21 +00:00
|
|
|
|
|
2021-10-16 13:15:35 +00:00
|
|
|
|
|
|
|
|
|
A VTEP with multiple peers (unicast point-to-multipoint with ingress / head-end replication):
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
auto vx_her
|
|
|
|
|
iface vx_her
|
|
|
|
|
vxlan-id 1337
|
|
|
|
|
vxlan-local-ip 2001:db8:1::1
|
|
|
|
|
vxlan-peer-ips 2001:db8:2::23 2001:db8:3::42 2001:db8:4::84
|
|
|
|
|
```
|
|
|
|
|
|
2020-10-02 19:24:21 +00:00
|
|
|
|
# AUTHORS
|
|
|
|
|
|
|
|
|
|
Maximilian Wilhelm <max@sdn.clinic>
|