No network access on bridged VM

[sarmiena]

I'm not sure exactly what is going wrong, but I cannot get network access on my Proxmox VMs.

The host machine had Debian 6.0.4 64bit installed by my hosting provider (Softlayer). I then installed Proxmox 2.0 as per instructions given on http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze.

When I rebooted and logged into the Proxmox web interface, I went to "Network" tab and noticed there was no "vmbr0". Here is what my /etc/network/interfaces file looked like:

# network interface settings
auto lo
iface lo inet loopback


auto eth0
iface eth0 inet static
#pre-up /sbin/ethtool -s eth0 autoneg off speed 100 duplex full
address 10.25.xxx.yyy
netmask 255.255.255.192
up route add -net 10.0.0.0/8 gw 10.25.xxx.yyy


auto eth1
iface eth1 inet static
#pre-up /sbin/ethtool -s eth1 autoneg off speed 100 duplex full
address 208.43.eee.ggg
netmask 255.255.255.192
gateway 208.43.eee.fff

In order to get "vmbr0" to show up as an option in the Proxmox 2.0 web gui, I modified my interfaces file to look like this:

auto lo
iface lo inet loopback


iface eth0 inet manual
#pre-up /sbin/ethtool -s eth0 autoneg off speed 100 duplex full


auto eth1
iface eth1 inet static
#pre-up /sbin/ethtool -s eth1 autoneg off speed 100 duplex full
address 208.43.eee.ggg
netmask 255.255.255.192
gateway 208.43.eee.fff



auto vmbr0
iface vmbr0 inet static
  address 10.25.xxx.yyy
  netmask 255.255.255.192
  up route add -net 10.0.0.0/8 gw 10.25.xxx.yyy
  bridge_hello 3
  bridge_maxage 12
  bridge_ports eth0
  bridge_stp off
  bridge_fd 0

This is what the host shows for bridges:

# brctl show
bridge name    bridge id        STP enabled    interfaces
vmbr0        8000.003048dda33c    no        eth0
vmbr0v1        8000.003048dda33c    no        eth0.1
                            tap100i0

This allowed me to select vmbr0 when creating a VM in bridged mode, but installation of a Debian 6.0.4 Squeeze VM failed to detect a network (apparently because it couldn't access a DHCP server).

Also, the VM has no routing entries using netstat -nr

What's the problem???

 

[sigxcpu]

You are using tagged VLAN 1 for the VM. Is this how it should work?

 

[sarmiena]

I'm not exactly sure how it should work. Do you have any suggestions on how I could change my configuration to get things working?

 

[sigxcpu]

I'm not exactly sure how it should work. Do you have any suggestions on how I could change my configuration to get things working?

Your VM 100 has its tap interface in tagged VLAN1 (in bridge vmbr0v1 along with eth0.1).

Also, are you expecting that the Debian should find a DHCP server? Do you have it installed?

 

[sarmiena]

TBH, I'm not sure about how tagging works. Is that something that would have been done manually when creating the VM through the GUI?

If so, it was definitely not intentional.

Also, I was able to get access to my private network by using VirtIO instead of Realtec adapter. So the problem is somewhat solved.

So, as things stand now, my VM is using the Proxmox server's eth0 ip address as the gateway:

# The loopback network interface
auto lo
iface lo inet loopback


# The primary network interface
allow-hotplug eth0
iface eth0 inet static
        address 10.25.250.71
        netmask 255.255.255.192
        network 10.25.250.64
        broadcast 10.25.250.127
        gateway 10.25.250.65 #>> This is the same gateway eth0 on Proxmox server uses <<
        # dns-* options are implemented by the resolvconf package, if installed
        dns-nameservers 10.0.80.11
        dns-search stuff.com
        up route add -net 10.0.0.0/8 gw 10.25.250.65

Now I just need to figure out how to get internet access on the VM (since 10.x.x.x is my private network). Can this be done entirely using NAT on the Proxmox server?

 

[sigxcpu]

Why don't you post the VM configuration here?

You can find it in /etc/pve/local/qemu-server/<VMID>.conf

 

[sarmiena]

bootdisk: virtio0
cores: 2
ide2: local:iso/debian-6.0.4-amd64-CD-1.iso,media=cdrom
memory: 1024
name: web-02
net0: virtio=1E:D4:32:D6:6F:53,bridge=vmbr0
ostype: l26
sockets: 1
virtio0: hdd:vm-101-disk-1

 

[sigxcpu]

I think you should select "NAT" mode in the VM network interface configuration first.
With your configuration, the VM works like having a physical interface in vmbr0 LAN segment through bridging.

 

[synet2k]

Is there any solution found?

 

[Bashar]

yeah me two in the same scenario

 

[mbrito]

Hi... after hours , I resolve my problem
I remove the VM and clone another one lol
now I can keep on going