From: "Marc Roos" <M.Roos@f1-outsourcing.eu>
To: lartc@vger.kernel.org
Subject: gretap tunnel redirecting 2 different networks on destination host to nics
Date: Tue, 03 Apr 2018 14:02:04 +0000 [thread overview]
Message-ID: <"H000007100114aa2.1522764124.sx.f1-outsourcing.eu*"@MHS> (raw)
How can I get the 10.11.12.x traffic received on tun1 at host B to eth2,
and traffic 172.16.1.x to eth1?
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.
When I add eth2 to the bridge, the whole network goes down. (Because of
a 'loop'?)
I thought of creating a 2nd gretab tunnel and use each tunnel for a
network, but I think there is probably a better solution. I also don’t
think iptables should be necessary, because I don’t want to do any
natting (However I have default policy DROP on INPUT, OUTPUT, FORWARD)
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. (Putting vms with a macvtap on
tun1 on host A)
+-------------+ +------------+
172.16.1.x | B | | A |
-------|eth1 | 192.168.1.x GRETAP | |
| tun1|-----------------------------|tun1 |
10.11.12.x | | | |
-------|eth2 | | |
+-------------+ +------------+
next reply other threads:[~2018-04-03 14:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 14:02 Marc Roos [this message]
2018-04-04 17:58 ` gretap tunnel redirecting 2 different networks on destination host to nics Grant Taylor
2018-04-05 2:00 ` Marc Roos
2018-04-05 16:05 ` Grant Taylor
2018-04-06 16:31 ` Marc Roos
2018-04-06 22:14 ` Grant Taylor
2018-04-07 3:26 ` Marc Roos
2018-04-07 5:10 ` Marc Roos
2018-04-07 9:24 ` Marc Roos
2018-04-21 1:42 ` Grant Taylor
2018-04-21 1:48 ` Grant Taylor
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='"H000007100114aa2.1522764124.sx.f1-outsourcing.eu*"@MHS' \
--to=m.roos@f1-outsourcing.eu \
--cc=lartc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).