I managed to make this windows server unreachable somehow. So I extended
the test just by simply adding eth1 to the bridge.
This did not seem to affect the connectivity of 172.16.1.x. However from
this point, I could not ping from the br0 172.16.1.y anymore. Although I
see with tcpdump icmp and arp packets on the eth2 interface and nothing
on eth1.
When I only remove eth1 with brctl delif br0 eth1, ping is working to
172.16.1.y. Do you know what this could be?
+-----------+
| BR0 |
172.16.1.y | | 172.16.1.x
--------|ETH2 TUN1|-------
| |
| | 172.16.1.x
| TUN2|-------
--------|ETH1 |
+-----------+
--
To unsubscribe from this list: send the line "unsubscribe lartc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
