03:51 <owrt-images-builds> Build [#64](https://buildbot.openwrt.org/images/#/builders/156/builds/64) of `main_layerscape/armv7` completed successfully.

03:54 <owrt-images-builds> Build [#65](https://buildbot.openwrt.org/images/#/builders/75/builds/65) of `main_mxs/generic` completed successfully.

04:56 <owrt-images-builds> Build [#63](https://buildbot.openwrt.org/images/#/builders/24/builds/63) of `main_mvebu/cortexa53` completed successfully.

05:15 <owrt-images-builds> Build [#64](https://buildbot.openwrt.org/images/#/builders/9/builds/64) of `main_loongarch64/generic` completed successfully.

05:43 <owrt-images-builds> Build [#65](https://buildbot.openwrt.org/images/#/builders/39/builds/65) of `main_realtek/rtl839x` failed: failed './scripts/feeds update' (failure)

06:55 <owrt-images-builds> Build [#64](https://buildbot.openwrt.org/images/#/builders/168/builds/64) of `main_bmips/bcm6368` failed: failed Tools built and installed (failure)

07:27 <owrt-images-builds> Build [#64](https://buildbot.openwrt.org/images/#/builders/25/builds/64) of `main_sunxi/cortexa8` completed successfully.

07:52 <indy> hi all, snapshot images are with apk or still with opkg?

08:12 <slh> apk

09:25 <indy> slh, thanks

09:25 <indy> will check

09:39 <russell--> aha, 3ec7f3a512a27 breaks my mesh-point association with november-era versions

09:59 <russell--> blocktrron: ^^^^

09:59 <russell--> "mac80211: set basic-rate for mesh interfaces"

11:00 <russell--> blocktrron: reverting 3ec7f3a512a27 on top of recent master lets a node's mesh point interface associate with an older node

11:01 <blocktrron> russell--: yeah, and this is known

11:01 <blocktrron> You can set the rates per vif

11:02 <russell--> set how, and to what rate to be compatible?

11:02 <blocktrron> I will not revert the commit, as the behavior prior to this commit depends on whether you use wpa_sipplicant or not

11:03 <blocktrron> I think it was the basic_rate option

11:04 <russell--> yeah, but what value?

11:04 <blocktrron> Which rates depend on to the band. For 2.4 it was 1 Mbit if I remember correctly

11:06 <russell--> is there a public discussion of how to make this work somewhere i can read?

14:26 <Piraty> hmm ... apu4d4 or firebox m300 for my new router ... i guess stintel has an opinion ;)

14:26 <Piraty> stintel do you have images of the opened m300 device?

15:20 <takino> hello! can someone point me in the right direciton on how to compile the mt76 (mt7915e) module with debug/extra logging enabled? thank you :D

15:50 <Slimey> https://forum.netgate.com/assets/uploads/files/1583764208695-2020-03-09_15-26.png

15:50 <Slimey> Piraty

15:55 <Piraty> thank you . so there is some head room to shorten the chassis

19:20 <reiffert> Hey guys - I like to sponsor a https://mikrotik.com/product/hex_2024 Mikrotik Hex Refresh https://cdn.mikrotik.com/web-assets/product_files/E50UG_241016.png to a developer to make it support OpenWRT. Please advise. Thanks.

19:25 <reiffert> A friend is willing to donate money to the project as long as he gets a donation receipt that gets accepted by the German Tax Office. Would anyone happen to know whether the "Software Freedom Conservancy

19:25 <reiffert> " can issue such a receipt?

22:19 <aparcar[m]> efahl: could you make owut more... quiet by default? I think it's very niche interest to see for every update which unrelated packages failed to build on an upstream server. Maybe just a trivial "progress" animation would be enough by default with some status info but not flooding the screen with details? I think it's great for debugging but a regular user is likely overwhelmed...

22:59 <slh> Piraty: apu4d4 and the AMD jaguar CPUs are getting tired, if you are looking for x86_64 devices there are much, much better options these days (alderlake-n n100/ n97), the jaguar cores are really at their limits dealing with 1 GBit/s (no opinion on qoriq, as I never played with that)

23:07 <efahl> aparcar[m]: it has -q to quiet things down, and the verbosity is a setting in its config (default is 2, set it to 1 for quieter)

23:09 <efahl> I actually asked about making verbosity=1 the default and people seemed to like the noise

23:10 <efahl> I'll ask again, bigger audience now so might get better feedback

23:11 <aparcar[m]> i guess i'm a fan of simple

23:13 <aparcar[m]> looking at the level 1 output it's very quiet 🙂 I'll think of something, my point is to see progress and status but not all the details

23:14 <efahl> when you do a build, you still get the monitor output at both verbosity levels, so that doesn't change until you do `-q -q`

23:16 <aparcar[m]> okay I'll play around with it

23:16 <aparcar[m]> maybe you can test this https://github.com/openwrt/openwrt/pull/17777#issuecomment-2628550814

23:21 <efahl> Thanks, I'll definitely try that out.

23:22 <Piraty> slh: i don't want to spend a fortune and am looking for a 1gbit/2.5gbit device with more than one eth on second hand market. i just realize you suggested sophos devices earlier. the only reasonable sohpos device i see in openwrt TOH is S135

23:29 <slh> sophos is always easily available, but usually not a bargain

23:30 <slh> and keep in mind that the first n100 devices from aliexpress start around 120 EUR in a sale, delivered and including 19% VAT, so that kind of defines an upper ceiling

23:31 <Piraty> i prefer to buy second hand , local'ish

23:31 <russell--> Piraty: i'm buying linksys e8450 refurbs from the bezoid for $35 each, advertises 2.5gbps ethernet

23:33 <slh> if you areinEurope, Zyxel T-56 from odido/ nl