blob: 7564ce760a2410a6f8cdfa7578e79a608fcd9a0b (
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
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
|
.. _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-address-with-dhcp.txt
:var0: pseudo-ethernet
:var1: peth0
.. cmdinclude:: ../_include/interface-description.txt
:var0: pseudo-ethernet
:var1: peth0
.. cmdinclude:: ../_include/interface-ipv6-addr-autoconf.txt
:var0: pseudo-ethernet
:var1: peth0
.. cmdinclude:: ../_include/interface-ipv6-addr-eui64.txt
:var0: pseudo-ethernet
:var1: peth0
Physical Asignment
------------------
.. cfgcmd:: set interfaces pseudo-ethernet <interface> source-interface <ethX>
Specifies the physical `<ethX>` Ethernet interface associated with a Pseudo
Ethernet `<interface>`.
Link Administration
-------------------
.. cfgcmd:: set interfaces pseudo-ethernet <interface> description <description>
Assign given `<description>` to interface. Description will also be passed
to SNMP monitoring systems.
.. cfgcmd:: set interfaces pseudo-ethernet <interface> disable
Disable given `<interface>`. It will be placed in administratively down
(``A/D``) state.
.. cfgcmd:: set interfaces pseudo-ethernet <interface> mac <mac-address>
Configure user defined :abbr:`MAC (Media Access Control)` address on given
`<interface>`.
|
