I have a dedicated server running multiple IPv6 only OpenVZ containers. I want them to be able to communicate with the IPv4 internet, but I realized that isn't going to be possible with IPv6 only. So they need to have an IPv4 address as well, not sure if a local address will work for it, but pretty sure it should.
I added 169.254.1.100 in the container .conf file, but when I try to start it, I get this :
Adding IP address(es): (the IPv6 address) 169.254.1.100
arpsend: 169.254.1.100 is detected on another computer : 00:04:9b:f2:b0:00
vps-net_add WARNING: arpsend -c 1 -w 1 -D -e 169.254.1.100 eth0 FAILED
What should I do now?
169.254.x.x is not usable as an internal network. Try using 192.168.x.x
Obviously they won't be able to communicate with the IPv4 internet on these addresses.
that is the link-local address range for IPv4. I'll try using 192.168.x.x, but what I want is the containers to be able to communicate with the IPv4 internet. I guess I need to bridge the connection for this, do I?
I have 5 IPv4 addresses routed to my server, just not assigning IPv4 addresses to the openvz containers. I don't want to assign a complete address to any one container, just want them to be able to communicate with the IPv4 internet. I am assigning only IPv6 addresses to the containers.
Have you seen lowendspirit.com? They provide IPv6 only VPS with 10.10.10.xxx internal IPv4 addresses, and NATed IPv4, and their VPS's can communicate with the external IPv4 internet without any problems. How is that done then?