| Re: Need help with OVZ networking implementation! [message #14791 is a reply to message #14739] |
Tue, 10 July 2007 19:38   |
joelee
Messages: 63
Registered: April 2006
|
Member |
|
|
| Quote: |
If you use the venet implementation you don't need to make all those aliases to the eth0 interface.
The venet0 interface behaves like an aliased interface all ready.
|
O.K, I did not realize this. It seems to me when I create basic VPS and look inside the /etc/network/interface file they all have the same default network/IP configuration - And, I assume they are bridged to the Host network. So, can I change the networking setup to different "subnets" AND not have to do anything on the host side? However, can you tell me if there would be a problem doing the sub-interfaces as well? (I will test this scenario anyway).
| Quote: |
The question is "Why do you want such a setup?".
Why do double nat (have a private ip address space IN a private ip address space) ?
|
You are right, I don't wish to do NAT between the HOST and VE... My external FW is already doing all the NAT. However, I do want a fw/iptable setup on HN just to do some filtering - But, no NATs.
| Quote: |
You can put the HN on the internet using a public ip on the eth0 interface and have the VE's in aprivate ip address space and do SNAT/DNAT for them.
|
Per above, my HN will not be directly on the internet. The HN will sit behind my external FW which is doing all NAT stuff and just MAPPING external public IP to Internal Host and just some general policies.
Based on my explanation above, would appreciate if you can further comment if I am on the same page.
The only thing I was not sure on if it would be o.k to change the networking setting to be on different subnets from the default network configs it generates.
Joe
[Updated on: Tue, 10 July 2007 19:40] Report message to a moderator |
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
