From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: a@unstable.cc
Subject: Re: [B.A.T.M.A.N.] bat0 trunk vlans?
Date: Thu, 09 Feb 2017 08:33:13 +0100 [thread overview]
Message-ID: <1505249.1X2o3mks0n@bentobox> (raw)
In-Reply-To: <CAA_JP8VHB3amFyjwfTtJdc-2E1DgDU5q4NdmVJ6HGVL5g97cZg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 656 bytes --]
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.
Kind regard,
Sven
[1] https://git.open-mesh.org/batman-adv.git/blob/HEAD:/net/batman-adv/translation-table.c#l715
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-02-09 7:33 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 [this message]
2017-02-09 7:44 ` Antonio Quartulli
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=1505249.1X2o3mks0n@bentobox \
--to=sven@narfation.org \
--cc=a@unstable.cc \
--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