linux can access internet, windows can't

de Thysebaert

Mar 12, 2017
on a new fresh install of a cluster (proxmox 5), with 2 nodes and one qdevice for quorum, connected to vrack infrastructure at ovh, a have an issue with connectivity.
The first physical network card (eno1) is connected directely to internet with his public ip for management.
The second card, (eno2) is connected to the virtual switch at OVH (vrack service).
vmbr1 is bridged on vlan 200 (eno2.200) for communication between nodes (all is ok here)
vmbr2 is bridged on vlan 100 (eno2.100) for private lan with private ip and VM can communicate.
vmbr3 is bridged to eno2 (no vlan specified) for public VM with public IP (block IP RIPE from OVH)

VM with linux (ubuntu 16.04 LTS) connected to the vmbr3 and configured with public IP can access the internet througn the vrack
VM with the same config CAN'T acces the net, cannot ping the default gateway , mac address seams to be not correct for this gateway


here my config for proxmox

# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
# If you want to manage part of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

auto eno1
iface eno1 inet manual

auto eno2
iface eno2 inet manual


auto vmbr0
iface vmbr0 inet static
address 54.38.xx.xx
gateway 54.38.xx.xx
broadcast 54.38.xx.xx
bridge_ports eno1
bridge_stp off
bridge_fd 0
network 54.38.xx.xx

auto vmbr1
iface vmbr1 inet static
bridge_ports eno2.100
bridge_stp off
bridge_fd 0

auto vmbr2
iface vmbr2 inet static
bridge_ports eno2.200
bridge_stp off
bridge_fd 0
#private network

auto vmbr3
iface vmbr3 inet manual
bridge_ports eno2
bridge_stp off
bridge_fd 0
bridge_vlan_aware yes
bridge_fd 0
#Public network through Vrack

auto vmbr4
iface vmbr4 inet manual
bridge_ports dummy0
bridge_stp off
bridge_fd 0


Proxmox Staff Member
Staff member
Mar 6, 2015
Probably the VM's MAC address is not accepted by OVH.

To be sure traffic investigation (wireshark resp. tcpdump) at all critical point (inside VM, bridge ports, bridge) necessary.


The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!