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.
Need a tech for 2 hours
Hi
I need a tech for a couple of hours to help me get my head round a solus internal network problem.
I'm not sure if its solus or the iptables rules that's causing the problem, or even possibly the hetzner network config we implemented to enable additional IP's.
Anyone want to earn a few $ and help me understand where the issues is ? Or even better .... anyone feeling charitable and want to help out for free 
Nik
Comments
@jhadley :-)
Thanks for the recommendation, @budingyun. Would be glad to help out - there's a bit about me at www.sysadmin.co.uk and my email address is me[at]jhadley.net.
@jhadley - pinged you and email
Whats the problem anyways? I bet someone can help you out in this thread
Basically, my solus slave can ping internal ips of VM's .... and the VM's can ping the virbr0 interface on the host with the internal ip, but they can't ping each other
@nikc I believe via my experience with OVH, which is basically setup the same way, you have to deal with telling the VMs and the host node how to route the data. Here is one bit of info on their site.
If you look here: http://wiki.hetzner.de/index.php/KVM_mit_Nutzung_aller_IPs_-_the_easy_way/en#Host you see how they are setting up the route. Also a bit of info here on the bridge and adding the MAC address via the hetzner robot and how to do the route with specific (CentOS for solus) OS configs. http://wiki.hetzner.de/index.php/Zusaetzliche_IP-Adressen/en#Bridged