techhub.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A hub primarily for passionate technologists, but everyone is welcome

Administered by:

Server stats:

4.7K
active users

#rtl83xx

0 posts0 participants0 posts today
Replied in thread

@txt_file replaced the switches at the #Nobreakspace with a second hand 52 ports switch and a 24 ports PoE switch - both with a #Realtek / #rtl83xx chip and OpenWrt support, 50€ each on kleinanzeigen.de. But yeah, 10 and even 40 Gbit/s ports and 750W for PoE on this Mikrotik one sound nice :D.

Nice talk at the @battlemesh about #Realtek #switches running #OpenWrt. To get people even more excited about it this is how an OpenWrt #LuCI can look like with 52 ports :D. This D-Link DGS-1210-52 F1 was obtained for just 50€ on a German second hand online market place (kleinanzeigen.de) and is now running in the #Nobreakspace. Always make sure to pick the correct revision though, there are switches with very similar names but which don't use a Realtek chip.
#rtl83xx #rtl93xx

Use #BSD for good networking, nuff said... Use #OPNsense for a firewall/router, nuff said...

Me trying to use #multicast snooping with this in our hackspace: After several hours of debugging, realizing it's not bc. of the #OpenWrt powered, #rtl83xx based switch I've added, nor the new patches I've made and added to it. But because of this two years old, ignored #OPNsense (or #FreeBSD?) bug with #MLD: github.com/opnsense/core/issue
😒 😤

Important notices Before you add a new report, we ask you kindly to acknowledge the following: I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING....
GitHubIPv6 MLD listener report going to wrong interface · Issue #6247 · opnsense/coreBy martijncoenen

So, an #rtl83xx based switch, a ZyXEL GS1900-24HP v1, running #OpenWrt was now added to the rack of our hackspace. Some initial weirdness and confusion: PoE would not be enabled by default on boot. "/etc/init.d/poe restart" would until rebooted. Or manually populating /etc/config/poe with each PoE port seems to make it reboot safe...
Also PoE LEDs are not working yet.
The thing is, many crucial things in our space rely on PoE, like #VoIP phones, WiFi APs and the internet modem...

Also getting my #rtl83xx switch #Linux kernel code changes more and more into a style shape that I start to like, that looks more upstreamable to me.
Sometimes I see can see that some code looks ugly, but might have some difficulties to come up with a solution that is more "pretty"/readable. I have some judgement for aesthetics, I think, but I'm sometimes lacking a bit of creativity for aesthetics in general. Aesthetics has such a huge search space, too many possibilities :D. #OpenWrt

Replied in thread

@jpl @ffhl @batadv @Freifunk bin gerade noch dabei, den #rtl83xx basierten Switch, den @bdobe empfohlen hatte, ein bisschen was am IGMP/MLD snooping im Linux kernel zu fixen und habe unseren #Nobreakspace wieder ans #dn42 angeschlossen, will danach dann auch das layer 3 #multicast routing noch zwischen @ffhl und unseren hackspace einrichten. Danach wäre der Plan, das über #dn42 und das #ICVPN zu machen, genau. Wer aber direkt schon layer 3 multicast peeren möchte, gerne bescheid sagen :-).

Had found an issue with the #DSA #rtl83xx #IGMP / #MLD snooping code in #OpenWrt, it would always flood snoopable IP #multicast payload with no MDB entry, instead of dropping. Finally got some clue how this chip gets configured, it's a bit confusing with all these tables and how they point to each other :D. And these magic shifting numbers, instead abstracting them... Also found one bug in one shift value, I think.
And could get things to drop! Now need to drop more selectively.

Continued thread

on the other hand, unfortunately, it seems that #DSA in #Linux (and by that this downstream #rtl83xx driver) so far seems to repeat the mistakes we did in the Linux #bridge and fixed during the last decade... it's not following #RFC4541, DSA does not seem to have an option to set multicast router ports yet... which overall breaks #IGMP / #MLD snooping and by that #multicast in many scenarios... will be interesting if that is fixable or a limitation of #rtl83xx based #switch chips.