From: Jonathan Thibault <jonathan@navigue.com>
To: netdev@vger.kernel.org
Cc: Herbert Xu <herbert@gondor.apana.org.au>
Subject: Ethernet over GRE and vlans
Date: Sat, 29 Jan 2011 00:16:06 -0500 [thread overview]
Message-ID: <4D43A296.4040906@navigue.com> (raw)
In-Reply-To: <4D2F77A8.1010700@navigue.com>
As per one of my previous posts, imagine a setup like this:
Three linux hosts connected to their individual 802.1Q network via
eth0 interface linked by a L3 network through their eth1 interface.
(local network)
| (remote network 1)
| eth0.1 <--br1--> gre1.1 |
| eth0.3 <--br0--> gre1 -- (l3_to_host1) -- gre0 <--br0--> eth0-+
+-eth0
eth0.4 <--br3--> gre2 -- (l3-to_host2) -- gre0 <--br0--> eth0-+
eth0.2 <--br2--> gre2.2 |
(remote network 2)
Wanting only untagged packets from remote networks 1 and 2 requires
simple ebtables rules wich answers my original query. But I ran into
a strange issue where vlan1 and vlan2 tagged packets from their
respective remote networks do not appear on gre1.1 and gre2.2
interfaces at all.
I see the tagged packets on the gre1 and gre2 interfaces respectively
but cannot make their untagged equivalent (or anything else) show up
on gre2.2 and gre1.1 as they would on standard ethernet devices.
Is it wrong on my part to expect such behaviour from gretap devices
or is this simply not possible/implemented yet?
Please include me in replies, I am not currently subscribed to netdev.
Jonathan
P.S.: I CCed Mr. Xu as I believe he originally submitted gretap
patches.
next prev parent reply other threads:[~2011-01-29 5:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 22:07 Tagged/untagged and gretap bridging question Jonathan Thibault
2011-01-29 5:16 ` Jonathan Thibault [this message]
2011-02-21 5:38 ` Ethernet over GRE and vlans Herbert Xu
2011-02-21 15:01 ` Jonathan Thibault
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=4D43A296.4040906@navigue.com \
--to=jonathan@navigue.com \
--cc=herbert@gondor.apana.org.au \
--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 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.