[PVE-User] Can´t ping to the outside - OVH Proxmox 5.3

[Miguel González]

Hi Stephan,

  I use public failover IP addresses. I ask about your gateway
configuration, you use:

  91.121.183.137

  and as far as I know, the gateway must be the public IP address of the
host ending with .254. That´s what OVH says in their docs.

  Thanks!

On 12/15/18 2:43 PM, Stephan Leemburg wrote:
> OVH Requires you to route traffic from VM's via the IP address of your
> hardware.
>
> So 137 is the ip address of the hardware.
>
> Do you use any public ip addresses on your soyoustart system?
>
> Or just private range and then send them out via NAT?
>
> Met vriendelijke groet,
> Stephan Leemburg
> IT Functions
>
> e: sleemburg at it-functions.nl
> p: +31 (0)71 889 23 33
> m: +31(0)6 83 22 30 69
> kvk: 27313647
>
> On 15-12-18 14:39, Miguel González wrote:
>> There must be something wrong with the configuration since I have tested
>> another server and seems to be fine.
>>
>> Why do you use 137? In the proxmox docs they say the gateway is
>> xxx.xxx.xxx.254
>>
>> Thanks!
>>
>>
>> On 12/15/18 2:16 PM, Stephan Leemburg wrote:
>>> Did you setup routing correctly within the containers / vm's?
>>> OVH/SoYouStart has awkward network routing requirements.
>>>
>>> I have 2 servers at soyoustart and they do fine with the correct
>>> network configuration.
>>>
>>> Below is an example from one of my containers.
>>>
>>> Also, it is a good idea to setup a firewall and put your containers on
>>> vmbr devices connected to the lan side of your firewall.
>>>
>>> Then on the lan side you have 'normal' network configurations.
>>>
>>> The pve has ip address 91.121.183.137
>>>
>>> I have a subnet 54.37.62.224/28 on which containers and vm's live.
>>>
>>> # cat /etc/network/interfaces
>>>
>>> auto lo
>>> iface lo inet loopback
>>>
>>> auto eth0
>>> iface eth0 inet static
>>>      address 54.37.62.232
>>>      netmask 255.255.255.255
>>>      pre-up /etc/network/firewall $IFACE up
>>>      post-up ip route add 91.121.183.137 dev $IFACE
>>>      post-up ip route add 54.37.62.224/28 dev $IFACE
>>>      post-up ip route add default via 91.121.183.137 dev $IFACE
>>>      post-down ip route del default via 91.121.183.137 dev $IFACE
>>>      post-down ip route del 54.37.62.224/28 dev $IFACE
>>>      post-down ip route del 91.121.183.137 dev $IFACE
>>>      post-down /etc/network/firewall $IFACE down'
>>>
>>>
>>> Met vriendelijke groet,
>>> Stephan Leemburg
>>>
>>> On 15-12-18 13:02, Miguel González wrote:
>>>> Hi,
>>>>
>>>>      I am migrating some VMs from a Soyoustart (OVH) Proxmox 5.1 to a
>>>> brand new Proxmox 5.3 server (again Soyoustart).
>>>>
>>>>      I have followed the instructions from OVH and Proxmox and I
>>>> can ping
>>>> from the VM to the host and the gateway and I can ping from the
>>>> host to
>>>> the VM. But I can´t ping the DNS server or anything outside the host
>>>> machine (i.e.: the legacy Proxmox host).
>>>>
>>>>     Some people suggest to enable ip forwarding, but I don´t have
>>>> enabled
>>>> on the legacy server.
>>>>
>>>>     But I enable it anyway echo 1 > /proc/sys/net/ipv4/ip_forward
>>>>        and nothing happens.
>>>>
>>>>     iptables seems to be turned off both in host and vm:
>>>>
>>>>      iptables -L
>>>> Chain INPUT (policy ACCEPT)
>>>> target     prot opt source               destination
>>>>
>>>> Chain FORWARD (policy ACCEPT)
>>>> target     prot opt source               destination
>>>>
>>>> Chain OUTPUT (policy ACCEPT)
>>>> target     prot opt source               destination
>>>>
>>>> So I´m out of ideas here
>>>>
>>>> Any suggestion?
>>>>
>>>> Miguel
>>>>
>>>>
>>>>
>>>> ---
>>>> This email has been checked for viruses by AVG.
>>>> https://www.avg.com
>>>> _______________________________________________
>>>> pve-user mailing list
>>>> pve-user at pve.proxmox.com
>>>> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>