New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
What issues?
well when I add an IP address from the block to a virtual server in solusvm and try to connect in putty it just doesn't work, when I run xm console and try pinging google it doesn't work either, the IP seems to be added when I run ifconfig on the vm but it can't reach anything
The following pages might be useful to you:
http://wiki.hetzner.de/index.php/Kategorie:Xen
http://wiki.hetzner.de/index.php/Zusaetzliche_IP-Adressen/en
You might need to get Virtual MAC for each IP & add it manually in SolusVM.
I am using Hetzner servers only and unfortunately they allocated me pool with a different subnet. somehow their failover ips does not work until you create routing file in each vps which is mentioned in their wiki http://guide.ovh.com/BridgeClient as
filename - route-eth0 and contents as -
GATEWAY_VM dev eth0
default via GATEWAY_VM dev eth0
the gateway should be main ip of your dedi server and this file needs to be created insdie vm. since it will be reset in each reboot the only option left is to configure images manually including this routing in each of them
Have you made sure your /etc/resolv.conf has correct nameservers?
Hetzner has different network setup than most other data centers, they use some kind of MAC filtering. Because of that, you need to take a bit of a different approach when using their IP's with virtualization.
In the case of SolusVM+Xen, you need to bridge one of the IP's in your subnet, and use that IP as the gateway in your IP block. That IP cannot be used for VM's of course, so you will need to 'reserve' it in SolusVM.