01:32 <noahm> Which stable branches of the openwrt git repos (packages, in particilar) are considered actively maintained? I haven't been able to find this on openwrt.org.

02:05 <SlimeyX> 23.10 ?

02:05 <SlimeyX> 23.05.5 sorry

02:06 <noahm> none of the older ones?

02:08 <efahl> Nope, none of the older ones: https://openwrt.org/docs/guide-developer/security#support_status

02:09 <noahm> ah, perfect, that's what I was looking for. No idea why I couldn't find it.

02:10 <efahl> If you tried to find it with the dokuwiki search, you'd never see it :(

02:11 <noahm> that might have been it

02:12 <efahl> I only ever get a billion toh entries when I try to use the built-in search, so end up using brave with site:openwrt.org

02:45 <SlimeyX> heh

04:08 <owrt-images-builds> Build [#49](https://buildbot.openwrt.org/images/#/builders/158/builds/49) of `main_mediatek/filogic` failed: failed Images built and installed (failure) (timed out)

06:11 <owrt-images-builds> Build [#53](https://buildbot.openwrt.org/images/#/builders/37/builds/53) of `main_malta/le64` completed successfully.

10:44 <f00b4r0> in the case of a dhcp interface, I'd expect that setting this value while keeping the default route enabled would result in the default dhcp route being affected to the selected table

10:44 <f00b4r0> but instead the default route is affected *both* to the selected and 'main' tables

10:56 <f00b4r0> hmm correction, the default route is applied to all main and custom tables. Not sure this is intended

11:08 <f00b4r0> https://git.openwrt.org/?p=project/netifd.git;a=commitdiff;h=4452867c4b34cb0d9dc7fe9dc42ecc86af887176

11:08 <f00b4r0> I don't understand this. This makes ip4/6table setting rather pointless unless everything is manually setup

11:09 <f00b4r0> (from https://github.com/openwrt/openwrt/issues/8174)

11:21 <f00b4r0> adding extra rules and static routes seem to be ignored without so much as an error message (24.10). /me scratches head

11:25 <f00b4r0> ha PEBKAC. Forgot that you can't use names in options unless these names have been defined in /etc/iproute2/rt_tables

11:25 <f00b4r0> this could use a bit of error reporting though

11:40 <f00b4r0> and now I have a device that uses a default route that's not in the main table even though I have no rule allowing lookup to custom tables. I guess I need to RTFM more

16:23 <Slimey> howdy everyone

16:31 <f00b4r0> nbd: https://pastebin.com/xXpbtmjz is this the expected output of a successful mt76 restart? the ieee80211 printks seem to occur *after* the actual restart and there is no confirmation of success, is this good? thx

16:33 <nbd> yes, that looks good

16:34 <f00b4r0> cool, thanks

16:50 <Slimey> u-boot gurus here?

17:23 <robimarko> Wouldnt call myself guru, but I do dev for it and use it

17:50 <grift> anyone have any information or clues about this oops: https://termbin.com/7jnk

18:43 <totkeks> I recently made a PR for the issue workflow on GitHub. But it just created more questions in my head. Maybe someone here can help me answer them. With the self-hosted git being the source of truth, what is the purpose of the github org and repos? Opening up to a wider audience? Leveraging its UI/UX known to many devs? Or something else entirely?

18:48 <aparcar[m]> totkeks sounds mostly right, audience, visibility, PR and CI workflows

18:50 <totkeks> CI only for the PRs though, right? The actual builds happen with the git.openwrt and on the buildbots?

18:59 <KanjiMonster> totkeks: for some things like the packages feeds github is actually the source of truth, so it's a bit of a mix

19:02 <totkeks> ha :D ... eh. :-(. is that written down somewhere as in "openwrt processes" or something? or just shared, but unwritten, knowledge?