<hurricos>
dansan: perhaps after Perl's IPC::Open2?
<hurricos>
but yeah. Buffers, how do they work?
<Slimey>
hah
rua has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
dangole has quit [Remote host closed the connection]
goliath has quit [Quit: SIGSEGV]
fda has joined #openwrt-devel
fda- has quit [Ping timeout: 480 seconds]
victhor has quit [Remote host closed the connection]
fda- has joined #openwrt-devel
fda has quit [Ping timeout: 480 seconds]
minimal has quit []
<neggles>
ayyyyy! APX530 works!
rua has quit [Quit: Leaving.]
valku has quit [Quit: valku]
rua has joined #openwrt-devel
legale_ has joined #openwrt-devel
<legale_>
Hello everybody!
<legale_>
I got a problem with sysupgrade. Scripts are too complicated, so i can't localize the problem. Verbose mode didn't show me nothing interesting. But simpliest way works well. mtd write kernel.bin /dev/mtd6 && mtd write squashfs-rootfs.bin /dev/mtd13
<legale_>
What do you think about to add this simple upgrade method to kernel?
<PaulFertser>
legale_: mtd write is used by sysupgrade internally
<legale_>
yes, and this place in sysupgrade works well. I mean part that updates kernel.
<PaulFertser>
legale_: you can't just write squashfs to a ubi volume because it might be too big (then it wastes space) or too small (then it can't contain rootfs) for the file you're upgrading to.
<PaulFertser>
legale_: why do you think it's the kernel upgrade part that's problematic? Your log doesn't imply that.
<legale_>
No. kernel part is working.
<legale_>
then something goes wrong. But sysupgrade is working till the end. Somehow ubi partition became demaged. On the next boot i got this:
<neggles>
the partition layout in your dts is a *mess*
<neggles>
is that what the OEM firmware uses?
<legale_>
I did it because of backward compatability with stock fw
goliath has joined #openwrt-devel
<PaulFertser>
legale_: either you're concatenating those two ubi partitions and use them combined, or you are not, and then you need to mark them accordingly.
<PaulFertser>
legale_: and you need to define label "ubi" only for a single partition on combined device.
<PaulFertser>
legale_: your paste lacks the beginning so we can't check kernel command line in use.
<neggles>
found the OEM partition layout in the forum post
<neggles>
it's a little weird but nothing out of the ordinary, two kernels, two rootfs, one data
<stintel>
yay should get new flex atx psus today, gonna replace the ones in my M300s and use one of them in the M200 that is without PSU atm
<neggles>
it would make most sense to just use the existing kernel, rootfs, and data partitions as... kernel, rootfs, and rwdata
<legale_>
i use breed bootloader for development. so boot command is boot flash 0x2300000
<stintel>
sysupgrade could use some love, you can't see what is happening unless you do it from a serial console
<stintel>
I had the idea to add some logging to it, so that you can at least check some things in case of a failure
<legale_>
i got serial console: log is attached
<stintel>
ahh
<stintel>
I'm gonna have to get my hands on a NAND device that uses UBI. I know nothing about that :(
<neggles>
the partition tree in here is an absolute mess
<PaulFertser>
hurricane electric had an outage, I might have missed something but I see the link to DTS.
<neggles>
last thing was me pointing out the mess that the partition table is
<neggles>
legale_: why not just https://paste.debian.net/1226371/ overlay both kernel/rootfs partitions with a combined 64MB kernel+rootfs partition, and use the "data" partition at the end for rwfs?
<neggles>
adding ubifs into the mix is unnecessary
<PaulFertser>
neggles: I think combined partition on nand targets isn't that nice
<legale_>
Dts applied to ubi-concat has no differences.
<legale_>
If you find "where the dog rushed" I will be very grateful.
<legale_>
Maybe i should dump /bin/sh -x /sbin/sysupgrade?
<legale_>
I have an off-topic question: mt7621 uses hardware oob. it is BCH ecc with page 2048b layout: 512 + 16 + 512 + 16 + 512 + 16 + 512 + 16. Is there any ability to dump nand from a running system with correct oob data?
<legale_>
At the moment i have to use ./BCH utility by MTK to convert raw data without oob to data with oob.
<Namidairo>
would you not have nanddump from mtd-utils
DRP4NSX has joined #openwrt-devel
<PaulFertser>
legale_: if ubi attaches to mtd15 before sysupgrade but can't do it after I guess it means some part of its gets overwritten. Probably your sysupgrade flashes kernel to one of the partitions that overlap with the ubipart* partitions?
<PaulFertser>
legale_: btw, DT in https://pastebin.com/8dfs062q is clearly different from what you're showing before
<PaulFertser>
legale_: so you're flashing to 0×000002300000-0×000004300000 but actually booting from 0×000000300000-0×000002300000, now that explains everything.
<PaulFertser>
Because 0×000002720000-0×000004300000 : “ubipart0”
<PaulFertser>
legale_: you got yourself into a trap with all those overlaps, but now it's clear.
<PaulFertser>
legale_: what do you need data with oob for? The driver and hardware should be doing the right thing for you when you write anything to nand.
<legale_>
Namidairo: nanddump -o returns incorrect data. nandtest just kills your data.
<PaulFertser>
legale_: btw, if you were pasting full serial output right from the beginning I'd probably spot the problem much earlier because I would naturally try to check the bootloader is using the same partition you write the kernel to.
<legale_>
PaulFertser: correct data + oob needed to revive nand chip with programmer
<neggles>
only if your programmer can't write the OOB
<PaulFertser>
legale_: indeed
<PaulFertser>
legale_: but do you often happen to overwrite bootloader accidentally?
<neggles>
you're better off not touching the bootloader partition & just using u-boot to rewrite corrupt partitions...
<stintel>
damnit, shipment got rerouted to office because my phone was on silent and missed the courier's call. can only pick it up on Monday
<stintel>
grrrrrr
<neggles>
stintel: F
<PaulFertser>
legale_: do you agree with my explanation of why sysupgrade was failing for you?
<legale_>
neggles: which programmer can do it mtk way?
<neggles>
legale_: u-boot, on the device :P and, any programmer that's configured appropriately... positioning of ecc information in OOB is relatively standardized i thought
<neggles>
as PaulFertser said, do you often overwrite u-boot?
<legale_>
PaulFertser: not often. For now only once. But the question is possibility of getting this data.
<PaulFertser>
legale_: there's nothing better than nanddump. If it returns incorrect data it means something is wrong with the kernel driver.
<stintel>
neggles: guess I should make it a habbit to order straight to the office and avoid this crap. if they bring it to my place they need to be able to call me because 1/ the doorbells are behind a close gate and 2/ my doorbell is broken if the gate would be open
<stintel>
I can hear them talk but I can't speak, if I press the speak button the light in the hallway switches on 😂
<PaulFertser>
Are they so fast that they manage to run away even if you rush to the door after hearing them speak?
<stintel>
PaulFertser: 6 floors ...
<PaulFertser>
Oh heh that would explain it :)
<PaulFertser>
Do you pay the landlord for that broken doorbell?
<legale_>
PaulFertser: back to our rams. Why kernel is looking ubi in ubipart1 (mtd15) and not ubipart0 (mtd13)?
<PaulFertser>
legale_: mtd15 is the combined ubipart0+ubipart1 , so it's looking exactly where it should be looking.
<stintel>
actually there is a building manager company and I pay them a lot, even monthly fee for central heating that never worked, not much I can do besides move out
<PaulFertser>
legale_: your problem is that you overwrite ubi by flashing the kernel to the wrong place.
<PaulFertser>
legale_: please reread what I sent you, paying attention to the offsets.
<stintel>
my rental contract says I have to pay these bills and that they can be increased, and as I am not the owner I can't really handle it with the building manager either
<PaulFertser>
stintel: ffs, and the owner is not cooperating because it's easy for them to find someone else if you move out?
<stintel>
I'm looking to buy something but my options are limited - I will only get a top floor duplex
<stintel>
it's not easy for them to find a new tenant, I complained about a few things a few times already, some are fixed, some are in the process of being fixed
<stintel>
otoh I'm here 6 years without rent being increased ever, I've heard many different stories
<legale_>
PaulFertser: So to solve this problem i need to add partition for kernel without overlap?
<stintel>
I'll cut the OT now to avoid further interrupting the on-topic problem, sorry
<PaulFertser>
legale_: why are you writing the kernel to 0×000002300000-0×000004300000 in the first place? It isn't where the bootloader fetches the kernel from, right?
<PaulFertser>
legale_: why do not you show full serial output?..
<legale_>
PaulFertser: Wait i'll do it in 5 mins.
<PaulFertser>
legale_: my guess is that you should kernel_stock partition to be just "kernel" (and the other to be named "kernel2") and that would be it.
<legale_>
PaulFertser: when i flash with my hands. I make it this way: first i flash kernel than rootfs.
<PaulFertser>
legale_: I think your bootloader is booting from 0×000000300000-0×000002300000 and you never overwrite that.
<PaulFertser>
legale_: but you overwrite your freshly flashed kernel with your rootfs, so everything seems to work.
<neggles>
stintel: ooooof, yeah, sounds like a parcel locker / send to work is gonna be the better option...
<stintel>
neggles: my home is my workplace :)
<stintel>
but the courier company has an office 1m walking distance from my apartment so I should just always have things delivered there
<stintel>
unless they weigh a ton :P
<neggles>
haha
<neggles>
yeah :P
<legale_>
PaulFerstser: It is working with layout with additional partition for openwrt kernel. The same place as stock kernel 1 0x2300000 but with different size 0x420000. It is without overlapping.
<legale_>
Спасибо, бро. Хорошо помог! С Новым годом!
<stintel>
:)
<stintel>
I could almost fully understand that o_O
<legale_>
Thanks to all. Happy New Year developers!
victhor has joined #openwrt-devel
Borromini has joined #openwrt-devel
* enyc
meeps
Borromini has quit [Ping timeout: 480 seconds]
Borromini has joined #openwrt-devel
<mangix>
Huh. Was that auto translate?
<mangix>
stintel: i undersood thanks. Good help. Happy new year.
dangole has joined #openwrt-devel
<rsalvaterra>
stintel: Me too… :P
<rsalvaterra>
Ok, guys, firewall3 is fixed for 5.15. :)
james_su_ has quit [Remote host closed the connection]
james_su has quit [Quit: Page closed]
fda- has quit [Ping timeout: 480 seconds]
legale_ has quit [Remote host closed the connection]
fda has joined #openwrt-devel
rua has quit [Quit: Leaving.]
rua has joined #openwrt-devel
<Tapper>
Hi people if I kick off a build now from master will I get firewall 3 or firewall 4?
<Tapper>
My config was set to build with firewall 3 as of 5 days ago.
<Borromini>
Is fw4 default already? I thought not?
nlowe has joined #openwrt-devel
<rsalvaterra>
Borromini: Not yet, but it will be.
<rsalvaterra>
At least, we want it to be, for the next release.
<rsalvaterra>
However, mwan3 is still iptables-only. And if it won't work with nftables on time for the next release, we should at least give users the choice of using fw3/iptables if they want to use mwan3.
<dangole>
Yep. we'll need mwan4... and banip to work with nftables instead of iptables (+ipset). as all targets have arrived on 5.10, i'd say branch-off now and release with fw3, because it's going to take more than 6 months to sort out iptables-corner-cases in a **router** distro...
pmelange has joined #openwrt-devel
pmelange has left #openwrt-devel [#openwrt-devel]
<Borromini>
rsalvaterra: neat. time to learn some nftables then i guess :P
<stintel>
defaults don't change what is in your config
danitool has joined #openwrt-devel
GNUmoon has quit [Remote host closed the connection]
aiyion has quit [Remote host closed the connection]
GNUmoon has joined #openwrt-devel
goliath has quit [Quit: SIGSEGV]
aiyion has joined #openwrt-devel
Tapper has quit [Ping timeout: 480 seconds]
rua1 has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
<Borromini>
stintel: i figured, but nftables seems the way to go so time to switch my regular Linux clients as well :)
<stintel>
yeah I did my laptop while I was in the hospital
<stintel>
and my hypervisor at OVH somewhere this week
<stintel>
my main router is fw4/nftables for a few months already
<stintel>
now I'm going to have to spend some time to make vallumd nftables compatible because nftables doesn't use ipset but supports sets of its own
<stintel>
guess I can take another week off in February and work on that then
Borromini has quit [Ping timeout: 480 seconds]
<aparcar>
rsalvaterra: what about mwan4 rather than fixing mwan3?
rua1 has joined #openwrt-devel
rua has quit [Ping timeout: 480 seconds]
rua1 has quit [Ping timeout: 480 seconds]
<rsalvaterra>
aparcar: That's out of my league, for now. I use mwan3 because it makes policy routing trivial to an idiot like me. :)
rua has joined #openwrt-devel
<rsalvaterra>
dangole: Most definitely. However, creating an mwan4, even taking mwan3 as a base, is not a trivial task. Unless someone with the required skills steps up to the plate, we need to keep mwan3 available.
<rsalvaterra>
In my humble opinion, fw4 for 22.x is rather ambitious.
rua has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
nlowe_ has joined #openwrt-devel
<nick[m]1234>
the image builder is broken? luci-app-firewall conflicts "The following packages conflict with firewall:" "firewall4 *"
nlowe has quit [Ping timeout: 480 seconds]
<dangole>
rsalvaterra, aparcar: that's exactly what i meant. it's quite a lot of work... so keeping fw3 by default and fw4 opt-in would be the way to go for an early-2022 release i guess
<rsalvaterra>
dangole: Amen!
<rsalvaterra>
Release early, release often, and all that jazz. ;)
valku has joined #openwrt-devel
DRP4NSX has quit [Remote host closed the connection]
<aparcar>
fine with me, I'd like to get a comment of stintel however
<stintel>
about ?
<aparcar>
next release with fw3
<aparcar>
and then the release after with Kernel 5.15 and fw4
<stintel>
so I did all this work for nothing, great. I thought we discussed that in a meeting already.
<rsalvaterra>
stintel: Wait, nobody said that! It's not for nothing, we definitely want to move to fw4 as soon as we can.
<rsalvaterra>
But not one moment before that.
<stintel>
I prioritized work on firewall4 because we were planning to use that in the next release, so we could branch that release soonish around new years
<rsalvaterra>
Indeed. But I believe we neglected the importance of mwan3. I don't remember speaking about it in the last meeting. :/
<stintel>
and if we don't switch the default now there will be incentive for making mwan nftables/firewall4 compatible and we will have the same discussion when we want to branch the next-next release
<stintel>
no incentive*
<rsalvaterra>
I don't know. feckert is the mwan3 author. Nobody better to estimate how much work it will take to create an mwan4. :/
dangole has quit [Remote host closed the connection]
dangole has joined #openwrt-devel
jlsalvador has quit [Quit: jlsalvador]
rua has quit [Ping timeout: 480 seconds]
jlsalvador has joined #openwrt-devel
rua has joined #openwrt-devel
fda has quit [Ping timeout: 480 seconds]
nlowe_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
rua has quit [Ping timeout: 480 seconds]
fda has joined #openwrt-devel
<PaulFertser>
rsalvaterra: mwan3 is not part of the default image anyway, so whoever wants mwan3 can downgrade to fw3 along the way, no need to keep fw3 the default I guess?
<Pepes>
PaulFertser: What about multi wan, which is I'd say so common?
<Pepes>
It is nice to have failover, etc.
rua has joined #openwrt-devel
<PaulFertser>
Pepes: it's common but not common enough to be in the default image, that's my point. So default can switch to fw4 for the majority, and then those who needs it can go back to fw3.
<Pepes>
No, default should be fw3 and opt-in fw4.
<PaulFertser>
Pepes: why would it be better in your opinion?
<Pepes>
A recent fixes for fw4 landed just now. Not sure, if this is in productive state. Yes, there are some people who has it running, but switching it to fw4 is a huge step and OpenWrt should do a new release soon. If you add fw4 now or switch to it, it will postpone the whole release. There are still things, which should need to be moved to nftables instead of iptables. My reason
<Pepes>
is to keep things like they are now, have kernel 5.10, do a branch off and ask people for testing and release it. :) There isn't anything wrong with releasing often, right? After branch-off, do what you want in the master branch, switch it to fw4 and if it is ok, ship it to users.
<aparcar>
Pepes: if maintainer don't respond to that call the list stays incomplete
<Pepes>
aparcar: You need to encourage them somehow or try to push them a little bit with some gifts. :)
<aparcar>
Pepes: the best gift I can switch of is a default installation of fw4
<Pepes>
If you do that now, you will postpone the branch off. You can do it after the branch off.
<Pepes>
There was some idea that core members will try to reward contributors. Not sure about the state, though.
<Pepes>
Doing the last minute change before branch off is not a good idea, that's my option.
<stintel>
why would it postpone the branching? the branching is done to freeze versions and stabilize what is branched
nlowe has joined #openwrt-devel
jlsalvador has quit [charon.oftc.net liquid.oftc.net]
PaulFertser has quit [charon.oftc.net liquid.oftc.net]
dwmw2 has quit [charon.oftc.net liquid.oftc.net]
AndyCap has quit [charon.oftc.net liquid.oftc.net]
KGB-1 has quit [charon.oftc.net liquid.oftc.net]
zatwai has quit [charon.oftc.net liquid.oftc.net]
\x has quit [charon.oftc.net liquid.oftc.net]
Acinonyx_ has quit [charon.oftc.net liquid.oftc.net]
floof58 has quit [charon.oftc.net liquid.oftc.net]
xdarklight has quit [charon.oftc.net liquid.oftc.net]
SamantazFox has quit [charon.oftc.net liquid.oftc.net]
gladiac has quit [charon.oftc.net liquid.oftc.net]
_lore_ has quit [charon.oftc.net liquid.oftc.net]
xes has quit [charon.oftc.net liquid.oftc.net]
EqUaTe has quit [charon.oftc.net liquid.oftc.net]
mva has quit [charon.oftc.net liquid.oftc.net]
jow has quit [charon.oftc.net liquid.oftc.net]
zorun has quit [charon.oftc.net liquid.oftc.net]
YSC has quit [charon.oftc.net liquid.oftc.net]
nbd has quit [charon.oftc.net liquid.oftc.net]
t4h4[m] has quit [charon.oftc.net liquid.oftc.net]
fieryeagle954[m] has quit [charon.oftc.net liquid.oftc.net]
embargo has quit [charon.oftc.net liquid.oftc.net]
lynxis has quit [charon.oftc.net liquid.oftc.net]
owrt-1907-builds has quit [charon.oftc.net liquid.oftc.net]
kabel has quit [charon.oftc.net liquid.oftc.net]
omni has quit [charon.oftc.net liquid.oftc.net]
FLD has quit [charon.oftc.net liquid.oftc.net]
lemmi has quit [charon.oftc.net liquid.oftc.net]
hauke has quit [charon.oftc.net liquid.oftc.net]
blogic has quit [charon.oftc.net liquid.oftc.net]
<Pepes>
I know that in your case it works well and you are using it, but others might not and there might be issues, which are not known and useful packages as it was said are not compatible with nftables. Switching to fw4 by default it will postpone it. There's a lot of work to do about fw4. Users if they want can switch to it manually. But there is also nothing wrong to release
<Pepes>
often, right?
<Pepes>
Release what is there in master branch and then prepare a new release. Users will be happy.
jlsalvador has joined #openwrt-devel
floof58 has joined #openwrt-devel
dwmw2 has joined #openwrt-devel
PaulFertser has joined #openwrt-devel
Acinonyx_ has joined #openwrt-devel
gladiac has joined #openwrt-devel
omni has joined #openwrt-devel
mva has joined #openwrt-devel
embargo has joined #openwrt-devel
lynxis has joined #openwrt-devel
hauke has joined #openwrt-devel
owrt-1907-builds has joined #openwrt-devel
kabel has joined #openwrt-devel
FLD has joined #openwrt-devel
\x has joined #openwrt-devel
AndyCap has joined #openwrt-devel
xdarklight has joined #openwrt-devel
KGB-1 has joined #openwrt-devel
blogic has joined #openwrt-devel
YSC has joined #openwrt-devel
jow has joined #openwrt-devel
nbd has joined #openwrt-devel
zorun has joined #openwrt-devel
EqUaTe has joined #openwrt-devel
fieryeagle954[m] has joined #openwrt-devel
t4h4[m] has joined #openwrt-devel
xes has joined #openwrt-devel
_lore_ has joined #openwrt-devel
SamantazFox has joined #openwrt-devel
lemmi has joined #openwrt-devel
zatwai has joined #openwrt-devel
<stintel>
that's the whole point of branching, so that more people can test new features and report problems, so they can get fixed
<Pepes>
For me it seems like more issues exaclty what happened during 21.02 release. LuCI DSA support was not ready, migration network configuration was not ready and it delayed the release.
<Guest9490>
For DSA hauke already summarized that the people merging it where different ones then fixing it. In this case stintel is likely available to help fixing things until it runs smoothly. fw3 isn't deleted so whoever plans to keep using it, great.
owrt-1907-builds has quit [charon.oftc.net liquid.oftc.net]
zorun has quit [charon.oftc.net liquid.oftc.net]
jow has quit [charon.oftc.net liquid.oftc.net]
fieryeagle954[m] has quit [charon.oftc.net liquid.oftc.net]
zatwai has quit [charon.oftc.net liquid.oftc.net]
YSC has quit [charon.oftc.net liquid.oftc.net]
jlsalvador has quit [charon.oftc.net liquid.oftc.net]
PaulFertser has quit [charon.oftc.net liquid.oftc.net]
xes has quit [charon.oftc.net liquid.oftc.net]
floof58 has quit [charon.oftc.net liquid.oftc.net]
gladiac has quit [charon.oftc.net liquid.oftc.net]
t4h4[m] has quit [charon.oftc.net liquid.oftc.net]
\x has quit [charon.oftc.net liquid.oftc.net]
EqUaTe has quit [charon.oftc.net liquid.oftc.net]
omni has quit [charon.oftc.net liquid.oftc.net]
xdarklight has quit [charon.oftc.net liquid.oftc.net]
FLD has quit [charon.oftc.net liquid.oftc.net]
lemmi has quit [charon.oftc.net liquid.oftc.net]
nbd has quit [charon.oftc.net liquid.oftc.net]
mva has quit [charon.oftc.net liquid.oftc.net]
hauke has quit [charon.oftc.net liquid.oftc.net]
blogic has quit [charon.oftc.net liquid.oftc.net]
AndyCap has quit [charon.oftc.net liquid.oftc.net]
SamantazFox has quit [charon.oftc.net liquid.oftc.net]
dwmw2 has quit [charon.oftc.net liquid.oftc.net]
kabel has quit [charon.oftc.net liquid.oftc.net]
_lore_ has quit [charon.oftc.net liquid.oftc.net]
lynxis has quit [charon.oftc.net liquid.oftc.net]
embargo has quit [charon.oftc.net liquid.oftc.net]
Acinonyx_ has quit [charon.oftc.net liquid.oftc.net]
KGB-1 has quit [charon.oftc.net liquid.oftc.net]
<stintel>
also the idea is that fw4 is compatible with fw3 config
<Pepes>
And aparcar is Guest9490 agan. :)
<Pepes>
again*
<stintel>
I don't think you can compare it with DSA
<aparcar>
yea sorry the matrix bot is currently broken
PaulFertser has joined #openwrt-devel
AndyCap has joined #openwrt-devel
xdarklight has joined #openwrt-devel
FLD has joined #openwrt-devel
_lore_ has joined #openwrt-devel
Acinonyx_ has joined #openwrt-devel
YSC has joined #openwrt-devel
xes has joined #openwrt-devel
mva has joined #openwrt-devel
jow has joined #openwrt-devel
EqUaTe has joined #openwrt-devel
nbd has joined #openwrt-devel
zorun has joined #openwrt-devel
fieryeagle954[m] has joined #openwrt-devel
t4h4[m] has joined #openwrt-devel
omni has joined #openwrt-devel
embargo has joined #openwrt-devel
lynxis has joined #openwrt-devel
hauke has joined #openwrt-devel
owrt-1907-builds has joined #openwrt-devel
kabel has joined #openwrt-devel
lemmi has joined #openwrt-devel
dwmw2 has joined #openwrt-devel
blogic has joined #openwrt-devel
KGB-1 has joined #openwrt-devel
SamantazFox has joined #openwrt-devel
jlsalvador has joined #openwrt-devel
zatwai has joined #openwrt-devel
floof58 has joined #openwrt-devel
gladiac has joined #openwrt-devel
\x has joined #openwrt-devel
Acinonyx_ has quit [Read error: Connection reset by peer]
<stintel>
also the headsup has been given 3 months ago, and as you stated yourself a whole bunch of packages is not ready. should we postpone core plans because community doesn't care?
<Pepes>
Well, packages needs to support nftables instead of iptables. What I am trying to say is that if you add more changes to do release now, it will be delayed no matter what. From my point of view is a good to take what is in master branch (especially kernel 5.10) and prepare a release.
goliath has joined #openwrt-devel
<Pepes>
Community cares. I see sometimes asked what needs to be done for nftables and no one replied to it. What about reaching him privately or headsup on openwrt-devel list?
Acinonyx has joined #openwrt-devel
<stintel>
take the package(s) that you use and fix them, like I did for miniupnpd
<stintel>
it's the only way forward, like I said, otherwise we'll have this discussion again in the future when we want to do the next-next branch
<dangole>
stintel, aparcar, rsalvaterra: if everyone if fine with making a release where many things in packages feed are known-to-be-broken, that's also fine. we should at least introduce dependency on fw3 or !fw4 for the affected packages.
Borromini has quit [Ping timeout: 480 seconds]
<Pepes>
The only way forward I see is to cooperate with the community and maintainers and developers from packages repository. Send an email to openwrt-devel regarding switching from fw3 to fw4, what steps needs to be done to switch to it and if others want, they can check the list and help. Dont offensive saying that community does not care. If you want to prepare early 2022 release,
<Pepes>
then you need to switch to fw4 in master branch for month or two. It will push the community to fix it, but during the time, there will be no release or am I wrong? How the core members are cooperating with the packages feed? That's also a good question to be asked first.
<Pepes>
mangix was using GitHub internal discussion and then it was disabled. At least it was the place, where contributors or at least packages maintainers could speak to each other, but someone got annoyed because of it. I think that's also an issue when someone mention globally the group, right? They could have turn off the notifications.
<stintel>
I disabled that because there are too many places where things are being discussed already
<Pepes>
But I think I said what I wanted to say.
<stintel>
we have IRC, ML, forum
SamantazFox has quit [Remote host closed the connection]
<mangix>
Pepes: to be fair I only used it once
jow has quit [Ping timeout: 480 seconds]
zorun has quit [reticulum.oftc.net liquid.oftc.net]
owrt-1907-builds has quit [reticulum.oftc.net liquid.oftc.net]
fieryeagle954[m] has quit [reticulum.oftc.net liquid.oftc.net]
YSC has quit [reticulum.oftc.net liquid.oftc.net]
zatwai has quit [reticulum.oftc.net liquid.oftc.net]
PaulFertser has quit [reticulum.oftc.net liquid.oftc.net]
jlsalvador has quit [reticulum.oftc.net liquid.oftc.net]
xes has quit [reticulum.oftc.net liquid.oftc.net]
floof58 has quit [reticulum.oftc.net liquid.oftc.net]
gladiac has quit [reticulum.oftc.net liquid.oftc.net]
t4h4[m] has quit [reticulum.oftc.net liquid.oftc.net]
\x has quit [reticulum.oftc.net liquid.oftc.net]
omni has quit [reticulum.oftc.net liquid.oftc.net]
EqUaTe has quit [reticulum.oftc.net liquid.oftc.net]
xdarklight has quit [reticulum.oftc.net liquid.oftc.net]
lemmi has quit [reticulum.oftc.net liquid.oftc.net]
nbd has quit [reticulum.oftc.net liquid.oftc.net]
FLD has quit [reticulum.oftc.net liquid.oftc.net]
mva has quit [reticulum.oftc.net liquid.oftc.net]
hauke has quit [reticulum.oftc.net liquid.oftc.net]
blogic has quit [reticulum.oftc.net liquid.oftc.net]
AndyCap has quit [reticulum.oftc.net liquid.oftc.net]
dwmw2 has quit [reticulum.oftc.net liquid.oftc.net]
kabel has quit [reticulum.oftc.net liquid.oftc.net]
_lore_ has quit [reticulum.oftc.net liquid.oftc.net]
embargo has quit [reticulum.oftc.net liquid.oftc.net]
lynxis has quit [reticulum.oftc.net liquid.oftc.net]
KGB-1 has quit [reticulum.oftc.net liquid.oftc.net]
dwmw2 has joined #openwrt-devel
xdarklight has joined #openwrt-devel
floof58 has joined #openwrt-devel
PaulFertser has joined #openwrt-devel
EqUaTe has joined #openwrt-devel
fieryeagle954[m] has joined #openwrt-devel
embargo has joined #openwrt-devel
omni has joined #openwrt-devel
lynxis has joined #openwrt-devel
owrt-1907-builds has joined #openwrt-devel
kabel has joined #openwrt-devel
hauke has joined #openwrt-devel
lemmi has joined #openwrt-devel
KGB-1 has joined #openwrt-devel
zatwai has joined #openwrt-devel
AndyCap has joined #openwrt-devel
_lore_ has joined #openwrt-devel
xes has joined #openwrt-devel
gladiac has joined #openwrt-devel
mva has joined #openwrt-devel
zorun has joined #openwrt-devel
nbd has joined #openwrt-devel
t4h4[m] has joined #openwrt-devel
YSC has joined #openwrt-devel
blogic has joined #openwrt-devel
\x has joined #openwrt-devel
jlsalvador has joined #openwrt-devel
FLD has joined #openwrt-devel
jow has joined #openwrt-devel
KGB-1 has quit [Ping timeout: 480 seconds]
<aparcar>
rsalvaterra: are you in contact with the mwan3 dev?
KGB-1 has joined #openwrt-devel
YSC has quit [charon.oftc.net liquid.oftc.net]
fieryeagle954[m] has quit [charon.oftc.net liquid.oftc.net]
PaulFertser has quit [charon.oftc.net liquid.oftc.net]
zatwai has quit [charon.oftc.net liquid.oftc.net]
jlsalvador has quit [charon.oftc.net liquid.oftc.net]
zorun has quit [charon.oftc.net liquid.oftc.net]
owrt-1907-builds has quit [charon.oftc.net liquid.oftc.net]
xes has quit [charon.oftc.net liquid.oftc.net]
floof58 has quit [charon.oftc.net liquid.oftc.net]
gladiac has quit [charon.oftc.net liquid.oftc.net]
t4h4[m] has quit [charon.oftc.net liquid.oftc.net]
\x has quit [charon.oftc.net liquid.oftc.net]
EqUaTe has quit [charon.oftc.net liquid.oftc.net]
omni has quit [charon.oftc.net liquid.oftc.net]
xdarklight has quit [charon.oftc.net liquid.oftc.net]
FLD has quit [charon.oftc.net liquid.oftc.net]
lemmi has quit [charon.oftc.net liquid.oftc.net]
nbd has quit [charon.oftc.net liquid.oftc.net]
mva has quit [charon.oftc.net liquid.oftc.net]
hauke has quit [charon.oftc.net liquid.oftc.net]
blogic has quit [charon.oftc.net liquid.oftc.net]
AndyCap has quit [charon.oftc.net liquid.oftc.net]
dwmw2 has quit [charon.oftc.net liquid.oftc.net]
kabel has quit [charon.oftc.net liquid.oftc.net]
_lore_ has quit [charon.oftc.net liquid.oftc.net]
embargo has quit [charon.oftc.net liquid.oftc.net]
lynxis has quit [charon.oftc.net liquid.oftc.net]
srslypascal_ has joined #openwrt-devel
srslypascal is now known as Guest10637
srslypascal_ is now known as srslypascal
jlsalvador has joined #openwrt-devel
AndyCap has joined #openwrt-devel
PaulFertser has joined #openwrt-devel
xdarklight has joined #openwrt-devel
mva has joined #openwrt-devel
YSC has joined #openwrt-devel
omni has joined #openwrt-devel
kabel has joined #openwrt-devel
gladiac has joined #openwrt-devel
\x has joined #openwrt-devel
zatwai has joined #openwrt-devel
zorun has joined #openwrt-devel
dwmw2 has joined #openwrt-devel
EqUaTe has joined #openwrt-devel
nbd has joined #openwrt-devel
owrt-1907-builds has joined #openwrt-devel
hauke has joined #openwrt-devel
t4h4[m] has joined #openwrt-devel
lynxis has joined #openwrt-devel
embargo has joined #openwrt-devel
xes has joined #openwrt-devel
fieryeagle954[m] has joined #openwrt-devel
FLD has joined #openwrt-devel
floof58 has joined #openwrt-devel
blogic has joined #openwrt-devel
lemmi has joined #openwrt-devel
_lore_ has joined #openwrt-devel
dangole has quit [Remote host closed the connection]
dangole has joined #openwrt-devel
Guest10637 has quit [Ping timeout: 480 seconds]
Borromini has joined #openwrt-devel
Tapper has joined #openwrt-devel
dangole has quit [Remote host closed the connection]
nlowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
nlowe has joined #openwrt-devel
nlowe has quit []
minimal has joined #openwrt-devel
dangole has joined #openwrt-devel
<rsalvaterra>
aparcar: Not directly, but he's idling in this channel. :)
rmilecki has joined #openwrt-devel
<rsalvaterra>
dangole: I'm also fine with that. Like I wrote before, as long as the user has the choice, that works for me.
<zorun>
I didn't find any mailing list discussion about fw3/fw4 switching
<rsalvaterra>
dangole: I *think* (I'm not sure, but I'm about 90 % confident) iptables can coexist with nftables (in the kernel, I mean). This means, in theory, a user could have both fw4 and mwan3 installed, but I have absolutely no idea of how they would interact with each other in practice. I'd rather keep that can of worms hermetically closed and have fw3 conflicting with fw4. :P
dedeckeh has joined #openwrt-devel
<hauke>
there is also a wrapper for the iptables user space application which will generate nftables rules
<hauke>
debian uses this for iptables by default
<rsalvaterra>
hauke: And there's also iptables-translate, for firewall.user rules. :)
nlowe has joined #openwrt-devel
nlowe has quit []
seasonal has joined #openwrt-devel
rmilecki has quit [Remote host closed the connection]
<PaulFertser>
rsalvaterra: the problem is that using that iptables wrapper would require rulesets of specific structure, so fw4 wouldn't be able to produce nicer rules probably.
nlowe has joined #openwrt-devel
vchrizz has quit [Read error: No route to host]
nlowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
vchrizz has joined #openwrt-devel
seasonal has quit [Quit: Page closed]
<rsalvaterra>
PaulFertser: If the automatic translation worked 100 %, I'd gladly accept less than optimal nftables rules as an interim solution.
<PaulFertser>
rsalvaterra: that would mean you'd just be using fw3 to generate iptables rules then.
dangole has quit [Remote host closed the connection]
dangole has joined #openwrt-devel
rmilecki has joined #openwrt-devel
Borromini has quit [Quit: Lost terminal]
floof58 has quit []
floof58 has joined #openwrt-devel
bluew has quit [Quit: Leaving]
bluew has joined #openwrt-devel
owrt-1907-builds has quit [charon.oftc.net liquid.oftc.net]
fieryeagle954[m] has quit [charon.oftc.net liquid.oftc.net]
zatwai has quit [charon.oftc.net liquid.oftc.net]
YSC has quit [charon.oftc.net liquid.oftc.net]
jlsalvador has quit [charon.oftc.net liquid.oftc.net]
PaulFertser has quit [charon.oftc.net liquid.oftc.net]
zorun has quit [charon.oftc.net liquid.oftc.net]
xes has quit [charon.oftc.net liquid.oftc.net]
gladiac has quit [charon.oftc.net liquid.oftc.net]
t4h4[m] has quit [charon.oftc.net liquid.oftc.net]
\x has quit [charon.oftc.net liquid.oftc.net]
EqUaTe has quit [charon.oftc.net liquid.oftc.net]
omni has quit [charon.oftc.net liquid.oftc.net]
mva has quit [charon.oftc.net liquid.oftc.net]
hauke has quit [charon.oftc.net liquid.oftc.net]
blogic has quit [charon.oftc.net liquid.oftc.net]
AndyCap has quit [charon.oftc.net liquid.oftc.net]
lemmi has quit [charon.oftc.net liquid.oftc.net]
nbd has quit [charon.oftc.net liquid.oftc.net]
xdarklight has quit [charon.oftc.net liquid.oftc.net]
FLD has quit [charon.oftc.net liquid.oftc.net]
dwmw2 has quit [charon.oftc.net liquid.oftc.net]
kabel has quit [charon.oftc.net liquid.oftc.net]
lynxis has quit [charon.oftc.net liquid.oftc.net]
embargo has quit [charon.oftc.net liquid.oftc.net]
_lore_ has quit [charon.oftc.net liquid.oftc.net]
jlsalvador has joined #openwrt-devel
dwmw2 has joined #openwrt-devel
PaulFertser has joined #openwrt-devel
\x has joined #openwrt-devel
mva has joined #openwrt-devel
zorun has joined #openwrt-devel
t4h4[m] has joined #openwrt-devel
xes has joined #openwrt-devel
EqUaTe has joined #openwrt-devel
nbd has joined #openwrt-devel
YSC has joined #openwrt-devel
_lore_ has joined #openwrt-devel
embargo has joined #openwrt-devel
fieryeagle954[m] has joined #openwrt-devel
omni has joined #openwrt-devel
owrt-1907-builds has joined #openwrt-devel
lynxis has joined #openwrt-devel
kabel has joined #openwrt-devel
hauke has joined #openwrt-devel
lemmi has joined #openwrt-devel
FLD has joined #openwrt-devel
gladiac has joined #openwrt-devel
zatwai has joined #openwrt-devel
AndyCap has joined #openwrt-devel
xdarklight has joined #openwrt-devel
blogic has joined #openwrt-devel
lynxis has quit [Remote host closed the connection]
lynxis has joined #openwrt-devel
owrt-1907-builds has quit [charon.oftc.net liquid.oftc.net]
fieryeagle954[m] has quit [charon.oftc.net liquid.oftc.net]
zatwai has quit [charon.oftc.net liquid.oftc.net]
PaulFertser has quit [charon.oftc.net liquid.oftc.net]
jlsalvador has quit [charon.oftc.net liquid.oftc.net]
YSC has quit [charon.oftc.net liquid.oftc.net]
zorun has quit [charon.oftc.net liquid.oftc.net]
xes has quit [charon.oftc.net liquid.oftc.net]
gladiac has quit [charon.oftc.net liquid.oftc.net]
\x has quit [charon.oftc.net liquid.oftc.net]
EqUaTe has quit [charon.oftc.net liquid.oftc.net]
t4h4[m] has quit [charon.oftc.net liquid.oftc.net]
omni has quit [charon.oftc.net liquid.oftc.net]
xdarklight has quit [charon.oftc.net liquid.oftc.net]
FLD has quit [charon.oftc.net liquid.oftc.net]
nbd has quit [charon.oftc.net liquid.oftc.net]
hauke has quit [charon.oftc.net liquid.oftc.net]
blogic has quit [charon.oftc.net liquid.oftc.net]
dwmw2 has quit [charon.oftc.net liquid.oftc.net]
lemmi has quit [charon.oftc.net liquid.oftc.net]
mva has quit [charon.oftc.net liquid.oftc.net]
AndyCap has quit [charon.oftc.net liquid.oftc.net]
kabel has quit [charon.oftc.net liquid.oftc.net]
_lore_ has quit [charon.oftc.net liquid.oftc.net]
embargo has quit [charon.oftc.net liquid.oftc.net]
_lore_ has joined #openwrt-devel
AndyCap has joined #openwrt-devel
jlsalvador has joined #openwrt-devel
PaulFertser has joined #openwrt-devel
fieryeagle954[m] has joined #openwrt-devel
owrt-1907-builds has joined #openwrt-devel
omni has joined #openwrt-devel
EqUaTe has joined #openwrt-devel
kabel has joined #openwrt-devel
hauke has joined #openwrt-devel
nbd has joined #openwrt-devel
embargo has joined #openwrt-devel
t4h4[m] has joined #openwrt-devel
xes has joined #openwrt-devel
dwmw2 has joined #openwrt-devel
\x has joined #openwrt-devel
YSC has joined #openwrt-devel
mva has joined #openwrt-devel
gladiac has joined #openwrt-devel
zatwai has joined #openwrt-devel
xdarklight has joined #openwrt-devel
zorun has joined #openwrt-devel
blogic has joined #openwrt-devel
lemmi has joined #openwrt-devel
FLD has joined #openwrt-devel
owrt-1907-builds has quit [charon.oftc.net liquid.oftc.net]
zorun has quit [charon.oftc.net liquid.oftc.net]
fieryeagle954[m] has quit [charon.oftc.net liquid.oftc.net]
YSC has quit [charon.oftc.net liquid.oftc.net]
zatwai has quit [charon.oftc.net liquid.oftc.net]
PaulFertser has quit [charon.oftc.net liquid.oftc.net]
jlsalvador has quit [charon.oftc.net liquid.oftc.net]
xes has quit [charon.oftc.net liquid.oftc.net]
gladiac has quit [charon.oftc.net liquid.oftc.net]
t4h4[m] has quit [charon.oftc.net liquid.oftc.net]
\x has quit [charon.oftc.net liquid.oftc.net]
EqUaTe has quit [charon.oftc.net liquid.oftc.net]
omni has quit [charon.oftc.net liquid.oftc.net]
xdarklight has quit [charon.oftc.net liquid.oftc.net]
FLD has quit [charon.oftc.net liquid.oftc.net]
nbd has quit [charon.oftc.net liquid.oftc.net]
lemmi has quit [charon.oftc.net liquid.oftc.net]
mva has quit [charon.oftc.net liquid.oftc.net]
hauke has quit [charon.oftc.net liquid.oftc.net]
blogic has quit [charon.oftc.net liquid.oftc.net]
AndyCap has quit [charon.oftc.net liquid.oftc.net]
dwmw2 has quit [charon.oftc.net liquid.oftc.net]
kabel has quit [charon.oftc.net liquid.oftc.net]
_lore_ has quit [charon.oftc.net liquid.oftc.net]
embargo has quit [charon.oftc.net liquid.oftc.net]
xdarklight has joined #openwrt-devel
dwmw2 has joined #openwrt-devel
PaulFertser has joined #openwrt-devel
YSC has joined #openwrt-devel
jlsalvador has joined #openwrt-devel
nbd has joined #openwrt-devel
zorun has joined #openwrt-devel
omni has joined #openwrt-devel
kabel has joined #openwrt-devel
lemmi has joined #openwrt-devel
hauke has joined #openwrt-devel
blogic has joined #openwrt-devel
gladiac has joined #openwrt-devel
FLD has joined #openwrt-devel
\x has joined #openwrt-devel
AndyCap has joined #openwrt-devel
xes has joined #openwrt-devel
_lore_ has joined #openwrt-devel
zatwai has joined #openwrt-devel
EqUaTe has joined #openwrt-devel
fieryeagle954[m] has joined #openwrt-devel
owrt-1907-builds has joined #openwrt-devel
mva has joined #openwrt-devel
t4h4[m] has joined #openwrt-devel
embargo has joined #openwrt-devel
gladiac1 has joined #openwrt-devel
gladiac is now known as Guest10651
Guest10651 has quit [Write error: connection closed]