-
Notifications
You must be signed in to change notification settings - Fork 324
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connecting interface of xrv9k instance with the external world #334
Comments
Yes, vr-xcon has a tap mode which can bridge from its "native form", which is the qemu style TCP sockets, to a tap device. Use such a vr-xcon instance on the host machine. Bridge the tap interface to a bridge which also connects to the physical interface. Use your normal vr-xcon instance to connect to this vr-xcon instance and connect it to whatever virtual router you want. It probably means that both vr-xcon needs to run in the host network namespace. |
Thanks for the reply @plajjan Can you share a sample command for the same ? |
vr-bgp runs xcon in tap mode, see https://github.com/vrnetlab/vrnetlab/blob/master/vr-bgp/vr-bgp.py#L173 So Since xcon is running on localhost, now you need your other vr-xcon instance, the "normal one" and connect your virtual router to localhost, like so |
Hi All,
I am new to vrnetlab and I really had fun deploying the initial setup with xrv9k instances.
Is it possible to connect the interfaces on XRV9K instance with the external world via physical interfaces in the server ?
The text was updated successfully, but these errors were encountered: