OVH Community, your new community space.

SolusVM & IP routing


alex
11-04-2015, 19:52
Quote Originally Posted by Neil
Perfect, vmacs are only required for KVM machines.
and XEN VMs

LawsHosting
04-04-2015, 12:42
Ok, for anyone using OpenVZ, do not follow step 2. from https://documentation.solusvm.com/di...p+Instructions - you do not need to add any rules.......

Hopefully this is sorted

LawsHosting
04-04-2015, 05:09
Ok, have found a new issue and the people I've asked have pointed this issue to be OVH's fault, either their OS image or the network.....

Issue:

So I have created 3 VMs, assigned each a master IP and some other IPs.... But when I connect outwards from the VMs (via wget etc), the destination is detecting the actual Host IP and not the VM master IP.

What could be the reason for this?

Anyone else using this OVH SolusVM image?

Neil
02-04-2015, 16:36
Perfect, vmacs are only required for KVM machines.

LawsHosting
02-04-2015, 14:35
Quote Originally Posted by Neil
Hi
Is it OpenVZ container? If so no vmac is required.
It is yes...

I'll try removing it........

And success..... pings now.....

Neil
02-04-2015, 14:20
Hi

Is it OpenVZ container? If so no vmac is required.

LawsHosting
02-04-2015, 13:38
Tried replacing mac;
Reboot the VM;
tried 'tcpdump -i eth0 src ';
12:09:11.113381 IP server1.xxxxxxx > 188.165.xxxxx: ICMP echo request, id 10133, seq 15, length 64
So, the request is getting to the server, but not to the actual VM.

Obviously I'm doing something wrong.. However, doesn't really make sense how the VM can make requests out though (tested by vzctl exec 101 ping bbc.co.uk -c 3, does it?

Ok, here's my current host details:
#ifconfig
eth0 Link encap:Ethernet HWaddr 0C:C4:7A:45:4C:0A
inet addr:5.196.90.nnn Bcast:5.196.90.255 Mask:255.255.255.0
inet6 addr: 2001:41d0:a:nnnn::/64 Scope:Global
inet6 addr: fe80::ec4:7aff:fe45:4c0a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3781428 errors:0 dropped:0 overruns:0 frame:0
TX packets:949556 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2263286942 (2.1 GiB) TX bytes:76179408 (72.6 MiB)
Memory:fb920000-fb93ffff

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:372 errors:0 dropped:0 overruns:0 frame:0
TX packets:372 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:18600 (18.1 KiB) TX bytes:18600 (18.1 KiB)

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: fe80::1/128 Scope:Link
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:257 errors:0 dropped:0 overruns:0 frame:0
TX packets:154 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:15393 (15.0 KiB) TX bytes:8207 (8.0 KiB)
--------------
#route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
188.165.xxx.xxx 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
188.165.xxx.xxx 0.0.0.0 255.255.255.240 U 0 0 0 eth0
5.196.xx.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 5.196.xx.254 0.0.0.0 UG 0 0 0 eth0
----------
# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere state NEW,RELATED,ESTABLISHED

Chain FORWARD (policy ACCEPT)
target prot opt source destination
SOLUSVM_TRAFFIC_IN all -- anywhere anywhere
SOLUSVM_TRAFFIC_OUT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere state NEW,RELATED,ESTABLISHED

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere state NEW,RELATED,ESTABLISHED

Chain SOLUSVM_TRAFFIC_IN (1 references)
target prot opt source destination
all -- anywhere 188.165.xxx.xxx

Chain SOLUSVM_TRAFFIC_OUT (1 references)
target prot opt source destination
all -- 188.165.xxx.xxx anywhere
and on the VM;
# vzctl exec 101 ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:27 errors:0 dropped:0 overruns:0 frame:0
TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1946 (1.9 KiB) TX bytes:1411 (1.3 KiB)

venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:188.165.xxx.xxx P-t-P:188.165.xxx.xxx Bcast:188.165.xxx.xxx Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1

Neil
02-04-2015, 11:37
Hi

If you ping the VM and do a TCP Dump you see the incoming requests? If so maybe remove the vmac and add it again.

LawsHosting
02-04-2015, 02:03
So, it appears that VMs can connect to the outside world, but nothing can come into them..... Very strange... Been going back and forth with the SolusVM team all day......

LawsHosting
01-04-2015, 21:18
Turns out I'm doing it all wrong (wouldn't be the first time).......

In that case, can someone elaborate on http://docs.ovh.ca/en/guides-network...-linux-clearos

LawsHosting
01-04-2015, 18:55
Ok, so for 2 days now I've been (trying) to set up SolusVM (with OpenVZ)....

I chose to opt for OVH's SolusVM/CentOS template - not sure if this was a good idea or not..

Right, I had to buy a new Ripe block to test/set up VMs... and now I am stuck....

I came across this link: http://www.lowendtalk.com/discussion...h-with-solusvm (I know it states KVM, but I guess the outline is the same?) leaving out the eth1 part.... Now, my main IP is on "br0".

Then decided to check OVH's http://docs.ovh.ca/en/guides-network...-linux-clearos and it kind of confused me, by it using and changing eth0

The IPs fail to ping from the outside.

So far:
1. Created a VirtualMac for just 2 IPs (type: ovh?) - check;
2. Added these 2 IP's to SolusVM - check;
3. Gave them the VirtualMac's given by OVH - check;
(as stated in the SolusVM docs, you need to assign/create MACs before creating VMs)
4. Created a small VM in SolusVM with an IP with a VirtualMac...
5. Try a ping to the IP.... fail..

I'd be grateful for any advice.