blcok has joined #openwrt-devel
blcok has quit [Ping timeout: 480 seconds]
minimal has quit [Quit: Leaving]
ssterlingg has quit [Remote host closed the connection]
ssterling has joined #openwrt-devel
SlimeyX has quit [Read error: Connection reset by peer]
SlimeyX has joined #openwrt-devel
goliath has quit [Quit: SIGSEGV]
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #openwrt-devel
<owrt-images-builds> Build [#27](https://buildbot.openwrt.org/images/#/builders/120/builds/27) of `openwrt-24.10_ath79/mikrotik` completed successfully.
<blogic> hauke: yeah I was planning on doing so today
valku has quit [Quit: valku]
sorinello has joined #openwrt-devel
<owrt-images-builds> Build [#27](https://buildbot.openwrt.org/images/#/builders/31/builds/27) of `openwrt-24.10_bcm4908/generic` completed successfully.
blcok has joined #openwrt-devel
blcok has quit [Read error: Connection reset by peer]
blcok has joined #openwrt-devel
ScrewDriver1337 has quit [Ping timeout: 480 seconds]
<ynezz> error: automatic de-ANSI-fication (was reading it as de-NACI-fication...)
killgufo has quit [Read error: Connection reset by peer]
<ynezz> s/CI/ZI/ :p
killgufo has joined #openwrt-devel
blcok has quit [Ping timeout: 480 seconds]
<blogic> where did you see that error ?
<ynezz> X-Modem in 2024, BBS vibes from 90's
blcok has joined #openwrt-devel
<owrt-images-builds> Build [#28](https://buildbot.openwrt.org/images/#/builders/242/builds/28) of `openwrt-24.10_malta/le64` completed successfully.
blcok has quit [Ping timeout: 480 seconds]
blcok has joined #openwrt-devel
<dhewg> blogic: fresh build for my one from ~5min ago fails to bring up wifi at all, same config as yesterday, haven't investigated at all, but that null mac line catches the eye? https://paste.debian.net/plainh/e3313da7
<dhewg> ynezz: hey, I just used rz/sz yesterday :P I consider it essential on all my routers/sbcs. There was no network set up at all, and if you have a serial connection anyway that's the most easy way to transfer stuff
<ynezz> yeah, many bootloaders are common use case as well
<ynezz> just reading through the code from the '90s is like museum experience :P
<dhewg> and combined with picocom it's a breeze, it's just C-r or C-s
<ynezz> yep, using the same combination right now for EFR32MG flashing
<ynezz> (EFR32MG is that Silabs MCU being widely used for Thread/Matter, home automation over Zigbee)
<dhewg> and thanks for that PR, you may have noticed my comment of the prior hack, I just can't touch autohell stuff anymore for sanity/nerdrage reasons :D
<ynezz> yep, its hell, I first tried to fix it cleanly, like using patches from Debian/Gentoo, but it was still failing to build, thus I give up and simply patched it out, should be good for next 20 years or so :P
<dhewg> hm, I don't think I have any EFR32MG devices, just some cheap zigbee and esp/wifi ones
blcok has quit [Ping timeout: 480 seconds]
maciekb7218 has quit [Quit: bye]
maciekb72183 has joined #openwrt-devel
<dhewg> and some esp ones are very nice in a hackable sense, see my own HA/esphome glue https://github.com/dhewg/esphome-miot
<ynezz> yes, I like espressif stuff
<ynezz> EFR32MG is not expensive, its actually the radio used in HomeAssistant's Yellow
<ynezz> or their USB stick called SkyConnect/ZBT-1
<ynezz> there are numerous many other alternatives of course as well
<ynezz> just the tooling is a bit heavy now, python everywhere
<dhewg> yeah, I have some esp32-c6 for wifi and nrf52840 for zigbee/thread, but I lack the time to play with it
blcok has joined #openwrt-devel
<blogic> dhewg: this is with ucode scripts ?
<ynezz> dhewg: actually there plenty of microBUS Zigbee modules https://www.mikroe.com/click/wireless-connectivity?type*=zigbee,zigbee
<ynezz> so quite tempted to go this route for HA
<ynezz> + One of course
<blogic> I use this one for zigbee
<blogic> and then zigbee2mqtt
<blogic> works really well if you ignore the fact that z2m is written in node.js and the folder is around 200MB
<ynezz> :D
<ynezz> actually that -E variant is using EFR32MG21 as well
<blogic> I actually wrote a small piece of code to intercept/sniff the serial data and built a tiny protocol analyzer
<blogic> yeah I am using -P version with z-stack
<dhewg> blogic: yup, with ucode
<blogic> must be related to the 2 patches felix pushed yesterday
<blogic> let me check
<dhewg> and I have the same zigbee dongle, but I went with zha directly, no mqtt
<dhewg> does the mikrobus work on the one already? as in, plug in board and it's accessible?
robimarko has joined #openwrt-devel
<dhewg> nice
<nbd> dhewg: can you please show me the wireless config from your device where mesh fails?
<dhewg> nbd: https://paste.debian.net/plainh/974ca2d5 (openwrt one)
<nbd> that is with ucode wifi scripts, right?
<dhewg> yeah
<nbd> i will look into it
blcok has quit [Ping timeout: 480 seconds]
<nbd> thanks
<dhewg> comparing the generated supplicant conf with another node: max_oper_chwidth is 1, the other has 2, and beacon_int is in the global scope, the other node has it in the network{} scope
<robimarko> This breaks the mini variant
<robimarko> /external-toolchain/openwrt-toolchain-malta-be_gcc-13.3.0_musl.Linux-x86_64/toolchain-mips_24kc_gcc-13.3.0_musl/bin/../lib/gcc/mips-openwrt-linux-musl/13.3.0/../../../../mips-openwrt-linux-musl/bin/ld.bfd: /__w/openwrt/openwrt/openwrt/tmp/cc8BABDn.ltrans4.ltrans.o: in function `uc_wpa_rkh_derive_key':
<robimarko> <artificial>:(.text+0x1e7c): undefined reference to `hmac_sha256_kdf'
<nbd> robimarko: i'll take care of it, thx
<owrt-images-builds> Build [#28](https://buildbot.openwrt.org/images/#/builders/238/builds/28) of `openwrt-24.10_malta/le` completed successfully.
<nbd> dhewg: fixed now
rua has quit [Quit: Leaving.]
<dhewg> nbd: confirmed, thanks!
<dhewg> sz without network again, I vote for including rz/sz everywhere :)
<nbd> robimarko: fixed
blcok has joined #openwrt-devel
ScrewDriver1337 has joined #openwrt-devel
blcok has quit [Ping timeout: 480 seconds]
blcok has joined #openwrt-devel
<blogic> we should consider closing PRs older than 6 months or something like that with a nice message
<owrt-images-builds> Build [#27](https://buildbot.openwrt.org/images/#/builders/36/builds/27) of `openwrt-24.10_mediatek/filogic` completed successfully.
blcok has quit [Remote host closed the connection]
robimarko_ has joined #openwrt-devel
blcok has joined #openwrt-devel
blcok has quit [Remote host closed the connection]
robimarko has quit [Ping timeout: 480 seconds]
<aparcar[m]> why don't we use this luci theme as default? seems to be quite modern https://github.com/jerrykuku/luci-theme-argon
<aparcar[m]> actually scrap that comment
rua has joined #openwrt-devel
<owrt-images-builds> Build [#33](https://buildbot.openwrt.org/images/#/builders/98/builds/33) of `main_mvebu/cortexa72` completed successfully.
<ynezz> aparcar[m]: ask 3 different users, you'll get 3 different answers :)
<owrt-images-builds> Build [#35](https://buildbot.openwrt.org/images/#/builders/4/builds/35) of `main_mpc85xx/p1010` failed: failed Images built and installed (failure) (timed out)
<ynezz> reading through that thread I kind of miss "Tom Psyborg" :P
goliath has joined #openwrt-devel
<schmars[m]> just make it a regular thing, when a new major release is done, close $everything
<schmars[m]> my experience in other projects has been that at some size of the PR queue, it starts to weigh on people
<schmars[m]> "nice message" is important though
rsalvaterra has quit []
rsalvaterra has joined #openwrt-devel
minimal has joined #openwrt-devel
rsalvaterra has quit [Ping timeout: 480 seconds]
rsalvaterra has joined #openwrt-devel
<owrt-images-builds> Build [#32](https://buildbot.openwrt.org/images/#/builders/162/builds/32) of `main_ipq806x/generic` failed: failed Images built and installed (failure) (timed out)
ScrewDriver1337 has quit [Ping timeout: 480 seconds]
<blogic> ynezz: lol
<blogic> does gh cli support yuibey
<blogic> *key
<blogic> ah, the cli does an oauth like bootstrap thing
<blogic> so we could build a script that out closes a PR after 6 months with no activity
<blogic> https://cli.github.com/manual/gh_pr_status allows looking up the timestamp of latestReviews
Sawzallz has quit [Read error: Connection reset by peer]
<mrkiko> ok uys, but seeing commits signed by "Die Peter Pan"... not nice
<mrkiko> s/uys/guys/
<mrkiko> s/guys/All/
<mrkiko> I do value a lot their work and I am really and sincerely thankful. I am talking only and xclusively about the sign-off here
Sawzall has joined #openwrt-devel
minimal has quit [Quit: Leaving]
valku has joined #openwrt-devel
<ynezz> blogic: we just need to define the message and timeout, there are already many solutions to that, like stale bot or such
<ynezz> blogic: for both PRs and issues
efahl is now known as Guest2978
efahl has joined #openwrt-devel
Guest2978 has quit [Ping timeout: 480 seconds]
ScrewDriver1337 has joined #openwrt-devel
<owrt-images-builds> Build [#16](https://buildbot.openwrt.org/images/#/builders/261/builds/16) of `main_qualcommax/ipq60xx` completed successfully.
cmonroe has quit [Quit: Textual IRC Client: www.textualapp.com]
<blogic> ynezz: yeah I found that aswell
mrnuke has quit [Ping timeout: 480 seconds]
cmonroe has joined #openwrt-devel
mrnuke has joined #openwrt-devel
<blogic> robimarko_: is there a reason why qualcommax does not have eap101 support yet ?
<Mangix> some of my commits got merged. much appreciated @blogic
<robimarko_> blogic: basically, I newer got around to finishing it
<robimarko_> I have had it in some branch for a while
<robimarko_> Probably should finish it up while on vacation over christmas
<blogic> robimarko_: ok, was suprised and thought there was a problem
<blogic> there is no urgency, was just wondering
<blogic> the cool thing is the unit has that TI cc25** MCU which allows an install of z-stack3.0
<hurricos_> blogic: Does my thinking RE: https://github.com/openwrt/openwrt/pull/16838 make sense to you; can I provide more background for the effort?
minimal has joined #openwrt-devel
<hurricos_> mrnuke: ping
robimarko_ is now known as robimarko
<stintel> if only the eap101 wouldn't shit itself all the time I would have been more motivated to finish my branch
<stintel> hurricos_: o/
<robimarko> Maybe one day QCA stop being d*cks and just publish the current FW
<robimarko> Especially since ipq807x uses essentially the same one and they published it ages ago
<stintel> I used the eap101 in production for a while before I moved my network from my apartment to my house
<robimarko> ipq807x was crap as well before the 2.9 FW
<robimarko> I tried 2.12 FW that DD-WRT guys took from QSDK and it works much better
<stintel> https://git.openwrt.org/?p=openwrt/staging/stintel.git;a=commit;h=ccfd85a53dcd598a296ab8e5c9e44a641b5382a1
<stintel> https://git.openwrt.org/?p=openwrt/staging/stintel.git;a=commitdiff;h=ccfd85a53dcd598a296ab8e5c9e44a641b5382a1 better
<robimarko> It was my TO-GO platform for testing and developing upstream with buildroot
<robimarko> I like PoE and RJ45 UART
<stintel> aye
<stintel> very much
<stintel> but yeah I plugged in my eap101 not so long ago to test something and I think within 10 minutes it shat itself
<robimarko> I wanted to get EAP102 as well, but work did not want to buy one and I aint getting more HW :)
<robimarko> Its the same old shit story with old FW and BDF-s
<robimarko> Newer FW-s are way better but they also mostly require "refreshing" the BDF to populate new fields with default values
<robimarko> As vendors will never update those
<stintel> I currently have 2x EAP615-Wall MT7905DAN/MT7975DN, 1x EAP683 MT7976AN/MT7976GN and 1x Cudy AP3000-Outdoor MT7981
<robimarko> I have been using Dynalink WRX-36 for a long time now (IPQ8072A) and its been quide solid
<robimarko> Will replace my AC stuff with random ipq807x gear soon as well as I have bunch of it lying around
robimarko has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
lucenera has quit [Read error: Connection reset by peer]
lucenera has joined #openwrt-devel
<hurricos_> stintel: hey!
nixuser has quit [Read error: Connection reset by peer]
nixuser has joined #openwrt-devel
<mrnuke> hurricos_: I would have responded to #42 if I had been given the time. I disagree with it :(
<hurricos_> mrnuke: reverted.
<hurricos_> I'm still very glad I filed and then reversed the commit. It puts on the record that blogic was unhappy and was uninterested in the context.
<mrnuke> hurricos_: everyone, including blogic, agrees that a uci-defaults script is a good solution. What I don't get is blogic's insistance that this be carried by the realtek-poe upstream instead of the creators of the JSON format.
<hurricos_> mrnuke: I think the sword to cut the Gordian Knot is probably to place the uci-defaults in openwrt/package.
<mrnuke> hurricos_: I agree with you on that
<mrnuke> feel free to tag 2df137e ("realtek-poe/openwrt: Generate config from board.json") if you think that having something rushed for 24.10 may work
<mrnuke> that way packages/ feed gets the uci-defaults for 24.10, and we figure out the final solution later
<hurricos_> I'm just gonna submit a PR to openwt/packages instead, and ask for the prior PR to be closed.
<mrnuke> hurricos_: thank you.
<hurricos_> I figured I'd just put a knife to the baby and see who came :^)
<mrnuke> blogic: if there are good arguments to having the uci-defualts script on realtek-poe upstream, I am open to change my view. To me, it seems it's just one preference over the other.
<owrt-images-builds> Build [#33](https://buildbot.openwrt.org/images/#/builders/29/builds/33) of `main_zynq/generic` completed successfully.
<hurricos_> PR prepared, https://github.com/openwrt/packages/pull/25551. I still have to build- and run-test.
<mrnuke> hurricos_: BTW, there's a commit in the repo to fix the github pipelines failing: d2d1e3d (".github/workflows: Appease the github gods and use "v4"")
<mrnuke> Do you want me to PR it?
<hurricos_> Oh, please do
<hurricos_> I've been wondering about that one.
<hurricos_> I spent far longer than I should have staring at the page that the build failure linked, about the v2 deprecation :^)
<hurricos_> Can we test CI without merging it? I think Github might allow it. PR and test. If the CI succeeds, merge.
<mrnuke> hurricos_: https://github.com/Hurricos/realtek-poe/pull/43 triggered a CI run. let's see if it passes
<hurricos_> thanks, looks good :^)
<hurricos_> The sad side is that CI builds won't have uci-defaults, but I don't really care, we can haggle with testers without much extra overhead.
<mrnuke> hurricos_: Maybe we should make the CI builds so that they don't override /etc/config/poe
<mrnuke> so if someone installs a CI build over a properly configured /etc/config/poe, the CI build doesn't rip out their knwon good config
<hurricos_> ack
<hurricos_> I'm reasonably sure configuration files are preserved?
<hurricos_> I don't actually konw this.
<hurricos_> I don't actually know this.
<owrt-images-builds> Build [#34](https://buildbot.openwrt.org/images/#/builders/24/builds/34) of `main_mvebu/cortexa53` completed successfully.
<schmars[m]> they are, but uci-defaults scripts will be recreated by a sysupgrade. in the script you can check for an existing config though
sorinello has quit [Ping timeout: 480 seconds]
<owrt-images-builds> Build [#35](https://buildbot.openwrt.org/images/#/builders/58/builds/35) of `main_apm821xx/sata` completed successfully.