OVH Community, your new community space.

Proxmox 1.5, failover and virtual MAC cannot get from public to VM


yatesco
01-02-2010, 12:02
**** SOLVED **** Windows 7 got confused about which network it was connected to - turning off the firewall worked. This obviously isn't the solution but routing works fine. Also, remember to set RDP to accept any connections, not just super secure ones.

Hi all,

I have a standard (EG) Proxmox 1.5 install with a single Windows7 VM. I am using vmbr0 with a fail over which has a virtual MAC assigned to it.

The VM7 configuration is:

IP: failover
netmask: 255.255.255.255
gateway: gateway of the physical machine (also tried failover)

Good news is that the VM can connect to the public, but the public cannot connect to the VM - ping and RDP time out (even though the firewall is disabled.

Relevant bits:

traceroute:
Code:
 8  20g.rbx-1-6k.routers.chtix.eu (91.121.131.13)  217.693 ms *  219.772 ms
 9  rbx-60-m1.routers.chtix.eu (91.121.130.52)  23.047 ms  26.215 ms  21.451 ms
10  * * *
on the host (unmodified):
Code:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# for Routing
auto vmbr1
iface vmbr1 inet manual
        post-up /etc/pve/kvm-networking.sh
        bridge_ports dummy0
        bridge_stp off
        bridge_fd 0


# vmbr0: Bridging. Make sure to use only MAC adresses that were assigned to you.
auto vmbr0
iface vmbr0 inet static
        address x
        netmask 255.255.255.0
        network x
        broadcast x
        gateway x
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0
ip route show
Code:
x/24 dev vmbr0  proto kernel  scope link  src x 
default via x dev vmbr0
ip route show
Code:
x/24 dev vmbr0  proto kernel  scope link  src x 
default via x dev vmbr0
brctl show
Code:
bridge name     bridge id               STP enabled     interfaces
vmbr0           8000.001cc072f23d       no              eth0
                                                        vmtab2101i0
vmbr1           8000.3607cad7e501       no              dummy0
I also tried using the failover IP as the gateway with the same effect.

Any ideas - *many* thanks for any help.