Misanthropos has quit [Read error: Connection reset by peer]
<PaulFertser>
rua: usually once you know what hardware is involved you look for a similar already supported board, study the commit that added support for it, do something similar for your device and build an initramfs image for trying it without flashing.
srslypascal is now known as Guest1486
srslypascal has joined #openwrt-devel
Misanthropos has joined #openwrt-devel
Guest1486 has quit [Ping timeout: 480 seconds]
robimarko has joined #openwrt-devel
Misanthropos has quit [Read error: Connection reset by peer]
borek has quit [Quit: borek]
borek has joined #openwrt-devel
borek has quit [Remote host closed the connection]
Piraty has quit [Remote host closed the connection]
Piraty has joined #openwrt-devel
schwicht has joined #openwrt-devel
dangole has joined #openwrt-devel
<corna>
Hi all. What is the policy for merges on 22.03, given that we're close to a release? Bugfixes only or also small improvements?
<pepes>
corna: Hi, submit your changes and create pull requests. You will see. :)
Gaspare has joined #openwrt-devel
<f00b4r0>
nbd: quick question: does unetd take full control of the wireguard configuration (I assume it does) or can it coexist with preexisting configs?
<nbd>
it takes full control (for the interface)
<f00b4r0>
ok
<nbd>
doesn't interfere with other wireguard interfaces created separately
<f00b4r0>
makes sense
<nbd>
i'm working on making it easy to include host entries for hosts not using unetd
<corna>
pepes: thanks, I'll wait for it to be merged on master and re-open it on 22.03
<f00b4r0>
neat. Last question: what's the minimum requirement for using it? (in other words, how old an openwrt release could I build unetd for?)
* f00b4r0
is ashamed to still have a 19.07 in the wild ;P
<nbd>
right now it only builds if ebpf support is available, but i guess it would be possible to add a config option to disable it
<nbd>
i think it also needs a recent libubox
<nbd>
and some netifd fixes that i made
<f00b4r0>
so I guess it means... master or bust? ;)
<nbd>
22.03 should also work
<nbd>
21.02 will likely require some backporting
<f00b4r0>
ok. I can probably help with that if it comes to that
<nbd>
is the wiki page that i made reasonably easy to understand?
<nbd>
or is it too complicated?
<f00b4r0>
it seems relatively clear. I need to start using it to get a hang for it I guess.
<f00b4r0>
one thing that is not completely clear is whether the VXLAN setup is required: AIUI it's not?
owrt-snap-builds has quit [Quit: buildmaster reconfigured: bot disconnecting]
owrt-snap-builds has joined #openwrt-devel
<nbd>
vxlan is completely optional
<nbd>
it's only needed if you want to do bridging
owrt-snap-builds has quit []
owrt-snap-builds has joined #openwrt-devel
<f00b4r0>
makes sense. I only do routing so I'll be fine.
<f00b4r0>
I'll start playing with a mockup setup (all my "production" devices are running at best 21.02; so can't test live yet)
<nbd>
one thing i also want to implement at some point is support for networks where none of the hosts has a public ip
<f00b4r0>
central repository?
<nbd>
i'm toying with the idea of using the bittorrent DHT implementation
<f00b4r0>
oh
<nbd>
for node discovery
<nbd>
and then STUN for NAT hole-poking
<f00b4r0>
smart :)
Larhzu has joined #openwrt-devel
<corna>
I see that /dev/mem is disabled on all the platforms: is it a deliberate choice, or is it possible to enable it on platforms where it makes sense (like x86, for flashrom support)?
<robimarko>
Its disabled by intention for security reasons
<robimarko>
Not something you want to have enabled unless really sure
<corna>
:(
<corna>
Thanks
<robimarko>
If you need it, its easily enableable through menuconfig
<corna>
I see, I just think it's not exactly user-friendly for owners of platforms like the PCEngines ones
<corna>
But I get the reason
Gaspare has quit [Quit: Gaspare]
<f00b4r0>
nbd: trying to build on linux, cryptic cmake error which I guess is related to missing deps: https://termbin.com/eu8p
<f00b4r0>
hmm same error with libnl-3-dev, libbpf-dev, libelf-dev and zlib1g-dev installed
<f00b4r0>
ah. libjson-c-dev
<f00b4r0>
nbd: mind if I amend the wiki just a bit to add build deps?
<jow>
hauke: going to push my last bump today
__lore__ is now known as _lore_
<nbd>
f00b4r0: feel free to update the wiki
<nbd>
thanks
<f00b4r0>
ok, will do
<f00b4r0>
rmilecki: I don't understand your comment
<rmilecki>
f00b4r0: which part? ;)
<f00b4r0>
all of it
<f00b4r0>
I tested the patch and it does exactly what's intended, namely using the node name as led name
<rmilecki>
it works, that's correct
<rmilecki>
but it doesn't follow rules
<f00b4r0>
the colors and functions cannot be used for the leds where I drop the label for the reason detailed in the comment above
<f00b4r0>
the node name doesn't follow rules?
<f00b4r0>
we're using this node naming *everywhere*
<rmilecki>
correct
<f00b4r0>
node naming style*
<rmilecki>
"If you check leds-gpio.yaml (...)"
<rmilecki>
sec for a link
<f00b4r0>
ok so you're going to fault this short patch because it breaks a rule we never respected to begin with? :P
<rmilecki>
Hunk #3 succeeded at 157 with fuzz 2 (offset 16 lines).
<rmilecki>
neverming, "patch" accepted it, it was "git am" that complained
<rmilecki>
"git am" is more picky
<f00b4r0>
i submitted this patch 2 weeks ago and afaict nothing touched this dts since then??
<f00b4r0>
or I'm getting senile ;P
<f00b4r0>
rmilecki: might I abuse your generosity by asking you to also push that to 22.03? ;)
<f00b4r0>
oh i see. It's the gmac muxing patch that offset the file. But this affects parts which are much further down, really odd that git am choked on that
<rmilecki>
f00b4r0: ack, sorry you wasted some time on it
<f00b4r0>
no big deal
<f00b4r0>
i guess we need a policy first :)
valku has joined #openwrt-devel
<f00b4r0>
nbd: first pass edit. I'll have to add the openwrt instructions later. I added the repo address which was missing, I used the GH one I hope that's ok.
<nbd>
the GH repo is going away
<nbd>
please point it to git.openwrt.org
<f00b4r0>
done
Gaspare has joined #openwrt-devel
<nbd>
thanks
goliath has quit [Quit: SIGSEGV]
tlj has joined #openwrt-devel
floof58 has quit [Ping timeout: 480 seconds]
schwicht has quit [Read error: Connection reset by peer]
floof58 has joined #openwrt-devel
DeadEnd has joined #openwrt-devel
<DeadEnd>
Quick question for the OpenWRT dev community.
<PaulFertser>
It's OpenWrt, not WRT ;)
<DeadEnd>
I have a PR for a new device that has been sitting for a bit. I don't want to be a bother to anyone as I know you are all volunteers - so is there someone that I should ask, or somewhere other than here I should go to ask for it to be reviewed?
<DeadEnd>
Yes, I typo'd... I'm use to shift+enter for new lines... haven't been on here before and didn't know that didn't work (so I could re-read before sending).
<DeadEnd>
It was supported in the past, but was dropped when ar71xx was moved to ath79 I believe.
<DeadEnd>
the PR is just to restore support - I mainly followed what was done for the D-Link DIR-825 B1 as they are very similar.
<PaulFertser>
I hope one of the maintainers sees it and approves the CI so that the PR is marked as buildable.
<DeadEnd>
mans0n was the user who helped me get it all fixed up (had some basic mistakes). As far as I can tell it should be ready for review - I have rebased and force pushed a few times trying to keep it up to date for when someone has time to review it.
<DeadEnd>
I don't want to pester anyone because obviously they all have lives and are donating their time to maintain and support this.
<PaulFertser>
Yeah, it certainly looks ready for review.
<PaulFertser>
Thanks you for contributing.
<mrnuke>
svanheule: That rtl switch port was such a ninja fix! :)
<nbd>
f00b4r0: btw. libnl and libbpf are not required for building on regular linux
<nbd>
because build.sh already builds libbpf and libnl-tiny
goliath has joined #openwrt-devel
ekathva has joined #openwrt-devel
ekathva has quit [Remote host closed the connection]
srslypascal has quit [Remote host closed the connection]
srslypascal has joined #openwrt-devel
Tapper has joined #openwrt-devel
Tapper has quit [Quit: Tapper]
<svanheule>
mrnuke: I'm too easily triggered by people saying "well, this is obviously impossible to fix" ;)
<mrnuke>
svanheule: Good to know what keeps you motivated :p
<svanheule>
mrnuke: that's why I'm still on the realtek target :^)
<mrnuke>
svanheule: Thank you for doing the fix! It would have taken me much longer to figure out what's going on (although the strlen did clue me to the port label)
<svanheule>
mrnuke: part of the switch port info was still being populated, so something wasn't properly ignoring those disabled nodes. DT subsystem has helpers for it, but doesn't do that automagically.
<svanheule>
been there before, as you can probably tell :P
<mrnuke>
The kernel is a mysterious place
<nick[m]1234>
Can't I add a PROVIDES:=examplepackage and than depend on PACKAGE_examplpackage? What is the correct way of doing such things?
Piraty has quit [Quit: No Ping reply in 180 seconds.]
Piraty has joined #openwrt-devel
<nbd>
f00b4r0: it is now possible to disable the unetd specific peer endpoint exchange protocol per host
<nbd>
(to improve behavior with non-unetd host entries)
<nbd>
and you can now also build it without vxlan/ebpf support
<tmn505>
did someone notice imagebuilder size for mvebu/cortexa53 going out of control? 21.02.3 = 164029.0 KB; 22.03.0-rc6 = 375568.1 KB; snapshot = 626051.3 KB! I see support for all ARM variants GCC supports in staging_dir, instead of only cortex-a53. When did that happen?
<tmn505>
ok, that budding thing seems to be toolchain from arm.com used to build TF-A. Damn that's wasteful.
dansan has joined #openwrt-devel
Borromini has joined #openwrt-devel
<barhom>
What would be the best way to keep track of data consumed per client?
<barhom>
Basically I want to show that client with mac-address X has gone through X bytes
cmonroe has quit [Ping timeout: 480 seconds]
cbeznea has quit [Quit: Leaving.]
<pkgadd>
nlbwmon
cmonroe has joined #openwrt-devel
MaxSoniX has quit [Quit: Konversation terminated!]
AtomiclyCursed has quit [Quit: ZNC 1.8.2 - https://znc.in]
AtomiclyCursed has joined #openwrt-devel
Borromini has quit [Quit: Lost terminal]
robimarko has quit [Quit: Leaving]
linusw_____ has quit []
<pepes>
nick[m]1234: I saw it somewhere, thus it should be possible, but still you can test it on your end. :-)
DeadEnd has quit [Remote host closed the connection]
<nick[m]1234>
pepes: I thought iptables would use that mechanism. However, it does not work for me. I wanted to add wpad-full to all that wpad packages providing a full installation
dangole has quit [Remote host closed the connection]
dangole has joined #openwrt-devel
cmonroe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<pepes>
I dont see a reason, why would you do that for wpad as then you would need to check if conflicts are correct.