From: Sven Eckelmann <sven@narfation.org>
To: Alessandro Bolletta <abolletta@netter.io>
Cc: b.a.t.m.a.n@lists.open-mesh.org, Antonio Quartulli <a@unstable.cc>
Subject: Re: Passing VID-aware ethernet frames on plain batX interfaces
Date: Fri, 11 Sep 2020 16:02:27 +0200 [thread overview]
Message-ID: <4337705.76P5Ur0oAU@sven-edge> (raw)
In-Reply-To: <CADJ1cUQZ2YqFSVj=SNhPcC_sOjy+AkrEr=dQ=8T_0HegFou=Hw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
On Friday, 11 September 2020 15:03:13 CEST Alessandro Bolletta wrote:
> I see. Ok for transmission purposes, but what if I have to receive a tagged
> frame?
It should not have been send to the other node when there is no TT entry for
this mac + VID from the receiver.
> Should I only rely to the 8021q interface (eg. bat0.1) or receive the whole
> traffic (untagged and tagged) from the plain bat0 interface?
Hm?
> If this is not feasible, is it possible to handle in someway this?
Hm?
> A linux
> bridge on the top of bat0 interface could make it possible?
No, the bridge must also enable the vlan for this bat0 interface.
See also
https://www.open-mesh.org/projects/batman-adv/wiki/Faq#BATMAN-Advanced-VLAN-questions
Maybe Antonio wants to add more things to this discussion.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-09-11 14:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 10:48 Passing VID-aware ethernet frames on plain batX interfaces Alessandro Bolletta
2020-09-11 12:01 ` Sven Eckelmann
2020-09-11 12:19 ` Alessandro Bolletta
2020-09-11 12:48 ` Sven Eckelmann
2020-09-11 12:50 ` Sven Eckelmann
2020-09-11 13:25 ` dan
2020-09-11 14:12 ` Sven Eckelmann
2020-09-11 13:46 ` Alessandro Bolletta
[not found] ` <CADJ1cUQZ2YqFSVj=SNhPcC_sOjy+AkrEr=dQ=8T_0HegFou=Hw@mail.gmail.com>
2020-09-11 14:02 ` Sven Eckelmann [this message]
2020-09-11 14:42 ` Alessandro Bolletta
2020-09-11 14:44 ` Sven Eckelmann
2020-09-11 15:03 ` Simon Wunderlich
2020-09-14 6:35 ` Antonio Quartulli
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=4337705.76P5Ur0oAU@sven-edge \
--to=sven@narfation.org \
--cc=a@unstable.cc \
--cc=abolletta@netter.io \
--cc=b.a.t.m.a.n@lists.open-mesh.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