Nick_Lowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<rsalvaterra>
mangix: Katyushas firing to the sound of an atrocious German song… WTF have I just watched…? o_O
zkrx has quit [Ping timeout: 246 seconds]
<mangix>
rsalvaterra: that was in response to people liking autotools
dwmw2_gone has quit [Ping timeout: 252 seconds]
dwmw2_gone has joined #openwrt-devel
dwmw2_gone has quit [Excess Flood]
dwmw2_gone has joined #openwrt-devel
zkrx has joined #openwrt-devel
kakaka has joined #openwrt-devel
Tapper has quit [Ping timeout: 268 seconds]
dwmw2_gone has quit [Ping timeout: 245 seconds]
dwmw2_gone has joined #openwrt-devel
user890104 has quit [Quit: user890104]
user890104 has joined #openwrt-devel
<Grommish>
Evening All
user890104 has quit [Client Quit]
<mangix>
kab-el: is the eMMC on the Omnia connected through the SoC's sdhci support? I ask since the SoC apparently supports higher speeds but not as configured currently.
kakaka has quit [Ping timeout: 240 seconds]
<Grommish>
mangix: What does PKG_BUILD_PARALLEL do?
<mangix>
Grommish: adds -j parameter to make. Only compatible with packages that use make.
<mangix>
So basically no packages using meson or CMake in the packages feed.
<Grommish>
Right, interesting. I can put that in, but to the Turris question, I answered that as well
<Grommish>
The Makefile was outdated, so I had to change some things, but I left the Header block intact
<mangix>
lol what was the answer?
<Grommish>
That is certainly was, but I left the header block intact. I wasn't going to start from scratch
<Grommish>
and I needed libhtp for Suricata6
user890104 has joined #openwrt-devel
<Grommish>
faux paux?
<Grommish>
It was either externalize it, or git clone libhtp every time I ran Build/Prepare :D which is how I was originally doing it
Guest54944 has quit [Quit: Leaving]
hbug_ has joined #openwrt-devel
hbug has quit [Ping timeout: 240 seconds]
<Pepe>
Grommish: It depends. You could write to the PR description that you used the Makefile from source, that you done these changes, etc would be one approach than saying "it was outdated", I did just three changes and I am the author (according to Git like it is done now). The other approach would be to put the original authors and use Co-authored-by and in your Signed-off-by add to the [] which changes
<Pepe>
you made.
<Pepe>
Just my point of view.
<Pepe>
Same applies for commit message.
<Grommish>
Pepe: I'd honestly rather not deal with it at all, but since it' not in the tree.. I'm not credit harvesting :) Feel free to comment on the PR on how you'd like to see it.. Or, submit it yourself? I don't care how it gets there
<Pepe>
Grommish: Why do you have such approach like I started smth and then give up?
<Grommish>
Pepe: But as you pointed out in the Suricata PR, I'd rather not git clone each time, but if it is an issue, I can go back to doing that
<Grommish>
Pepe: It's not give up :) It's just path of least hassle
dwmw2_gone has quit [Ping timeout: 245 seconds]
<Grommish>
Pepe: If you have a better, proper way, I invite you to correct the PR via comments. If you want to submit it yourself, please do. I just need it in the repo, or a work around on how to get it
<Pepe>
Grommish: For me it seems like you do. I told you what should be done and if I should repeat myself in that PR, fine. It seems you need it in upstream, so feel free to continue what you are doing. If you want to go back to the ugly way like doing git clone each time, then go.
<Grommish>
Pepe: You recommended a different way, I used it. How it gets into the OpenWrt repo I honestly don't care about, as long as it's there
<Pepe>
I am not going to reinvent wheel as it will be good to have it in upstream, but there should be some dependencies tighten to it or in other words, packages which are using that.
<Pepe>
I see that this is not going anywhere, sorry.
<Grommish>
Pepe: I'm not being argumentative, at least ot intentionally, but I'm not understanding what you are trying to convey
dwmw2_gone has joined #openwrt-devel
<Grommish>
Pepe: Instruct me on a better way, and I'll certainly go that route. My goal is least resistance for this since, let's face it, no one is going to actually end up using the package
dwmw2_gone has quit [Ping timeout: 245 seconds]
<Grommish>
Pepe: I only need LibHTP for Suricata, which also requires Rust, so the use-case for either is going to be damn near nothing. Usually, anything I need is already in the build tree, this was not. You questioned git cloning it, and were right. You pointed to the Makefie for 0.5.33, and you were right :) I removed the ICONV stuff because it wasn't playing nice, and Build/Compile because the -fno-stack-protector was questionable and the $(MAKE) call
<Grommish>
was just redoing Build/Compile/Default
<Grommish>
Pepe / mangix: If it's an issue for either of you, simply close it and I'll go back to doing it the way I was
<Grommish>
I'm not getting worked up about it though
<kab-el>
mangix: it is
dwmw2_gone has joined #openwrt-devel
<kab-el>
mangix: i am not sure about whether the MMC supports it, but I have never looked into this
kakaka has joined #openwrt-devel
<mangix>
kab-el: I have a Helios4 board (very similar SoC to the Turris Omnia) and am looking into getting some of my SD cards working (it has SD instead of eMMC). Apparently after kernel 4.19 something happened and high speed support broke. I'm trying to figure out what happened.
<Pepe>
Grommish: I know why LibHTP is needed, but I didn't said that I dont want to see that in upstream or did I? I responded to your faux paux message that it could be done better than finding in the comments, which changes you did and why. If you want to have it in OpenWrt, go ahead and finish that. I am not doing it, because as you said, it requires Rust and Rust is needed for Suricata. Both things you
<Pepe>
have running or I suppose so accordings to PR. I havent ever tried it. Because I would need to compile it, test it and to see if it works and then I could send libhtp there, but all of this, in the end cost developer time if you said that it saves hassle, which it does not, though.
<Pepe>
Grommish: Also, I have running libhtp on OpenWrt 19.07 and I dont have it running for OpenWrt 21.02 either OpenWrt master, and thats why I am not sending it to upstream as it would be completely untested, which I am not doing.
tobleminer-tSYS has quit [Quit: AS4242423214]
tobleminer-tSYS has joined #openwrt-devel
<Grommish>
Pepe: If you wanted to, I'd be more than happy to test it for you. Like I stated, I'm just looking to use it, I'm not picky about how it gets there
<guidosarducci>
nbd: Hi Felix, I'm updating a prior NLS fix you made in binutils (which you also maintain) and have some questions in https://github.com/openwrt/openwrt/pull/4038. Please take a look. Thanks!
victhor has quit [Ping timeout: 246 seconds]
<guidosarducci>
Grommish: BTW, curious on what platform you run suricata? Wondering also if you enable eBPF?
<Grommish>
guidosarducci: I've tested on mipsel and mips64, someone on the forums tested under aarch64. There is an option for ebpf but I can't use test it because of the arch. Like Hyperscan. I know suricata can support it, but I can't test it
<Grommish>
guidosarducci: I've not set deps for arches yet for those options though and I've not put hyperscan in at all yet
<guidosarducci>
Grommish: I was more curious of the HW platforms used that are actually capable of using suricata without struggle. What is this arch restriction for eBPF?
<Grommish>
guidosarducci: Using debian as a guide: EBPF_ARCHS = amd64 arm64 armel armhf i386 ppc64el s390x ppc64 sparc64 x32. I know Hyperscan is Intel x86_64/AMD64 specific
<Grommish>
guidosarducci: I've not production tested suricata yet outside of getting it booted and loaded, I need to make sure the rules get loaded and then test throughput
<Grommish>
guidosarducci: WIth snort3 on the Shield, I get about 80% max when it's running, I expect about the same for suricata
<guidosarducci>
Grommish: thanks for the explanation. Interesting about the restriction, I wonder if that's artificial or based on something. Thought maybe BPF JIT support, since mips32 lacks this, but mips64 works so should be there. Let me know when you using this in anger ..err.. production.
<Grommish>
I've not tried building on a target platform that should support it yet, but I can give you the error I get for mipsel easy enough if you want to give me a few minutes
danitool has quit [Ping timeout: 265 seconds]
<Grommish>
guidosarducci: General error, although more details are avail.. checking checking if mipsel-openwrt-linux-musl-gcc supports -march=native... no
<guidosarducci>
Grommish: strange, could it be it doesn't support cross builds for mips? if you gist the details somewhere I'll try to take a look.
<Grommish>
It just seems -march=native isn't valid
<Grommish>
For cross-compile, I dunno how it would though
<Grommish>
guidosarducci: I saw your BTF PR, and was wondering if it was related to the eBPF issues I was seeing, but then I saw the arch restrictions
<OutBackDingo>
guidosarducci: what do you plan to achieve with ebpf on low speed links like wireless / dsl / FTTH
Acinonyx_ has joined #openwrt-devel
Acinonyx has quit [Ping timeout: 246 seconds]
<mangix>
guidosarducci: I don't actually use bpftools. No idea what the actual issue is.
<guidosarducci>
Grommish: right, kernel debug BTF is not arch specific and shouldn't affect something not looking for it.
<Grommish>
guidosarducci: I am just going to build out an x86_64 target and see what happens
<guidosarducci>
mangix: was referring to the compile issue, shouldn't matter what exec we're building, right?
<guidosarducci>
mangix: if you're unsure of details may be better to upstream the change and get feedback.
<guidosarducci>
OutBackDingo: flexible, programmable packet processing is one aspect, tracing/monitoring/debug is the other motivation for BPF. The link speed being high or low is orthogonal...
<guidosarducci>
OutBackDingo: a BPF jited program can run at native speed, but if your CPU is underpowered you have the same issues as always.
<guidosarducci>
OutBackDingo: but compared to traditional tc filters or netfilter rules you can have more capabilities and efficiency with BPF than before.
<guidosarducci>
Grommish: Hmm, I think you need to figure out where that "native" is coming from in "-march=native".
dwmw2_gone has quit [Ping timeout: 245 seconds]
<OutBackDingo>
guidosarducci: yes im quite familar with BPF...
Olipro has quit [Quit: Don't flap your BGP at me sonny]
Olipro has joined #openwrt-devel
Olipro has joined #openwrt-devel
Olipro has quit [Changing host]
dwmw2_gone has joined #openwrt-devel
enyc has quit [Remote host closed the connection]
enyc has joined #openwrt-devel
<Grommish>
guidosarducci: Yeah, it's coming from the conftest it looks like, but I'll get to test a few things, create a rust toolchain for x86_64 a target and see what breaks :)
kakaka has quit [Ping timeout: 240 seconds]
<guidosarducci>
OutBackDingo: oh, so then why the troll?
biangbiangmian has joined #openwrt-devel
<OutBackDingo>
guidosarducci: not so much a troll just more seeking insight from a low end embedded platform perspective.
<OutBackDingo>
as most of these "wireless access points have minimium resources
<biangbiangmian>
hey all, has anyone published anything about the release of 21.02?
<biangbiangmian>
but i did not see any forum announcement
<aparcar[m]>
mangix: ping
<aparcar[m]>
since you merged this ninja patch, do you see any change in building speed/
<mangix>
aparcar[m]: I provided some numbers in that PR..” Anyway, I build with ccache so any numbers I post would not be representative.
<aparcar[m]>
I see
<aparcar[m]>
are buildbots running without ccache?
<mangix>
They are
<mangix>
ccache is not enabled by default anywhere
valku has joined #openwrt-devel
valku has quit [Client Quit]
rmilecki has joined #openwrt-devel
biangbiangmian has quit [Read error: Connection reset by peer]
biangbiangmian has joined #openwrt-devel
kakaka has joined #openwrt-devel
nslu2-log__ has quit [Quit: Disconnecting from stoned server.]
nslu2-log has quit [Quit: Disconnecting from stoned server.]
nslu2-log has joined #openwrt-devel
nslu2-log_ has joined #openwrt-devel
<Thermi>
ynezz: I am working on fixing procd right now and I can't believe that code is actually in use. There are balatant problems like at least one use after free, problems with signedness, and use of stack variables in a global variable. The CI tells me about them. How did that not get fixed before the code was used?!
<plntyk>
probably because the developer didnt want to invest time in setting up a CI, learn the configuration etc.
<plntyk>
in-tree documentation is missing too from procd
<plntyk>
so much to do and so little time
black_ant has joined #openwrt-devel
black_ant has quit [Changing host]
black_ant has joined #openwrt-devel
dedeckeh has joined #openwrt-devel
<Thermi>
plntyk: No, it's not CI specific. It's stuff that you get already when you compile with -Werror=sign-compare
<Thermi>
With -Wall specifically
<Thermi>
Generally I mean
<Thermi>
It's standard stuff you see if you care at all
<Thermi>
And the C functions with the stack variables and use after free are like 10 lines long only.
<Thermi>
It boggles the mind
goliath has quit [Ping timeout: 252 seconds]
biangbiangmian has quit [Remote host closed the connection]
goliath has joined #openwrt-devel
<mangix>
Thermi: I doubt anyone has looked at it honestly.
<Thermi>
Yeah.
<Thermi>
Pearls
<Thermi>
/builds/Thermi/openwrt-procd/service/instance.c:1362:15: error: comparison of unsigned expression in ‘>= 0’ is always true [-Werror=type-limits]
<Thermi>
Diamonds even
<mangix>
Fortunately or unfortunately, there’s a lot of NIH code here.
<Thermi>
That's the first time reading NIH code
<Thermi>
what is that?
<mangix>
Not invented here
<Thermi>
Ah
<Thermi>
I see.
<mangix>
procd ubus uclient umdns etc...
Tost has joined #openwrt-devel
* rmilecki
has pushed mtd update
<rmilecki>
changes look more scary than they are
<rmilecki>
still blame me for issus
kakaka has quit [Ping timeout: 240 seconds]
Night-Shade has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
heffer has quit [Quit: heffer]
heffer has joined #openwrt-devel
kakaka has joined #openwrt-devel
<rsalvaterra>
mangix: I wouldn't call it NIH. What were the alternatives at the time (and even today!) at the same footprint?
<olmari>
Well... he specifically didn't say it is automatically bad thing :)
caiortp has joined #openwrt-devel
<rsalvaterra>
NIH has a usually pejorative meaning, though… But in this case I really couldn't see any alternative. :)
daregap has joined #openwrt-devel
<olmari>
Maybe that's why he started with how he started ;P but yeah... peoples are hard, y0 =D
<jow>
let's see... procd->systemd. On my system the main executable is 1.7M, the shared libsystemd-shared-247.so 2.6M
<jow>
so this already exceeds the size of my entire openwrt rootfs
<jow>
ubus->dbus, main executable 240K, shared library 330K, also requires expat, lzma, zstd, lz4, libsystemd
<jow>
that's roughly another MB
<jow>
umdns->modemmanager, the ipk for modemmanager alone is ~1.2MB
<jow>
and it still requires dbus, glib etc.
<rsalvaterra>
That reminds me… has anyone played already with dbus-broker?
<rsalvaterra>
I tried it for the lulz on my Debian system, and it worked just fine, but somehow the at-spi-bus-launcher still invokes the original dbus daemon directly.
zatwai has quit [Quit: ZNC 1.8.2+deb2~bpo10+1 - https://znc.in]
Acinonyx_ has quit [Ping timeout: 240 seconds]
jas4711 has joined #openwrt-devel
Acinonyx has joined #openwrt-devel
csrf has quit [Ping timeout: 260 seconds]
csrf has joined #openwrt-devel
Tapper has quit [Ping timeout: 268 seconds]
zatwai has joined #openwrt-devel
<pekster>
aparcar[m]: dropear logs during auth? That just identifies which pubkey was used (see the `-E` option to `ssh-keygen` from OpenSSH.) That's just reference only, no bearing on the keytype you're using.
<pekster>
dropbear*
<pekster>
From your interactive Unix-host, try for example: for kt in md5 sha256; do find ~/.ssh -name '*.pub' -print0 | xargs -0L1 ssh-keygen -E "$kt" -lf; done
<pekster>
(works for server keys too.)
kakaka has quit [Remote host closed the connection]
kakaka has joined #openwrt-devel
valku has joined #openwrt-devel
romany has joined #openwrt-devel
Namidairo has quit [Ping timeout: 260 seconds]
Namidairo has joined #openwrt-devel
noltari_ has quit [Quit: Bye ~ Happy Hacking!]
noltari has joined #openwrt-devel
Tost has quit [Ping timeout: 260 seconds]
rsalvaterra1 has joined #openwrt-devel
rsalvaterra has quit [Ping timeout: 246 seconds]
rsalvaterra1 has quit [Quit: Leaving.]
rsalvaterra has joined #openwrt-devel
swex has quit [Quit: swex]
kakaka has quit [Remote host closed the connection]
kakaka has joined #openwrt-devel
swex has joined #openwrt-devel
kakaka has quit [Remote host closed the connection]
luke-jr has quit [Remote host closed the connection]
Borromini has joined #openwrt-devel
swex has quit [Quit: swex]
swex has joined #openwrt-devel
Nick_Lowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Nick_Lowe has joined #openwrt-devel
swex has quit [Client Quit]
swex has joined #openwrt-devel
swex has quit [Client Quit]
swex has joined #openwrt-devel
Tapper has quit [Ping timeout: 240 seconds]
noahm has quit [Quit: reboot]
swex has quit [Quit: swex]
noahm has joined #openwrt-devel
swex has joined #openwrt-devel
Nick_Lowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Nick_Lowe has joined #openwrt-devel
swex has quit [Quit: swex]
swex has joined #openwrt-devel
goliath has quit [Quit: SIGSEGV]
Thermi has quit [Quit: Meet your opposition - Profane and disciplined - Take back your pride - With a pounding hammer]
Thermi has joined #openwrt-devel
<aparcar[m]>
pekster: thanks
Tapper has joined #openwrt-devel
<xdarklight>
Hauke: do you know if the reset bit (15) in GSWIP_MII_CFGp(p) is self-clearing?
<xdarklight>
Hauke: background info: I am debugging with jwh why the two AR8030 PHY based LAN ports in the 7360v2 are deaf (no RX, no TX), while the two GPHY based ones are working fine. we already found the ISOLATE bit and cleared that, but that did not do the trick (yet)
<Hauke>
xdarklight: the documentation says "Read/write register with input from and output to hardware"
<Hauke>
so I think it is self clearing
<Hauke>
but I am not sure
<Hauke>
you could try it by setting it to 1 wait some ns and then read it back
<xdarklight>
Hauke: thanks - I also checked the AVM kernel sources and there they're treating it as self-clearing with 100us delay after setting that bit
<Hauke>
do they do activly do changes to this register or is this the standard lantiq code?
zatwai has quit [Quit: ZNC 1.8.2+deb2~bpo10+1 - https://znc.in]
zatwai has joined #openwrt-devel
Borromini has quit [Quit: Lost terminal]
whyz has quit [Quit: bbl]
whyz has joined #openwrt-devel
whyz has quit [Client Quit]
Tapper has quit [Ping timeout: 240 seconds]
whyz has joined #openwrt-devel
Nick_Lowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zatwai has quit [Quit: ZNC 1.8.2+deb2~bpo10+1 - https://znc.in]
zatwai has joined #openwrt-devel
danitool has quit [Read error: Connection reset by peer]
Tapper has joined #openwrt-devel
sbrown has quit [Ping timeout: 240 seconds]
sbrown has joined #openwrt-devel
dedeckeh has quit [Ping timeout: 240 seconds]
<Tapper>
Hi did OpenWrt join the Free Software Foundation?