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
Copy file name to clipboardexpand all lines: README.md
+19-1
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ project itself, consider reading the [docs of the upstream repo](https://github.
11
11
## What is this fork about?
12
12
13
13
At [containerlab](https://containerlab.srlinux.dev) we needed to have
14
-
[a way to run virtual routers](https://containerlab.srlinux.dev/manual/vrnetlab/)
14
+
[a way to run virtual routers](https://containerlab.dev/manual/vrnetlab/)
15
15
alongside the containerized Network Operating Systems.
16
16
17
17
Vrnetlab provides perfect machinery to package most-common routing VMs in
@@ -80,6 +80,24 @@ Full list of connection mode values:
80
80
| ovs-bridge | :white_check_mark: | Same as a regular bridge, but uses OvS (Open vSwitch).
81
81
| macvtap | :x: | Requires mounting entire `/dev` to a container namespace. Needs file descriptor manipulation due to no native qemu support.
82
82
83
+
## Management interface
84
+
85
+
There are two types of management connectivity for NOS VMs: _pass-through_ and _host-forwarded_ (legacy) management interfaces.
86
+
87
+
_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.
88
+
89
+
NOSes defaulting to _pass-through_ management interfaces are:
90
+
91
+
* None so far, we are gathering feedback on this, and will update this list as feedback is received. Please contact us in [Discord](https://discord.gg/vAyddtaEV9) or open up an issue here if you have found any issues when trying the passthrough mode.
92
+
93
+
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.
94
+
95
+
NOSes defaulting to _host-forwarded_ management interfaces are:
96
+
97
+
* all current systems
98
+
99
+
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.
100
+
83
101
## Which vrnetlab routers are supported?
84
102
85
103
Since the changes we made in this fork are VM specific, we added a few popular
0 commit comments