bridging issue

[ancly2008]

I encountered an issue while testing bridging in OpenWRT. Edge1 and Edge2 have already established P2P connections (both interfaces are Tun0). Then, bridge tux0 and eth1 on the edge1 device. Similarly, bridge tux0 and eth1 on the edge2 device. At this point, I found that the original normal P2P connection became disconnected
Do it support bridging configuration in this way ?
I don't know if n3n can support L2 bridging, so that eth1 of two devices can form an L2 connection

[hamishcoleman]

N3N does have support for bridging the tun device with other network interfaces and it is not supposed to affect the P2P connection.

I will need to build a test network with enough devices to actually run bridging between them to be able to investigate this issue.

[leonardospeca]

Same problem, same scenario, in the moment that the bridge is done, the p2p connection became disconnected

[SerinaNya]

any progress?

[catoc]

In your scenario, if eth1 is your WAN interface and your public/exit IP is bound directly to eth1, adding both tux0 and eth1 to the same bridge will cause a global network disruption. This happens because the physical interface loses its individual IP configuration when it becomes a bridge member, tearing down the existing P2P tunnels.
To resolve this, please follow these steps:

1. Create a bridge first: Establish a bridge (e.g., br-wan) and add eth1 to it.
2. Bind the IP to the bridge: Ensure your exit IP address is bound to br-wan rather than the raw eth1 interface.
3. Add the n3n interface: Once the n3n edge is fully started and the tunnel is established, add tux0 to the br-wan bridge.

[ancly2008]

eth0 is wan port ,eth1 just for test bridge