Netdev List
 help / color / mirror / Atom feed
From: "Marc Roos" <M.Roos@f1-outsourcing.eu>
To: netdev <netdev@vger.kernel.org>
Subject: FW: gretap tunnel redirecting 2 different networks on destination host
Date: Tue, 3 Apr 2018 06:33:43 +0200	[thread overview]
Message-ID: <15208.4267618649$1522749049@news.gmane.org> (raw)

 
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.

             reply	other threads:[~2018-04-03  9:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-03  4:33 Marc Roos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-04-03  4:33 FW: gretap tunnel redirecting 2 different networks on destination host Marc Roos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='15208.4267618649$1522749049@news.gmane.org' \
    --to=m.roos@f1-outsourcing.eu \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox