new brigde networks problems

  • Thread starter Thread starter llazzaro
  • Start date Start date
L

llazzaro

Guest
I have created a new bridge vmbr1 attached to eth1.

One container is attached to that bridge. But that vm dont get any ip from the dhcp server. Proxmox can ping the server at that subnet.

More data, CT102 now have an static ip 192.168.1.23 I could ping promox box with 192.168.1.20 (bridge static ip). Proxmox could also ping the CT102, but inside CT102 I cant ping the gateway (192.168.1.1) however proxmox pings 192.168.1.1!

route problem?

I also check this
http://wiki.openvz.org/Bridge_doesn't_forward_packets

In /proc/sys/net/bridge/ all was with 1 , changed but nothing works...
I also run
iptables -A FORWARD -d 255.255.255.255 -j ACCEPT

this is my configuration

bridge name bridge id STP enabled interfaces
vmbr0 8000.001bb993454a no eth0
veth101.0
veth104.0
veth105.0
veth106.0
vmbr1 8000.001f1f1259ef no eth1
veth102.0
veth103.0
vmbr2 8000.000000000000 no

proxmox:~# ip route show
192.168.1.0/24 dev vmbr1 proto kernel scope link src 192.168.1.20
172.16.0.0/24 dev vmbr0 proto kernel scope link src 172.16.0.7

no clue, thanks a lot!

switching CT102 to vmbr0 bridge gets ips from the subnet 172.16.0.0
 
solved

echo 1 > /proc/sys/net/ipv4/conf/vmbr1/proxy_arp

the problem was eth1 dont have link up at boot
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, 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 yours easily in our online shop.

Buy now!