<Hauke>
pkgadd: I also had the problem with the serial, but switching this was my 2. try ;-)
goliath has quit [Quit: SIGSEGV]
<Hauke>
the default network config looks broken, it expects VLAN 100
<pkgadd>
that's the same for all devices of realtek target so far
<pkgadd>
I'm not really a fan of that either
<pkgadd>
https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=target/linux/realtek/base-files/etc/board.d/02_network;h=2568fd2e0e0620d0281e826628d4d1840d8c2398;hb=HEAD#l25 there it explicitly sets up the management VLAN on VID 100, leaving the untagged ports as WAN
philipp64 has quit [Quit: philipp64]
victhor has quit [Remote host closed the connection]
home-alone has joined #openwrt-devel
Tost has quit [Ping timeout: 264 seconds]
aliceussr has joined #openwrt-devel
<aliceussr>
Hello! Who can help me compile the driver for rt5390 (Soc) from the rt5390 driver (PCI)?
<grift>
does anyone know if the cgroup2 memory controller is supposed to work on linux 5.4? i get "write error: not supported" when i echo "+memory" > /sys/fs/cgroup/cgroup/subtree_control?
weijie has quit [Ping timeout: 265 seconds]
<aparcar[m]>
Pepe: that's what I was looking for, thanks
<karlp>
because some people say it's only negative benefit fo rthem...
<karlp>
sorry, lost in the scrollback. no longer relevant
<Pepe>
aparcar[m]: The thing about this patch is that in the repository's index there is a missing kernel and libc and if it is not there, we can not update libc either kernel. We thought that this is done on purpose in OpenWrt as some kind of protection so you can not break your system while using opkg update/opkg upgrade.
<grift>
i am looking for someone or some people that would like to help me do some "sandbox" pentesting. these persons would get root access to my router and the goal would be to kick me off the internet or to escape the sandbox. the onle rule is that you dont use resources (ie saturate network or memory or storage) to cause a denial of service and kick me off that way. the only way to possibly improve the
<grift>
implemetation is to have knowledgable people scrutinize it and not just me
<rsalvaterra>
karlp: I just take it as an incentive to run newer kernels. :)
<urjaman>
Yeah i kinda expect it'll be supported longer (hopefully), but ofc there's no point if it's not being used and updated to; That said I always find it weird when a new stable has an EOL date earlier than older stable kernels... that kinda is an incentive to stay with the older ones
<rsalvaterra>
urjaman: If you prefer slower performance and/or lesser features…
* rsalvaterra
is still waiting for the MIPS32 eBPF JIT…
<urjaman>
With hardware that's running LTS kernels, usually updates only result in a bigger kernel, and hopefully the same performance :P
<rsalvaterra>
urjaman: That depends a lot on the hardware, especially the architecture…
<karlp>
rsalvaterra: so... what od you do with bpf?
<rsalvaterra>
x86(-64), for example, typically receives much more love.
<rsalvaterra>
karlp: Nothing. Yet. That's why I'm not holding my breath. :)
<urjaman>
yeah but basically unless there's somebody working to improve said specific hardware support, and you're not using any new software features, new kernels are mostly just bigger, and hopefully nothing broke
<greearb>
stintel, I'll check that crash later.
<rsalvaterra>
urjaman: Not really. It's easy to dismiss the kernel size increases as bloat if you don't follow the development. I invite you to peruse (at least) the linux-{kernel, mm, netdev, wireless} mailing list archives on a daily basis. You'll be surprised. ;)
<urjaman>
As I said, _if you're not using any of that_
<karlp>
rsalvaterra: still, for _lots_ of people, there's nothing in the new stuff.
<rsalvaterra>
karlp: The core networking code is changed and fixed *all the time*. And it's vital for OpenWrt, for example.
<rsalvaterra>
It's actually the most active subsystem in terms of kernel development.
<urjaman>
But anyways with most of the incentive for updating being security... having a newer kernel be supported for less time than the one you're on already... what.
<rsalvaterra>
Yes, even more active than graphics.
<reiffert>
stintel: I was deleting /etc/config/network
<reiffert>
ok that worked. need to find a way to create the vlans through uci...
<stintel>
it's not ideal but at least this way you keep the rest of the config without having to restore a backup, and then probably if you would restore a backup with old network config you would loose access to the device anyway
<grift>
i refuse to believe no-one genuinely cares for our selinux work and the well-being of it so i am going to lower the barrier for you all to try out our sandbox heres the url you can use a proxy so that i wont know who connected: http://defensec:skit123@openwrt.defensec.nl:7681
<stintel>
grift: the problem is that you call everything corner cases and the core policy will break stuff for many people
<ldir->
selinux stuff doesn't build under macos so I'm not playing I'm afraid.
aep has joined #openwrt-devel
<grift>
you dont need selinux, you just need a browser
<stintel>
grift: I think you did but let's agree to disagree
<reiffert>
stintel: thanks so far. I'm currently not figuring out how that DSA thing works. I was installing ip-bridge and I guess I can make it work with the bridge command. But I wonder what path I should follow, make it work through the uci utility or throw everything in a hotplug file
<grift>
stintel: sure, its a matter of interpretation
<stintel>
reiffert: I have to figure out that part of DSA myself, my DIR-860L doesn't use VLANs, so I haven't been forced to do that yet. maybe there is some more info in the forums?
norris has quit [Read error: Connection reset by peer]
HeN has quit [Ping timeout: 265 seconds]
zx2c4 has quit [Ping timeout: 272 seconds]
Tsesarevich has quit [Write error: Connection reset by peer]
Protagonistics__ has quit [Read error: Connection reset by peer]
indy___ has quit [Read error: Connection reset by peer]
whyameye has quit [Read error: Connection reset by peer]
nejon has quit [Read error: Connection reset by peer]
feepo has quit [Write error: Connection reset by peer]
carlomaragno has quit [Read error: Connection reset by peer]
arnd has quit [Read error: Connection reset by peer]
Dracos-Carazza has quit [Ping timeout: 256 seconds]
<reiffert>
I dont know how but the configured vlans have survived a reboot
nejon has quit [Ping timeout: 260 seconds]
Protagonistics__ has quit [Read error: Connection reset by peer]
carlomaragno has quit [Ping timeout: 264 seconds]
HeN has quit [Read error: Connection reset by peer]
carlomaragno has joined #openwrt-devel
Protagonistics__ has joined #openwrt-devel
HeN has joined #openwrt-devel
linzst has joined #openwrt-devel
jschwart has joined #openwrt-devel
reiffert has quit [Ping timeout: 256 seconds]
reiffert has joined #openwrt-devel
linzst has quit [Ping timeout: 260 seconds]
philipp64 has quit [Quit: philipp64]
linzst has joined #openwrt-devel
rmilecki has quit [Ping timeout: 265 seconds]
norris has quit [Ping timeout: 264 seconds]
MentalPower has quit [Read error: Connection reset by peer]
rmilecki has joined #openwrt-devel
norris has joined #openwrt-devel
MentalPower has joined #openwrt-devel
nejon has joined #openwrt-devel
norris has quit [Read error: Connection reset by peer]
MentalPower has quit [Read error: Connection reset by peer]
nejon has quit [Read error: Connection reset by peer]
valku has quit [Quit: valku]
MentalPower has joined #openwrt-devel
valku has joined #openwrt-devel
reiffert has quit [Read error: Connection reset by peer]
carlomaragno has quit [Read error: Connection reset by peer]
Protagonistics__ has quit [Read error: Connection reset by peer]
norris has joined #openwrt-devel
Protagonistics__ has joined #openwrt-devel
nejon has joined #openwrt-devel
carlomaragno has joined #openwrt-devel
linzst has quit [Quit: Leaving]
reiffert has joined #openwrt-devel
<reiffert>
I was re-adding the routes into /etc/config/network
<reiffert>
how can I make them apply and have uci configure them? uci commit was not doing it
norris has quit [Read error: Connection reset by peer]
nejon has quit [Ping timeout: 260 seconds]
Protagonistics__ has quit [Ping timeout: 264 seconds]
carlomaragno has quit [Read error: Connection reset by peer]
<reiffert>
reboot worked.
philipp64 has joined #openwrt-devel
carlomaragno has joined #openwrt-devel
norris has joined #openwrt-devel
nejon has joined #openwrt-devel
Protagonistics__ has joined #openwrt-devel
Darkmatter66 has joined #openwrt-devel
philipp64 has quit [Quit: philipp64]
<reiffert>
stintel: it's working. vlan id 1 is now untagged on the master interface. Previsouly it had to be tagged on the slave which was kinda odd.
home-alone has quit [Ping timeout: 265 seconds]
home-alone has joined #openwrt-devel
caravel has joined #openwrt-devel
carlomaragno has quit [Write error: Connection reset by peer]
nejon has quit [Read error: Connection reset by peer]
norris has quit [Read error: Connection reset by peer]
Protagonistics__ has quit [Read error: Connection reset by peer]
<greearb>
stintel, those wave-1 crashes are some sort of mem corruption in the firmware descriptors, you have hit same problem before. In case the new firmware is obviously worse than a previous one, then maybe something we can look out, but may also just random reproduction of previous issue
voltagex has quit [Ping timeout: 260 seconds]
voltagex has joined #openwrt-devel
kontaxis_ has joined #openwrt-devel
norris has joined #openwrt-devel
kontaxis has quit [Ping timeout: 268 seconds]
feriman has quit [Quit: WeeChat 3.0]
feriman has joined #openwrt-devel
jschwart has quit [Ping timeout: 260 seconds]
xdarklight_ is now known as xdarklight
<karlp>
reiffert: uci commit, then reload_config....
linzst has joined #openwrt-devel
nejon has joined #openwrt-devel
reiffert has quit [Read error: Connection reset by peer]
carlomaragno has joined #openwrt-devel
reiffert has joined #openwrt-devel
dedeckeh has joined #openwrt-devel
Protagonistics__ has joined #openwrt-devel
feriman has quit [Quit: WeeChat 3.0]
<xdarklight>
greearb: for me https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=e1938d3397ba2bc40d27dc4f97f8532228de6112 greatly reduced the crash frequency. it went from crashing once every 24-48h to crashing once after 14 days of uptime (that was 10 days ago, still running since then). this is on a Home Hub 5A with QCA9880-BR4A
Borromini has joined #openwrt-devel
jschwart has joined #openwrt-devel
<greearb>
xdarklight, glad to hear newer FW is acting nice for you.
dedeckeh has quit [Quit: Connection closed]
dedeckeh has joined #openwrt-devel
nejon has quit [Read error: Connection reset by peer]
carlomaragno has quit [Read error: Connection reset by peer]
Protagonistics__ has quit [Read error: Connection reset by peer]
Protagonistics__ has joined #openwrt-devel
jschwart has quit [Ping timeout: 260 seconds]
<grift>
not sure who that was but "gg"
<grift>
its back up
<grift>
you managed to kill yourself
carlomaragno has joined #openwrt-devel
aep has quit [Quit: WeeChat 3.0]
feriman has joined #openwrt-devel
<stintel>
greearb: I don't recall having it this frequently
feriman has quit [Client Quit]
feriman has joined #openwrt-devel
jschwart has joined #openwrt-devel
linzst has quit [Quit: Leaving]
kontaxis_ has quit [Quit: leaving]
kontaxis has joined #openwrt-devel
jschwart has quit [Ping timeout: 260 seconds]
jschwart has joined #openwrt-devel
nucleo has joined #openwrt-devel
<aparcar[m]>
stintel: dang it why is the version missing :/
dedeckeh has quit [Quit: Connection closed]
Grommish has joined #openwrt-devel
<aparcar[m]>
stintel: is that from a buildbot or your local build?
<Borromini>
aparcar[m]: is this px5g-wolfssl?
<aparcar[m]>
yes
<Borromini>
yeah just saw in my local buildroot something about 'fix your package'