From: Antonio Quartulli <a@unstable.cc>
To: Sven Eckelmann <sven@narfation.org>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] bat0 trunk vlans?
Date: Thu, 9 Feb 2017 15:44:17 +0800 [thread overview]
Message-ID: <20170209074417.GG11922@prodigo.lan> (raw)
In-Reply-To: <1505249.1X2o3mks0n@bentobox>
[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]
On Thu, Feb 09, 2017 at 08:33:13AM +0100, Sven Eckelmann wrote:
> On Mittwoch, 8. Februar 2017 16:40:38 CET dan wrote:
> > Assuming MTU is great enough (1528 right? 1500+24 batman-adv+4 VLAN),
> > can the bat0 interface act as trunk for VLANs?
> >
> > 2 Nodes:
> > bat0:
> > eth1
> >
> > bridge0:
> > eth0|bat0
> >
> >
> >
> > device connected to node1-eth0 tags vlan20, does that traverse the
> > bat0 mesh and come out node2-eth0 with tag in-tact? Does it traverse
> > node1-eth0 at all?
>
> Afaik, the VLANs not on configured on batX will be rejected since TT was made
> VLAN aware [1]. I think Simon and Antonio can clarify this.
I agree with Sven. The Translation Table (TT) component should complain by
printing the message that you can see in the link.
This happens because TT needs to know about all the VLANs in order to learn the
MAC addresses of the clients.
However, TT gets to know a new VLAN only when this is actually created (i.e. by
creating bat0.X).
The solution would be to create a VLAN on top of bat0 (i.e. bat0.20) and let the
tagging happen at the node.
Cheers,
--
Antonio Quartulli
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-02-09 7:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 23:40 [B.A.T.M.A.N.] bat0 trunk vlans? dan
2017-02-09 7:33 ` Sven Eckelmann
2017-02-09 7:44 ` Antonio Quartulli [this message]
2017-02-09 9:38 ` Simon Wunderlich
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=20170209074417.GG11922@prodigo.lan \
--to=a@unstable.cc \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=sven@narfation.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