lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:   Tue, 3 Apr 2018 06:33:43 +0200
From:   "Marc Roos" <M.Roos@...outsourcing.eu>
To:     netdev <netdev@...r.kernel.org>
Subject: FW: gretap tunnel redirecting 2 different networks on destination host

 
I see you are quite busy with discussing the patches etc. If this is the 
incorrect place to ask for a little help please let me know. I just got 
this from some one on stack overflow who got some answers here.




-----Original Message-----
Subject: gretap tunnel redirecting 2 different networks on destination 
host


How can I get the 10.11.12.x traffic received on tun1 at server B to 
eth2, and 172.16.1.x to eth1? 


I have a server A that sends 172.16.1.x and 10.11.12.x traffic via a 
gretab tunnel 192.168.1.x to server B.

            +-------------+                             +------------+
 172.16.1.x |      B      |                             |      A     |
     -------|eth1         |         192.168.1.x GRETAP  |            |
            |         tun1|-----------------------------|tun1        |
 10.11.12.x |             |                             |            |
     -------|eth2         |                             |            |
            +-------------+                             +------------+

When I put the tun1 interface of server B in a bridge with eth1 I am 
able to ping several 172.16.1.x ip's from server A. And communication on 

this network seems to be ok


- I cannot put eth2 on the same bridge. 
- I thought of creating a 2nd gretab tunnel and use each tunnel for a 
network, but I think there is probably a better solution.







Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ