Can anyone explain how the networking/routing is setup in VZ and what technologies are used? Mainly, I'd like to know how venet0 is setup and what kind of device it is. I can see from scripts how VZ adds a static route and sends out arp replies to neighbors to update arp cache, but I suspect there is more to it than that. Any help in understanding this would be great because I hate being clueless about a product I use.
venet looks like a virtual Point-to-Point connection between VPS and VE0 (hostOS) So that VPS IP can be seen from outside you need to add the route on VE0
The thing that boggles my mind is how you can reach VZPP on the IP assigned to a VE when the VE isn't mounted. I've tried setting up a virtual network device like VZ does including setting up the route with a src IP of that virtual device and sent out arp notices as well like I see they do. Nothing I do allows me to trace the IP to the src IP. I'm just trying to get a grip on this because it's very interesting to me. Below are commands I've used to test this. 1. Create a virtual device first, we'll call it virt0 and bring it up. 2. ip route add 192.168.1.2 dev virt0 src 192.168.1.3 3. ip neigh add proxy 192.168.1.2 dev eth0 4. /usr/sbin/arpsend -c 1 -w 1 -U -i 192.168.1.2 -e 192.168.1.2 virt0 Perhaps this goes beyond the discussions of this board, but I thought someone might know here how exactly to set something like this up for an example of how it works with VZ.
heh VZPP is commercial VZ feature, sorry... it is our small know-how ... do you want to implement a similar offline management?
Yes, I'd like to implement a similiar setup for my own benefit. I can certainly come up with other ideas, but this interests me and I'd like to use it if I can get it to work.