danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
dlg has quit [Read error: Connection reset by peer]
dlg has joined #openwrt-devel
awgh_ has joined #openwrt-devel
awgh has quit [Ping timeout: 480 seconds]
dlg has quit [Remote host closed the connection]
dlg has joined #openwrt-devel
rua has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
dlg has quit [Remote host closed the connection]
dlg has joined #openwrt-devel
clayface_ has joined #openwrt-devel
clayface has quit [Ping timeout: 480 seconds]
minimal has quit [Quit: Leaving]
swalker has quit [Quit: leaving]
swalker has joined #openwrt-devel
dlg has quit [Read error: Connection reset by peer]
dlg has joined #openwrt-devel
amaumene has joined #openwrt-devel
guidosarducci_ has joined #openwrt-devel
guidosarducci has quit []
philipp64 has joined #openwrt-devel
dlg has quit [Read error: Connection reset by peer]
dlg has joined #openwrt-devel
Grommish has joined #openwrt-devel
dlg has quit [Read error: Connection reset by peer]
dlg has joined #openwrt-devel
dlg has quit [Read error: Connection reset by peer]
dlg has joined #openwrt-devel
mrkiko has joined #openwrt-devel
dedeckeh has joined #openwrt-devel
goliath has joined #openwrt-devel
amaumene has quit [Read error: Connection reset by peer]
<Grommish>
neggles: ping
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #openwrt-devel
lmore377_ has quit [Read error: Connection reset by peer]
lmore377 has joined #openwrt-devel
dlg has quit [Read error: Connection reset by peer]
dlg has joined #openwrt-devel
danitool has joined #openwrt-devel
SuYingJie_ has joined #openwrt-devel
jow has quit [Remote host closed the connection]
jow_laptop has joined #openwrt-devel
jow_laptop is now known as jow
SuYingJie_ has quit [Quit: Page closed]
jow has quit [Remote host closed the connection]
aleksander has joined #openwrt-devel
kenny has quit [Quit: WeeChat 3.3]
<neggles>
Grommish: hi hi
<neggles>
sorry its been
<neggles>
just been ugh
Tapper has joined #openwrt-devel
noltari has quit [Quit: Bye ~ Happy Hacking!]
gladiac has quit [Read error: No route to host]
gladiac has joined #openwrt-devel
noltari has joined #openwrt-devel
noltari has quit [Read error: No route to host]
gladiac has quit [Read error: No route to host]
gladiac has joined #openwrt-devel
noltari has joined #openwrt-devel
noltari has quit [Read error: Connection reset by peer]
noltari has joined #openwrt-devel
jow_laptop has joined #openwrt-devel
jow_laptop is now known as jow
<svanheule>
ynezz: ping
<ynezz>
svanheule: sup
<svanheule>
ynezz: I seem to recall you had a G1900-48 too, or were planning to get one. Is that right?
<ynezz>
svanheule: I've currently just dgs-1210-28 and I still plan to extend testbed with more devices soon, so I'll need to look around for something bigger
eduardo010174 has joined #openwrt-devel
<ynezz>
svanheule: I would like to have realtek DUT in that testbed as well, any idea/hint for some small device which can boot initramfs image over TFTP?
<ynezz>
at least 2 ports for wan/lan testing, ideally 12V power supply
<svanheule>
if initiating a TFTP transfer from the device's boot console is fine, then the GS1900-8 might be a good option for that
<svanheule>
I'm not aware of any Realtek based siwtches you can push an image to during boot though
<ynezz>
yes, tftp pull is enough, something like 'tftpboot 0x84000000 openwrt-ipq40xx-generic-glinet_gl-b1300-squashfs-sysupgrade.bin && sf probe && sf erase 0x180000 0x1e80000 && sf write 0x84000000 0x180000 $filesize && bootipq'
<jow>
what's the current state of RB750Gr3 support in OpenWrt?
<f00b4r0>
jow: should work out of the box. With the caveat that you won't be able to configure routerboot from openwrt
<jow>
that's not important for my use case, thanks f00b4r0
<f00b4r0>
re wg pmtu discovery, isn't pmtu discovery _always_ broken? :) I had trouble with my wg links until I enabled mtu clamp as rsalvaterra did, since then I never checked whether it's still necessary
eduardo010174 has quit [Quit: Leaving]
eduardo010174 has joined #openwrt-devel
goliath has quit [Quit: SIGSEGV]
<Tapper>
Have the build bots dun building OpenWrt 21.02.2 ?
<rsalvaterra>
f00b4r0: That's why I asked how bad it would be to just enable it globally for all interfaces. It sure didn't cause any issues on my side. Maybe it would have a performance impact, since it would check all incoming/outgoing SYN packets on every interface, but aside from that…
dedeckeh has quit [Remote host closed the connection]
user95 has joined #openwrt-devel
goliath has joined #openwrt-devel
rua has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
user95 has quit [Remote host closed the connection]
srslypascal has quit [Quit: Leaving]
srslypascal has joined #openwrt-devel
srslypascal has quit [Ping timeout: 480 seconds]
srslypascal has joined #openwrt-devel
rua has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
dlg has quit [Read error: Connection reset by peer]
dlg has joined #openwrt-devel
minimal has joined #openwrt-devel
dlg has quit [Read error: Connection reset by peer]
dlg_ has joined #openwrt-devel
shibboleth has joined #openwrt-devel
kenny has joined #openwrt-devel
srslypascal is now known as Guest313
srslypascal has joined #openwrt-devel
Guest313 has quit [Ping timeout: 480 seconds]
rua has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
Tapper has quit [Ping timeout: 480 seconds]
srslypascal is now known as Guest315
srslypascal has joined #openwrt-devel
Guest315 has quit [Ping timeout: 480 seconds]
srslypascal is now known as Guest317
srslypascal has joined #openwrt-devel
Guest317 has quit [Ping timeout: 480 seconds]
srslypascal has quit []
srslypascal has joined #openwrt-devel
rua has quit [Ping timeout: 480 seconds]
owrt-snap-builds has quit [Remote host closed the connection]
rua has joined #openwrt-devel
owrt-snap-builds has joined #openwrt-devel
user95 has joined #openwrt-devel
Tapper has joined #openwrt-devel
Misanthropos has quit [Ping timeout: 480 seconds]
<rsalvaterra>
Guys, like the kernel, we could *really* use a make olddefconfig target… ;)
<olmari>
rsalvaterra: you really mean that predicting past is easier than predictin futuredefconfig? /s
<rsalvaterra>
LOL! Come on, you know what I'm talking about… ;)
<rsalvaterra>
Sometimes we spend several weeks without building a target, the world moves on… then we make a new build with make oldconfig and spend ages answering every new symbol prompt. :)
<olmari>
I know, and half of the time I couldn't be really sure should I need to answer what, even when practically usually no is okay
<rsalvaterra>
"Take my current config and for every new symbol, assume its default value." <- that's olddefconfig.
<rsalvaterra>
In the end, you can always sanity check diff -u .config.old .config for sanity checking.
<rsalvaterra>
From the department of redundancy department.
<Habbie>
would you folks take a 21.02 PR to enable xz support in squashfs-tools?
goliath has quit [Quit: SIGSEGV]
<Grommish>
neggles: Ick.. I hope it settles down for ya! Also, I'm pretty sure ths is middle of the night for you, so.. Whenever :) I'm working on cutting compoile time down, but, since mips64-openwrt-linux-musl is upstreamed, would rustup eventually be able to make use of it? I tried -Zbuild-str on the float-test compoile, but it didn't do anything
<Grommish>
neggles: -Zbuild-std
minimal has quit [Quit: Leaving]
user95 has quit [Quit: Leaving]
user95 has joined #openwrt-devel
cmonroe has quit [Ping timeout: 480 seconds]
aleksander has quit [Quit: Leaving]
owrt-1907-builds has quit [Remote host closed the connection]
owrt-snap-builds has quit [Remote host closed the connection]
owrt-2102-builds has quit [Remote host closed the connection]
owrt-1907-builds has joined #openwrt-devel
owrt-2102-builds has joined #openwrt-devel
owrt-snap-builds has joined #openwrt-devel
owrt-2102-builds has quit [Remote host closed the connection]
owrt-snap-builds has quit [Remote host closed the connection]
owrt-1907-builds has quit [Remote host closed the connection]
owrt-2102-builds has joined #openwrt-devel
nlowe has joined #openwrt-devel
owrt-2102-builds has quit [Remote host closed the connection]
owrt-snap-builds has joined #openwrt-devel
owrt-1907-builds has joined #openwrt-devel
owrt-2102-builds has joined #openwrt-devel
user95 has quit [Ping timeout: 480 seconds]
rua has quit [Ping timeout: 480 seconds]
foxtrot has joined #openwrt-devel
foxtrot is now known as Guest324
Guest324 has quit []
rua has joined #openwrt-devel
user95 has joined #openwrt-devel
foxtrot- has joined #openwrt-devel
southey has quit []
foxtrot- has quit []
southey has joined #openwrt-devel
dorf has joined #openwrt-devel
srslypascal is now known as Guest325
srslypascal has joined #openwrt-devel
user95 has quit [Ping timeout: 480 seconds]
Guest325 has quit [Ping timeout: 480 seconds]
southey has quit [Ping timeout: 480 seconds]
<ynezz>
would it be possible to merge some PR in openwrt/packages for master in order to test some changes on buildbot?
<Habbie>
ynezz, just making the PR will build (and test?) in GH Actions, btw
<Habbie>
ah, it already did
goliath has joined #openwrt-devel
foxtrot has joined #openwrt-devel
foxtrot is now known as Guest328
Ansuel has joined #openwrt-devel
dorf has quit [Remote host closed the connection]
dorf has joined #openwrt-devel
<enick_479>
couldn't we drop quilt entirely and use git instead for kernel patches?
<Habbie>
hey enick_479, thanks for the docker arm a9 merge
<enick_479>
Habbie:
<enick_479>
does it work?
<Habbie>
earlier it did not
<Habbie>
then you pushed another commit
<Habbie>
pipeline: failed
<enick_479>
Habbie: strange. how do you try to use the image?
<Habbie>
enick_479, uh, my hope was for the image to appear on hub.docker.com
<Habbie>
enick_479, i have not tried building locally from your repo yet
rua has quit [Ping timeout: 480 seconds]
<Habbie>
enick_479, but i might try that on Friday
nlowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
nlowe has joined #openwrt-devel
PaulFertser has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
nlowe has quit []
PaulFertser has joined #openwrt-devel
nlowe has joined #openwrt-devel
nlowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Borromini has joined #openwrt-devel
minimal has joined #openwrt-devel
awgh_ has quit [Quit: eschaton immanetized.]
awgh has joined #openwrt-devel
dorf has quit [Remote host closed the connection]
dorf has joined #openwrt-devel
philipp64 has quit [Quit: philipp64]
cmonroe_ has joined #openwrt-devel
eduardo010174 has quit [Quit: Leaving]
<mkresin>
aiyion: you can only switch the function of a whole group of pins. but a group might consist of only one pin.
GNUmoon has quit [Ping timeout: 480 seconds]
<mkresin>
aiyion: portmap is used to prevent leaking packets from wan to lan as early as possible. without packets would be forwarded between all switch ports after the driver is loaded and till the openwrt network config is applied
<mkresin>
portdisable is a bitmap of the switchports. disabling unused (not exposed) switch ports lowers the energy consumption
philipp64 has joined #openwrt-devel
<mkresin>
aiyion: bit 0 is port 0, bit set means disabled
philipp64 has quit []
wiebel has joined #openwrt-devel
wiebel has quit []
<mkresin>
aiyion: as far as I remeber, you've 5 switch ports, port 6 is the cpu connection and should not be disabled.
<mkresin>
aiyion: depending on the SoC, the portmap is defined as "wllll"/"llllw" or as bitmap. for the bitmap, bit not set (0) is wan and bit set (1) is lan. cpu port (port 6) should be always set (lan).
dorf has quit [Remote host closed the connection]
rua has quit [Ping timeout: 480 seconds]
dorf has joined #openwrt-devel
rua has joined #openwrt-devel
koukoutsi has joined #openwrt-devel
GNUmoon has joined #openwrt-devel
Ansuel_ has joined #openwrt-devel
<neggles>
Grommish: I believe it would, yes, but there would have to be a build for it in rust CI
Ansuel has quit [Ping timeout: 480 seconds]
<Grommish>
neggles: I managed to cut 2 hours off the compile time so far
<neggles>
i guess rustup can probably be pointed to a custom repo?
<Grommish>
neggles: Dunno, but I never had a reason to look at it since i wrote off rustup in the beginning
<neggles>
I mean all rustup does is download precompiled toolchain/stdlib from some kind of repository
Borromini has quit [Quit: leaving]
<Grommish>
neggles: *nod* I basically already do that with the installation files
Ansuel_ has quit [Quit: Probably my PC crashed or time to sleep.]
<neggles>
Grommish: I suspect it could be trivially configured to point to an OpenWrt toolchain repo
<Grommish>
neggles: Maybe, but I've already replicated the functionality
<neggles>
i mean the point of rustup is to download from a public CI / buildbot-type repo
<neggles>
not create the dist tarballs :P
<Grommish>
Yeah, but if i have to handle it with a Makefile internal to OpenWrt, I might as well do it all
<Grommish>
Making a Makefile to do rustup to handle the toolchan just puts it external for the same effort
<neggles>
I’m still not convinced that it’s particularly necessary to build the whole thing from scratch / use custom tuples it really feels like this should be in master, not packages, since it’s a toolchain & that could potentially allow for sharing an LLVM backend with the eBPF compiler
<neggles>
Oops that was meant to be two lines sorry
<neggles>
s/tuples it/tuples… and it
<Grommish>
I agree,however.. The response I've gotten to rust-lang in OpenWrt has been "Why?".. I'm not convinced I'm going to get any traction with it as a package, let alone in the core
<Grommish>
Or worse than "Why", "That's stupid"
<neggles>
point them to the “why rust in the kernel” pages
<Grommish>
That's a farly new development
<Grommish>
I've been working on this on and off since 2020
<Grommish>
neggles: rust builds out full LLVM for the targets anyway
<neggles>
not really all that new, kernel rust has been worked on since about then
<neggles>
Grommish: exactly, cause it uses LLVM as rustc’s backend - so why are we building LLVM twice…
<neggles>
or rather kernel rust was first talked about in public Aug 2020 or so, but probably been in the works since before then
<neggles>
and the point was that the reasons for rust in kernel are also good reasons for rust in OpenWrt
<Grommish>
I make it public because someone might use it.. It doesn't irritate me that it might never be in OpenWrt. If OpenWrt wants to use it, it's there.. if not, I won't be upset
<neggles>
eventually it’ll be a requirement for *some* device drivers, it makes writing OpenWrt-specific drivers a lot simpler and easier and safer (once kernel support is merged), and the memory-safety and speed/efficiency of rust code is exactly what you want in an embedded system
<Grommish>
I run master branch locally for my device, so I really don't need the build-bots or image servers.. It's a crap-tastic way to think, but when it comes down it, it's what it is
<Grommish>
But, I plan on using it, so I still want to make it work :D
nlowe has joined #openwrt-devel
<Grommish>
I won't even a CV bump from it because I don't do that kind of stuff. I know someone was looking to help with the Suricata 6 stuff in order to be able to point to it for work
dorf has quit [Remote host closed the connection]
<neggles>
Grommish: it does need to be designed with releases/CI in mind though, even if you don’t use them - if it doesn’t work with the buildbots, or it’s responsible for a third of the build time, that’s going to be problematic… and if it ends up conflicting with kernel rust that would be a big problem too
<Grommish>
neggles: The goal is to see if the buildbots can generate the toolchain installs and then the client will then just downlkoad them and install, yes
<neggles>
probably your best bet for mainline OpenWrt inclusion is waiting for RfL to make it into an LTS kernel and reusing that toolchain 😝
<jow>
exactly
<Grommish>
neggles: Which is why it's modularized like that.. It can pick the target toolchain and install it as needed
<jow>
ressources are already spread *very* thin, no need to introduce even more work with introducing a secondary toolchain to maintain, a new programming environment and language plus associated ecosystem and support tools
<jow>
so wait for upstream linux to polish it, ensure that it runs on all architectures openwrt cares about and then we can simply use it
<jow>
(wrt. linux kernel rust)
<neggles>
yeah
<Grommish>
I never heard of rust prior to trying to use Suricata6.. Only recently have I seen more news on it. Right now, it can be used as either a toolchain for host or cross-compiling
<Grommish>
as-is
<neggles>
RfL already works on x86, ARM64, arm, and mips64
nlowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<jow>
fine, so we can wait some more until it works on mips32 and ppc too
<neggles>
it might already tbh
<neggles>
maybe I should find out
<Grommish>
It's all beyond my knowledge.
<Grommish>
I let the knowledable folks deal with the hard details
philipp64 has joined #openwrt-devel
philipp64 has quit [Quit: philipp64]
GNUmoon has quit [Ping timeout: 480 seconds]
GNUmoon has joined #openwrt-devel
goliath has quit [Remote host closed the connection]
nlowe has joined #openwrt-devel
nlowe has quit [Remote host closed the connection]