* FW: gretap tunnel redirecting 2 different networks on destination host
@ 2018-04-03 4:33 Marc Roos
0 siblings, 0 replies; 2+ messages in thread
From: Marc Roos @ 2018-04-03 4:33 UTC (permalink / raw)
To: netdev
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* FW: gretap tunnel redirecting 2 different networks on destination host
@ 2018-04-03 4:33 Marc Roos
0 siblings, 0 replies; 2+ messages in thread
From: Marc Roos @ 2018-04-03 4:33 UTC (permalink / raw)
To: netdev
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-04-03 9:52 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-04-03 4:33 FW: gretap tunnel redirecting 2 different networks on destination host Marc Roos
-- strict thread matches above, loose matches on Subject: below --
2018-04-03 4:33 Marc Roos
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.