MaxSoniX has quit [Remote host closed the connection]
MaxSoniX has joined #openwrt-devel
lmore377_ has joined #openwrt-devel
lmore377 has quit [Ping timeout: 480 seconds]
danieli has joined #openwrt-devel
damex has quit [Ping timeout: 480 seconds]
robimarko has joined #openwrt-devel
<xdarklight>
hauke: please ping me if you want to work on it - we (Martin Schiller and myself) got stuck at some point. I currently don't have the time to work on lantiq patches myself, but I can get you up to speed on where we got stuck (and what happened along the way)
<hauke[m]>
Thank you for the update. I will read up the current status in the evening and contact you later
<djfe_>
Does anyone know which of the WikiDevi forks are still in active use? wi-cat.ru , deviwiki.com or shoutwiki.com? I created an account on wi-cat.ru but can't verify my mail so I got no rights to create new entries. (Error because their smtp server refuses the password when trying to send me the mail. I send them a mail already but received no answer so far)
<djfe>
according to this https://boxmatrix.info/wiki/OpenWRT-Info deviwiki is a frozen backup actually. Can anyone confirm whether this is still the case? I might turn to shoutwiki then (TechinfoDepot)
zatwai has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
zatwai has joined #openwrt-devel
danitool has joined #openwrt-devel
astro1 has joined #openwrt-devel
<astro1>
I am trying to understand how ubus works. When I do 'ubus call luci-rpc getBoardJSON', where is the C function that gets called to return back the board details?
<hgl>
stintel: with kmod-crypto-sha512 installed, the issue is fixed. I'd be happy to send a PR, but I'm not sure if sha512 should be added to crypto-rng's deps or it should replace sha256. crypto-rng doesn't seem to be drbg specific. thoughts?
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
<hgl>
Ansuel: your nginx PR compiled successfully in my own CI too
<Ansuel>
but why it does fail there...
<Ansuel>
still didn't had time to check why
xback has quit [Ping timeout: 480 seconds]
tidalf_ has joined #openwrt-devel
cbeznea1 has joined #openwrt-devel
tidalf has quit [Ping timeout: 480 seconds]
cbeznea has quit [Ping timeout: 480 seconds]
kenny has quit [Quit: WeeChat 3.8]
tidalf has joined #openwrt-devel
tidalf_ has quit [Ping timeout: 480 seconds]
kenny has joined #openwrt-devel
<Ansuel>
it's incredible i'm reading a paper from 1997 where they are talking about memory limitation with make projects
<Ansuel>
with exceeding 10mb of ram
<Ansuel>
and here we are with ssdk make project having the same implementation...
<Ansuel>
just to quote a pice... in the same sentence... "Modern computer" "10MB of ram"
<schmars[m]>
what's the expectation around building *on* linux-arm64? i see that macos arm64 is "tested", so i assume it's worth a try?
Borromini has quit [Ping timeout: 480 seconds]
<robimarko>
schmars[m]: I used to compile on Ampere ARM64 cores and it just worked
<schmars[m]>
nice nice, thanks - i'll see if i can get an arm64 sdk and imagebuilder going
<Ansuel>
i mean as long as host tools compile everything else is rebuilt from scratch
<schmars[m]>
yeah i just have a habit of running into unrelated (but bad) issues, the last four days were wasted to a faulty microsd card adapter, so this time i thought i'd ask about known issues first, hehe
raenye has joined #openwrt-devel
Borromini has joined #openwrt-devel
<raenye>
Hello! Are there any ramips people here who would like to review my new device pull req?
<Borromini>
anyone know what happened to luci-app-wireguard? it completely vanished from the luci repo >_>
<Borromini>
in master, that is.
<PaulFertser>
Borromini: protocols/luci-proto-wireguard/Makefile:PKG_PROVIDES:=luci-app-wireguard in current LuCI feed repo
<Borromini>
PaulFertser: oh. I don't keep track of the feeds logs :-/
MaxSoniX has quit [Quit: Konversation terminated!]
Borromini has quit [Ping timeout: 480 seconds]
tidalf_ has joined #openwrt-devel
tidalf has quit [Ping timeout: 480 seconds]
cbeznea1 has quit [Quit: Leaving.]
<philipp64>
Anyone know how to figure out why OpenWrt, when booted as an x86 VM, only detects one of the two Ethernet devices configured? Is there an easy way to debug netifd discovery?
<schmars[m]>
philipp64: detecting the hardware device itself is the kernel's business, you should find that in dmesg. if the kernel detects two devices and creates eth0 and eth1 (or lan1 and lan2), there's nothing i know of in openwrt that'd outright delete the second device
<philipp64>
schmars[m]: it's not that it's deleted... I see it. but only the config for `lan` is being applied. the config for `wan` gets ignored.
<schmars[m]>
you could check if it at least appears in ubus list
<schmars[m]>
but i don't have much clue otherwise
<philipp64>
this is interesting:
<philipp64>
[ 6.279274] 8021q: adding VLAN 0 to HW filter on device eth0
<philipp64>
[ 6.281612] ixgbevf 0000:00:03.0: NIC Link is Up 10 Gbps
<philipp64>
[ 6.283046] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
<philipp64>
I don't see a similar message for eth1.
bluew has joined #openwrt-devel
Borromin1 has left #openwrt-devel [#openwrt-devel]
<stintel>
I believe these are triggered by link up event. so the most basic question: is the other interface plugged in?
<stintel>
or a wild guess: wan and wan6 both use device eth1, maybe the "config interface 'wan'" section is also disabled because "config interface 'wan6'" has option enabled 'false'
<stintel>
increase log level for netifd in /etc/init.d/network, reboot, see if that gives you new, useful info. if not ... I guess improve netifd debuggability and documentation
raenye has quit [Remote host closed the connection]