RE: gretap tunnel redirecting 2 different networks on destination host to nics

"Marc Roos" <[email protected]>
Newsgroups org.kernel.vger.lartc
Message-ID <"H00000710011525e.1523093043.sx.f1-outsourcing.eu*"@MHS>
Update on this. 
Pinging from 172.16.1.y to br0 is not received, cannot see it arrive 
with tcpdump on eth2. However doing a broadcast ping is being seen on 
eth2.


-----Original Message-----
From: Marc Roos 
Sent: zaterdag 7 april 2018 7:11
To: gtaylor; lartc
Subject: RE: gretap tunnel redirecting 2 different networks on 
destination host to nics

 

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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.