You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* vrnetlab: Add pass-through management interfaces
* vjunos: Add pass-through management interface support
* vrnetlab: Use JSON output of iproute2
* vrnetlab: Add exception for serial console ports 5000-5007 for transparent mode mgmt interface
* vrnetlab: Remove non-working port 5000 tc mirred exception, redirect to correct interface
* vrnetlab: Use tc clsact qdisc and flower matching as best practice
* vrnetlab: Re-add workaround for serial ports in transparent mgmt mode
* vrnetlab: Add IPv6 support to management address/gw functions
* vjunos: Add IPv6 management addresses, fix v4 address templating
* vrnetlab: Set dummy IPv6 address/gw for hostfwd management
Copy file name to clipboardExpand all lines: README.md
+16
Original file line number
Diff line number
Diff line change
@@ -39,6 +39,22 @@ Other connection mode values are:
39
39
* ovs-bridge - same as a regular bridge, but uses OvS. Can pass LACP traffic.
40
40
* macvtap
41
41
42
+
## Management interface
43
+
44
+
There are two types of management connectivity for NOS VMs: _pass-through_ and _host-forwarded_ (legacy) management interfaces.
45
+
46
+
_Pass-through management_ interfaces allows the use of the assigned management IP within the NOS VM, management traffic is transparently passed through to the VM, and the NOS configuration can accurately reflect the management IP. However, it is no longer possible to send or receive traffic directly in the vrnetlab container (e.g. for installing additional packages within the container), other than to pre-defined exceptions, such as the QEMU serial port on TCP port 5000.
47
+
48
+
NOSes defaulting to _pass-through_ management interfaces are:
49
+
- All vJunos routers
50
+
51
+
In case of _host-forwarded_ management interfaces, certain ports are forwarded to the NOS VM IP, which is always 10.0.0.15/24. The management gateway in this case is 10.0.0.2/24, and outgoing traffic is NATed to the container management IP. This management interface connection mode does not allow for traffic such as LLDP to pass through the management interface.
52
+
53
+
NOSes defaulting to _host-forwarded_ management interfaces are:
54
+
- Every NOS not listed as pass-through management
55
+
56
+
It is possible to change from the default management interface mode by setting the `CLAB_MGMT_PASSTHROUGH` environment variable to 'true' or 'false', however, it is left up to the user to provide a startup configuration compatible with the requested mode.
57
+
42
58
## Which vrnetlab routers are supported?
43
59
Since the changes we made in this fork are VM specific, we added a few popular routing products:
0 commit comments