Am 2017-02-09 um 00:33 schrieb dan:

Will that work?

bat0 is untagged bat0 contains eth0

bat1 is for management bat1 contains eth0.10

I thought that bat0 could trunk VLANs if the MTU is 1528? (1500 + 24 batman-adv overhead + 4 VLAN)

So which wins? If bat0 has a VLAN10 traversing it, but eth0.10 is in bat0, then something breaks.

On Wed, Feb 1, 2017 at 10:57 AM, fboehm fboehm@aon.at wrote:

...

I didn't test the following. So I could be totally wrong :)

Airfiber allows to configure VLAN for the management traffic. That means you can activate VLAN100 on the Airfiber device and create interface eth1.100 at the Batman-router.

Kinda like you described in your 2nd sketch. The main difference is that now the Airfiber management traffic is VLAN tagged and the Batman mesh-traffic remains untagged.

Bridging eth1.100 with bat0 should make the Airfiber device available everywhere in your network. Which isn't necessarily desired.

Franz

Am 2017-02-01 um 15:17 schrieb dan:

...

I'm trying to figure out the best way to handle this:

(bat0-eth1) <===> PTP Radio1 ~~~~~~~ PTP Radio2 <===> (eth1-bat0) (eth1 is in bat0)

These radios only have 1 interface (ie, no management interface) so I have to handle their configuration by assigning an IP to the same interface I want to connect into batman-adv.

I considered: bat0-bridge-eth1 <===> PTP Radio1 ~~~~~~~ PTP Radio2 <===> eth1-bridge-bat0 but this means the link isn't in the mesh

I don't know if this would work: bat0-bridge-eth1 <===> PTP Radio1 ~~~~~~~ PTP Radio2 <===> eth1-bridge-bat0 (bat0-eth1.10)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~(bat0-eth1.10) because I don't know if the eth1.10 vlan will be touched by the bridge, or if it will work with bat0 this way.

The purpose here is to use higher end radios like a ubiquiti airfiber 5x to reduce hop-counts and increase capacity.

Any thoughts?

I guess in your example eth0.10 is still meant to be used for managing the PtP equipment (like Airfiber).

As Airfiber isn't a batman-capable device it wouldn't help to attach eth0.10 directly to batman. No matter if it's bat0 or bat1. Because the Airfiber isn't aware of Batman header and can't process such network traffic. Instead you want to configure eth0.10 is an entry/exit point for regular traffic that doesn't carry a batman-header. The batman documentation says you need to use a bridge between eth0.10 and bat0 (or bat1).

Kind regards, Franz

Am 2017-02-11 um 07:41 schrieb Linus Lüssing:

On Fri, Feb 10, 2017 at 09:50:32AM +0100, fboehm wrote:

...

Because the Airfiber isn't aware of Batman header and can't process such network traffic.

Hm, why is that? The Airfiber can surely forward ethernet frames, can't it?

Been using a pair of Ubiquiti NanoBridges with their stock firmware in WDS-bridging mode to forward batman-adv frames successfully in the past.

Regards, Linus

True. But I think my information has to be seen in context to the initial thread topic: "access radio management interface of Airfiber".

That means if you manage Airfiber via a separate management VLAN, then this management-VLAN-Interface is unaware of batman header.

The capability of Airfiber to forward/bridge Ethernet frames with an embedded Batman header remains unaffected of this.

I Hope this clarifies the misunderstanding.

Franz