[SOLVED] Upgrade 4.2 broke network config

Trevor Cilmo

New Member
Sep 26, 2016
3
0
1
33
Hello everyone,
quite late, I upgraded my proxmox pve to the 4.2 version, but since, my containers can't access the internet.

I use a bridged configuration which was working so far :
Code:
auto lo
iface lo inet loopback

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

auto vmbr0
iface vmbr0 inet static
        pre-up iptables-restore < /etc/iptables.rules
        address 37.x.x.111
        netmask 255.255.255.0
        gateway 37.x.x.254
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0

iface vmbr0 inet6 static
  address 2001:41D0:A:676f::1
  netmask 64
  post-up /sbin/ip -f inet6 route add 2001:41D0:A:67ff:ff:ff:ff:ff dev vmbr0
  post-up /sbin/ip -f inet6 route add default via 2001:41D0:A:67ff:ff:ff:ff:ff
  pre-down /sbin/ip -f inet6 route del default via 2001:41D0:A:67ff:ff:ff:ff:ff
  pre-down /sbin/ip -f inet6 route del 2001:41D0:A:67ff:ff:ff:ff:ff dev vmbr0

auto vmbr0:0
iface vmbr0:0 inet static
  address 192.168.4.1
  netmask 255.255.255.0
  network 192.168.4.0
  broadcast 192.168.4.255

With my current provider (OVH), I need to use an alias to make the bridge works, and this specific config is not helping when seeking help on a search engine ...

From the containers I can ping the gateway (192.168.4.1), but nothing else. I also tried by creating a new one CT, but same results : my guess is that the gateway is broken somehow, but I don't know how to fix it :/

Any help would be welcomed !
 
Hello,
as I rely on my server for many services, I'd appreciate if someone skillful could give me an advice on that issue :/
BTW I just upgraded it to 4.3, still the same
Thanks
 
Last edited:
I fixed it by uncommenting
Code:
net.ipv4.ip_forward=1
in
Code:
/etc/sysctl.conf
I guess it has been reseted without my knowledge...
Anyway, problem solved !