From: Sven Eckelmann <sven@narfation.org>
To: Alessandro Bolletta <abolletta@netter.io>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: Passing VID-aware ethernet frames on plain batX interfaces
Date: Fri, 11 Sep 2020 14:50:51 +0200 [thread overview]
Message-ID: <2590739.vkdJLyYtQh@ripper> (raw)
In-Reply-To: <38142483.hY40ij8To5@ripper>
[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]
On Friday, 11 September 2020 14:48:19 CEST Sven Eckelmann wrote:
> On Friday, 11 September 2020 14:19:59 CEST Alessandro Bolletta wrote:
> > So you mean that it is not feasible to create a (single) linux network
> > interface that let me send traffic on the batman-adv network in an
> > untagged or tagged way, though the same interface I mean?
>
> batman-adv is depending on the Linux code telling it what VLAN it should
> handle (through ndo_vlan_rx_add_vid and ndo_vlan_rx_kill_vid). So something
> like the 8021q driver or the bridge code for vlans. Only when this was done,
> it will also handle the addresses in TT. So no, bat0 is not enough to
> transport something like an ethernet frame tagged as vlan1. You also need
> bat0.1 (assuming this is the vlan interface for VID 1). But it is then not
> really relevant for it whether the data was send through bat0.1 or was somehow
> else tagged and then put into bat0.
Btw. why are you now using VLANs on top of bat0 - weren't you trying before to
have multiple mesh clouds by using VLAN (or VLAN-like) technologies below
bat0?
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 12:50 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 [this message]
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
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=2590739.vkdJLyYtQh@ripper \
--to=sven@narfation.org \
--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