blob: 26d8a36497908f9c1494f50d44bd8af1960f729b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
|
.. _pseudo-ethernet-interface:
#######################
Pseudo Ethernet/MACVLAN
#######################
Pseudo-Ethernet or MACVLAN interfaces can be seen as subinterfaces to regular
ethernet interfaces. Each and every subinterface is created a different media
access control (MAC) address, for a single physical Ethernet port. Pseudo-
Ethernet interfaces have most of their application in virtualized environments,
By using Pseudo-Ethernet interfaces there will be less system overhead compared
to running a traditional bridging approach. Pseudo-Ethernet interfaces can also
be used to workaround the general limit of 4096 virtual LANs (VLANs) per
physical Ethernet port, since that limit is with respect to a single MAC
address.
Every Virtual Ethernet interfaces behaves like a real Ethernet interface. They
can have IPv4/IPv6 addresses configured, or can request addresses by DHCP/
DHCPv6 and are associated/mapped with a real ethernet port. This also makes
Pseudo-Ethernet interfaces interesting for testing purposes. A Pseudo-Ethernet
device will inherit characteristics (speed, duplex, ...) from its physical
parent (the so called link) interface.
Once created in the system, Pseudo-Ethernet interfaces can be referenced in
the exact same way as other Ethernet interfaces. Notes about using Pseudo-
Ethernet interfaces:
* Pseudo-Ethernet interfaces can not be reached from your internal host. This
means that you can not try to ping a Pseudo-Ethernet interface from the host
system on which it is defined. The ping will be lost.
* Loopbacks occurs at the IP level the same way as for other interfaces,
ethernet frames are not forwarded between Pseudo-Ethernet interfaces.
* Pseudo-Ethernet interfaces may not work in environments which expect a
:abbr:`NIC (Network Interface Card)` to only have a single address. This
applies to:
- VMware machines using default settings
- Network switches with security settings allowing only a single MAC address
- xDSL modems that try to lear the MAC address of the NIC
Configuration
=============
Common interface configuration
------------------------------
.. cmdinclude:: ../_include/interface-common-with-dhcp.txt
:var0: pseudo-ethernet
:var1: peth0
Pseudo Ethernet/MACVLAN specific options
----------------------------------------
.. cfgcmd:: set interfaces pseudo-ethernet <interface> source-interface <ethX>
Specifies the physical `<ethX>` Ethernet interface associated with a Pseudo
Ethernet `<interface>`.
|
