fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

10K
active users

#batman_adv

0 posts0 participants0 posts today

I kind of hoped this would be a more demanding endeavour.

Connected two gluon nodes via fibre optic cables, set the respective interfaces to mesh with each other
and it just worked™.

The ERX SFP are about 70 bucks each, Ali Express did the rest.

Gigabit Freifunk Mesh for <160€ with two active B.A.T.M.A.N. speaking components.

Only 200 metres for now, tendency rising.

PS for non-techies:
This is a non-electrical connection between two computer networks, which allows for connections across buildings or towns without the risk of short circuits between them.

#gluon #freifunk #freifunkh #fibre #fiber @freifunkh #batman_adv

Another patchset for #batman_adv, this time some rework of the #VLAN support. This should mitigate the OGM overhead regression we accidentally introduced with compat version 15. I'm hoping to reduce the OGM overhead by about 30 to 50% again. This is also quite a step towards support of dynamically snooped TT VLAN detection from bridged-in clients. So far allowed/used VLANs had to manually be declared/configured on the batman-adv node itself.
patchwork.open-mesh.org/projec
#mesh #meshnetwork #Freifunk

patchwork.open-mesh.org[v3,0/3] add dynamic, bridged-in TT VID detection support - Patchwork

One of my first open source patches was for @pidgin, to fix some #IPv6 and #Bonjour / #mDNS issues in it. Bonjour chat and file transfer would allow to do so without needing a central server while we were on our decentral, layer 2 #batman_adv #meshnetwork at #Freifunk. Unfortunately we had to start filtering all #multicast in 2013 due to increased network sizes. Now, 11 years later with many new changes in #batman_adv and #Gluon we could reenable multicast at @ffhl. And Bonjour chat works again!

Wanted to continue working on my dynamic #VLAN support patch in #batman_adv. After quite some, late night debugging time noticed that the denial-of-service vector I found earlier was actually not in my patch, but is already present in upstream... :D.
While at it, also probably found an issue that could be abused as a small memory leak.
Not an immediate idea how to fix both though, as I'm overall not that familiar with the bridge-loop-avoidance code in batman-adv yet.

Replied in thread

@goetz @ffhl I needed a while to figure out what practical benefit we would have. One thing that came to my mind: Avoiding #ARP on supporting devices completely if I understand #ipv6mostly correctly. We do have a DHT for ARP in #batman_adv. And could reduce broadcasts a lot with it. But it's still not zero. #IPv6 is so much smarter for Neighbor Discovery as it uses #multicast properly with its solicited mcast addresses and not like broadcasts. And we have #MLD snooping in our #mesh.

So will be giving a presentation on the #batman_adv mesh routing protocol next week at the @nook. Had been wondering if I should organize a presenter to switch slides. Should I use my USB SNES controller in my bag? And now I'm kind of tempted to check if I could turn my #bluetooth VR controller from the HP Reverb G2 into a mouse device on #Linux :D. Especially as it generally works as a controller within #Monado and can be paired with #BlueZ. And its black design looks like a #Batman gadget :D.

Replied in thread

@paoloredaelli @jwildeboer some years ago mesh networking in phones was a no-go, because it would drain their battery too quickly. Lately I was very surprised to see a Gl.inet XE300 travel router last for 8 hours on its integrated 5000mAh battery with a #Freifunk firmware with #11s + #batman_adv (and no user traffic). So maybe portable 24/7 mesh networking devices in your pocket or bag is on the table again these days.
I'm wondering what #OLPC's experience with 11s and battery life was.

Continued thread

@ffhl so measurements were finally performed, collected, analyzed and visualized: The optimistic top third in the poll was right:

Overall #ARP #broadcast overhead was reduced by 89.86%. The main savings came as expected/hoped from the gateways, their ARP #broadcasts in the mesh were even reduced by 96.21%:

open-mesh.org/projects/batman-

Let's hope that this will finally get merged upstream soon.

Replied in thread

@kernellogger that "some features take longer than that" sounds very familiar... took me... ehm... 13 years, to get group aware #multicast #mesh routing into #batman_adv in the Linux kernel (including all these fixes for the multicast snooping in the Linux bridge which batman-adv taps into, plus a hack/workaround for an MLD bug in the Android firewall, which took Android 3 or 4 years or so to present a proper fix for...). But finally we have all this running at least at #Freifunk in Lübeck @ffhl

Replied in thread

@geerlingguy very cool, looking forward to your experiences with it, I'm very curious about #Meshtastic, too! I'm coming more from the 802.11 2.4/5ghz mesh side, have been developing on the #batman_adv mesh routing protocol for about 15 years for #Freifunk wireless community networks now, built on top of the #PicoPeeringAgreement. But on these bands it was always annoying that you'd need a line-of-sight to get far. #LoRa has the range, but not throughput. Would be great to combine both somehow.

Continued thread

@ffhl also note, that one of the two parts for the proposed solution on that wiki page back then, snooping #DHCP, was added upstream to #batman_adv and is applied at @ffhl. However the noflood mark is not. Downsides of the latter would be that it (potentially) would break IPv4 for hosts that don't use DHCP. And requires manual addition of ebtables rules. The hope is that the DAT DHT split patchset + timeout increase would work universally, without needing to configure/tweak anything as a user.

Continued thread

@freifunkradio @ffhl der #batman_adv translation table nach war ich wohl wieder der einzige Zuhörende (Knoten) über #Multicast. Aber an sich ist #Unicast ja auch nur eine Untermenge von Multicast :D </halbironisch>. Und dank der Optimierungen in batman-adv halt auch ohne andere z.B. per #Broadcast zu belästigen, wie es früher war. Aber genau deswegen denke ich, dass Multicast Routing zwischen Communities dann wichtig wäre um die Vorteile von Multicast voll auszuspielen. #CriticalMass