Mapping physical subinterfaces to vRouter native interfaces

Before posting something, READ the changelog, WATCH the videos, howto and provide following:
Your install is: Bare metal, ESXi, what CPU model, RAM, HD, what EVE version you have, output of the uname -a and any other info that might help us faster.

Moderator: mike

Post Reply
steve71
Posts: 3
Joined: Wed Aug 08, 2018 1:02 pm

Mapping physical subinterfaces to vRouter native interfaces

Post by steve71 » Thu Aug 09, 2018 8:53 am

HW: Dual E5-2650, 64GB, 150GB, 4xGE & 2x10GE
Type: Bare metal
Ubuntu: Ubuntu 16.04.5 LTS
eve-ng: 2.0.3-92

For our testing, we need to connect one or more native interface on each vRouters to a different tagged sub-interfaces of a physical port on the host. I can't see any easy way of doing this. I realise that I could hack the /etc/network/interfaces to statically bridge ethX.Y sub-interfaces to different pnet images but I'm hoping that there is a better way.

Also - is there a limit on the number of pnetX interfaces that can be used? In some labs we need more than the default 10 pnet interfaces if each one is mapped to a physical sub-interface.

Uldis (UD)
Posts: 1617
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:

Re: Mapping physical subinterfaces to vRouter native interfaces

Post by Uldis (UD) » Thu Aug 09, 2018 9:10 am

Isn't better to use classic trunk port connected to virtual router and your tagged dot1q interfaces reach whatever you need over it.
EVE pnet bridged with server nic---trunk to---real sw
Rest simple VLANs SVI will do the job

Uldis

steve71
Posts: 3
Joined: Wed Aug 08, 2018 1:02 pm

Re: Mapping physical subinterfaces to vRouter native interfaces

Post by steve71 » Thu Aug 09, 2018 9:34 am

That might work for my current technology demonstration but if, as I hope, budget is approved for upgrading to the Corporate solution (with ~4-10 users), the different labs from different users would really need to share the same physical interfaces using different VLANs.

This wouldn't seem easy to achieve with a vRouter acting effectively as a switch breaking out a single physical trunk to lots of access interfaces or have I overlooked something about how different labs run by different users could communicate with this proposed "shared virtual switch" in the Corporate version?

Uldis (UD)
Posts: 1617
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:

Re: Mapping physical subinterfaces to vRouter native interfaces

Post by Uldis (UD) » Fri Aug 10, 2018 12:52 am

Steve,
please visit our live chat to talk about it..
I guess we have diff way solution you want...

Uldis

http://www.eve-ng.net/live-helpdesk

use google account or create new to join...

UD-EVE

Post Reply

Who is online

Users browsing this forum: No registered users and 7 guests