Bridge won't start because of bridge-ports issues

[Marathon]

does is ipv6 routing works before reload ?
and is
net.ipv6.conf.all.forwarding=1 enabled in sysctl.conf ?


what is the value of "cat /proc/sys/net/ipv6/conf/all/forwarding" ?


(also, do you have the same problem with option "ip6-forward yes" ?)


I'll try to reproduce with ipv6 today or tomorrow.

It's a little bit hard to answer, it worked before and ipv6 forwarding is enabled:

# cat /proc/sys/net/ipv6/conf/all/forwarding
1

From a VM it's stalled after the command has been started but on Proxmox itself it goes OK.

• Ping works great from the VM to HV
• Traceroute from VM to HV gives back * * *
• Ping from HV to VM doesn't give reply
• Traceroute from HV to VM is also a !H

I'm pretty sure it's not a firewall issue but I'm not sure what it can be otherwise, it started after the bridge issues/changes.

 

[Marathon]

Any update on this from your side spirit ?

 

[spirit]

Hi, i was very busy last weeks, i ll try to test IPv6 next week

 

[Marathon]

No problem, me as well! Let's teamup again

 

[spirit]

No problem, me as well! Let's teamup again

Hi,
could you send me your ipv6 setup (/etc/network/interfaces of proxmox host) ?

I've prepared my ipv6, I'll like to have same exact config than you.

 

[Marathon]

Hi,

Sure sorry for the delay but can you post yours ? I would like to test upfront, I might see some flaw.

Thanks!

 

[spirit]

Hi,

Sure sorry for the delay but can you post yours ? I would like to test upfront, I might see some flaw.

Thanks!

Hi,
I only have prepared my ipv6 network currently (routers).
I would like to known if your proxmox host is the ipv6 gateway for your vms ? or if the gateway is an external router after proxmox host ?

 

[Marathon]

Hi,
I only have prepared my ipv6 network currently (routers).
I would like to known if your proxmox host is the ipv6 gateway for your vms ? or if the gateway is an external router after proxmox host ?

My Proxmox host is the GW for my VM's indeed. It's a port routed subnet for the host, so that is why.

 

[chengkinhung]

Hi, I encounter the same issue, host network interface lost settings after add another linux bridge, seems proxmox is using incorrect debian network interface options when modifing the /etc/network/interfaces files. Debain system seems only accept "_" but proxmox is using "-", for exampel, debian is using bridge_ports but proxmox is using "bridge-ports":

# pveversion
pve-manager/6.0-4/2a719255 (running kernel: 5.0.15-1-pve)

--- /etc/network/interfaces    2019-12-03 16:58:58.740002264 +0800
+++ /etc/network/interfaces.new 2019-12-08 15:49:33.452984474 +0800
@@ -1,15 +1,36 @@
+# network interface settings; autogenerated
+# Please do NOT modify this file directly, unless you know what
+# you're doing.
+#
+# If you want to manage parts of the network configuration manually,
+# please utilize the 'source' or 'source-directory' directives to do
+# so.
+# PVE will preserve these directives, but will NOT read 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

iface eno1 inet manual

+iface eno2 inet manual
+
auto vmbr0
iface vmbr0 inet static
address 192.168.x.x
netmask 255.255.255.0
gateway 192.168.x.x
- bridge_ports eno1
- bridge_stp off
- bridge_fd 0
+ bridge-ports eno1
+ bridge-stp off
+ bridge-fd 0
+
+auto vmbr1
+iface vmbr1 inet manual
+ bridge-ports eno2
+ bridge-stp off
+ bridge-fd 0
+ bridge-vlan-aware yes
+ bridge-vids 2-4094
+#VM internet interface bridge

-iface eno2 inet manual
[/CODE

 

[spirit]

>>Debain system seems only accept "_" but proxmox is using "-", for exampel, debian is using bridge_ports but proxmox is using "bridge-ports":

no, that's wrong, debian ifupdown support both "_" && "-"

 

[chengkinhung]

Thanks, when changed networking, PVE notice need to reboot hostnode, however networking lost after reboot, I need to go to hardware console to restart network. This issue is not the first time happening.