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!
Recent searches
Search options
#batman_adv
0 posts0 participants0 posts today
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.
Meine kleine #IPv6 #Multicast Demo mit @videolan und @gstreamer im #Freifunk / @ffhl im Kontext der chaotischen #5MinutenTermine beim @chaotikumev ist mittlerweile online:
https://media.ccc.de/v/2024-07-03-linus-lussing-uber-die-freifunk-freiraumdisko
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.
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.
The #gstreamer #RaptorQ implementation (in #Rust!) for Forward Error Correction (#FEC) is awesome! Played a bit with it yesterday. With less than double extra overhead it worked well for an #Opus audio stream at 25% packetloss rate!
Which will be very handy for streaming with the new #batman_adv #multicast packet type at #Freifunk.
It's always exciting to see your #Linux patches trickle up the various steps and hopefully pass the eyes of the various maintainers on the way, until they finally land in Linus' master branch. But for my current one, which adds a new #multicast packet type to #batman_adv, I'm particularly excited. The BATMAN maintainers have reviewed and ack'd them and have now submitted them for adoption to the Linux netdev mailing list.
And one more update to the #brmldproxy integration in #Gluon: Added a patch to #batman_adv that avoids flooding #MLD reports when using brmldproxy in our specific scenario. Now that we got the link layer pretty quiet of broadcast flooded #IPv6 #multicast packets it was too tempting to keep it that way :D. #scalability #mesh #MeshNetwork #Freifunk