Hi Benny,
From: "Benny Amorsen" <[email protected]>
"Daniel Bauer" <[email protected]> writes:
I've several nics on the hostnode. Only the internal service nic have
an
internal IP. The other nics are without IPs and connected to
different
internal subnets and public www.
I've read the differences between venet and veth
http://wiki.openvz.org/Differences_between_venet_and_veth
and want to use venet, but only venet0 is active in the hn, I think
this
is connected to eth0, but how to access the other nics?
What we do is a bit simpler: Just add the appropriate NIC into the
guest. This way the host loses access to the NIC and the guest can be
configured in exactly the same way a non-virtualized server would be
configured. Routing and firewalling is then done by our usual routers
and firewalls, again exactly like it works for non-virtualized
servers.
To avoid having to put 50 NIC's in each VZ server we actually do it
with
VLAN interfaces rather than NIC's.
It's an really interesting solution. I've to look at the VLAN technic,
because I've never used it.
One thing was, that nobody - only the HN - could change the IP for a CT.
This issue couldn't be solved by VLAN or veth, so I thought to use
venet.
Now I think I'll prefer the bultin veth technic to solve my problem
right now.
Thanks a lot
Daniel
_______________________________________________
Users mailing list
[email protected]
https://openvz.org/mailman/listinfo/users
