13:53 <f00b4r0> nbd: if you have a chance to take a look at this: https://github.com/f00b4r0/uspot/blob/c89ebd4a28ab9f5f1a462f4c7df2c6d7a861c7b4/files/usr/share/uspot/uspotbpf.uc#L20, I can't get ucode-mod-bpf to load my ebpf module natively, I've had to do this silly workaround and I really can't figure out what I'm doing wrong. Thanks

17:31 <Edu4rdSHL> Hi, quick question. OpenWrt push several licenses on https://github.com/openwrt/openwrt/tree/main/LICENSES, however, in the COPYING: OpenWrt is provided under: SPDX-License-Identifier: GPL-2.0-only ... In addition, other licenses may also apply. Is this possible to use OpenWrt on a company at all, without having to publish every thing you are going to modify/add? Or is that

17:32 <Edu4rdSHL> simply not possible without breaking GPL

17:32 <Edu4rdSHL> Thanks in advance

17:49 <f00b4r0> Edu4rdSHL: not sure if that answers your question but the GPL requires that the source be distributed along the binaries. In other words, any *recipient* of the binaries you build from GPL sources is entitled access to the (modified) sources.

17:50 <Habbie> (and they are then allowed to put it online, to be clear)

17:50 <Edu4rdSHL> f00b4r0, yeah, it seems that all needed is to just put the sources somewhere so that they can download it

17:51 <f00b4r0> of course if said modifications are "internal use only", then the sources can remain "internal use" as well

17:51 <Habbie> Edu4rdSHL, that is a valid implementation

17:51 <f00b4r0> ^

17:51 <Habbie> but if you ship the binaries, they are not 'internal use'

17:51 <Edu4rdSHL> Habbie, thanks, I thought it was going to be more complex!

18:17 <f00b4r0> is it expected that the GH packages CI will fail to download files for a brand new packages that isn't found on the owrt archive yet? It doesn't seem to try the git fallback, if I read the logs correctly

22:08 <philipp64> Can someone please review (and hopefully merge) my PR's for libubox? ISC-DHCP has gone end of life, and I'm trying to come up with a frontend for Kea that understands legacy /etc/config/dhcp files, but Kea of course uses JSON configs and synthesizing them from UCI is non-trivial. Also Kea doesn't seem to have an active maintainer, so I'd like to take it over... but as I've said on the mailing list, my libubox changes have not

22:08 <philipp64> seen much progress in over a year. @jow reviewed them and I thought I addressed all of his comments, so they *should* be good to go unless I missed something.

22:11 <philipp64> @Ansuel @blogic @stintel @nbd @ynezz ^^^

22:12 <Ansuel> i will take a look tomorrow

22:12 <philipp64> **thank you**

22:15 <philipp64> thanks BKpepe for the quick turn-around on the ssh permissions PR.

22:25 <philipp64> in other news, since PC Engines is winding down, decided to go out and get a BPi-R4... there's a month lead time since it ships from China... don't know much about the MediaTek SoCs, so I'll ask here, the 4xGBE ports are they individual NICs, or connected to a switch internally?

22:26 <Habbie> that feels like something the DTS could answer

23:09 <philipp64> where is the magic about using env/kernel-config documented? I've not had to set up a new cloning in a really long time...

23:24 <dwfreed> philipp64: bpi-r4 uses a switch chip for the 1 GbE interfaces

23:26 <philipp64> okay, so if I want to separate them, I need to put them on different VLAN's internally?

23:27 <dwfreed> well, that depends; the switch chip is DSA, so if you want all 4 ports separate, just don't put them on 1 bridge

23:28 <dwfreed> (the SFPs are their own interfaces direct to the CPU)

23:29 <dwfreed> otherwise you can use separate bridges, or separate vlans on 1 bridge; tomato-tomahto

23:31 <dwfreed> there is no real difference in practice

23:49 <slh> just pointing out, Intel n100 or n97 based systems with four dedicated 2.5 GBit/s ports range from ~120-250 EUR on aliexpress, those would be almost a(n updated) 1:1 replacement for the apu2

23:53 <slh> filogic 880 would be obviously much more interesting if wireless is part of the story (but at least in form of the BPi-R4, that is a tad too much on the may- or may not work side of things, and buying case, PSU, pigtails, antennas, wireless cards individually also drives up the cost quite a bit, especially if you can't be sure that it all works together)