Timeline for engineer list by rozzin, page 90
rozzin
engineer
Thursday, 29-Nov-0001 19:00:00 EST
-
@rozzin we'll have to plan a #beer and #BBQ day some time soon - I could really go for some good #ribs. I don't think I can wait for the #ribfest in June!
-
@mmn, there seems to be no support in #OpenWrt for #RSTP.
-
@mmn, there are hooks in the kernel code for a userspace #RSTP implementation, but I'm having trouble figuring out what the canonical userspace RSTP code is or its maintenance status.
-
The #Linux kernel code supports only the slow (and #obsolete) version of #STP from 802.1d-1998, not #RSTP from 802.1d-2004.
-
@rozzin Is there a reason _not_ to enable STP everywhere? :)
-
Thanks for the camera, @cjbprime!
-
I've got an #802.11s !mesh where all of the meshpoint nodes are also hosting #4addr APs that bridge onto the mesh (and some 4addr client<->wired bridges); having some difficulty reasoning about where and why I actually need #STP in this setup to avoid routing-loops, how often I should expect the topology to get out of sorts, and how quickly I can expect the system to sort itself out.
-
@mmn, it looks like you and I are working on similar things....
-
Though... I see there is this possibly interesting packge: luci-app-meshwizard? @mmn @hfroese
-
@mmn @hfroese, IIRC the big issue w/ the #OpenWrt #luci !mesh UI is that there's nowhere to enter a mesh_id value, so you need to set that manually in /etc/config/wireless or via #uci #commandline.
-
@hfroese I've mainly just looked at#OpenWrt documentation. The luci web interface doesn't work by default for setting up mesh yet. Hopefully I can push some patches.
-
@bobjonkman, I think I'm finding that !mesh #networking w/ #802.11s is not nearly as hard as everyone makes it out to be: https://github.com/o11s/open80211s/wiki/HOWTO
-
I spent at least a week learning about BATMAN, barman-adv, OLSR, etc. before I realised that #802.11s !mesh was a thing.
-
@vinzv @windigo But they're using #BATMAN and I want to try out #802.11s (as with future configurability and implementations, it should be as simple as switching a "backend" option to change the mesh protocol used in the 802.11s network). All the meshes out there today tend to use lots of userspace tools - I just want to hand it off to the kernel and look away.
-
@mmn Then I'll have to learn to set everything up with #AuthSAE so I can have encrypted mesh.
-
I've been playing with customizing #OpenWrt. It boots with preconfigured mesh (#802.11s!), anyone can link up to it, and a customized "UmeshLAN [mac-addr]" network is now published for easier administration of individual nodes.