Re: OpenWrt 21.02-rc1
On 21-04-21, Perry wrote: > Now that openwrt-21.02-rc1 is tagged, would it be possible to have an > "openwrt-21.02" section for the Reported Version on bugs.openwrt.org? > While at it, why is it still possible to file bug reports for lede-17.01? Good catch, thanks. I have just added openwrt-21.02 to the bug tracker and disabled the possibility to use 17.01 and 18.06 for new bugs. Baptiste signature.asc Description: PGP signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1
On 4/19/21 11:26 PM, Hauke Mehrtens wrote: > On 4/19/21 8:59 AM, Andre Heider wrote: >> On 19/04/2021 08:51, Florian Eckert wrote: >>> Hello, >>> >>>> If there are some other bugs in the 21.02 branch which are fixed in >>>> master, we can backport the fixed as long as they are not so big. If >>>> there is something missing, just ask on the mainling list. >>> >>> Since last weekend the following patch was merged into master. >>> The patch extends ltq-vdsl ubus interface with the missing state_num >>> and power_state_num values. >>> https://github.com/openwrt/openwrt/commit/4407d45d9667ab3d376ad4a6b760e07f4dd43e49#diff-ff00a3f4f318bb11684e008813bd876f0865ce6c2c681ec26b0bf178b4e83163 >>> >>> >>> Could we please backport this to the branch openwrt-21.02 before rc1 >>> stable release? >> >> Let's get these two patches in too: >> >> 48162e4c0c85a7f64d9007565bf5be2c7ace3ada lantiq: enable G.INP >> retransmission counters >> 4f27ea7c33447f4b0c8e577509726927916b9625 lantiq: use ActualNetDataRate >> for speed reporting >> >> With those 3 patches 21.02 matches master with the big ubus dsl metric >> change. > > I added these 3 patches, but only after tagging. > > We should do a 21.02.0-rc2 in 2 to 3 weeks anyway. > > Hauke > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > . Now that openwrt-21.02-rc1 is tagged, would it be possible to have an "openwrt-21.02" section for the Reported Version on bugs.openwrt.org? While at it, why is it still possible to file bug reports for lede-17.01? Perry ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1
On 19/04/2021 23:26, Hauke Mehrtens wrote: On 4/19/21 8:59 AM, Andre Heider wrote: On 19/04/2021 08:51, Florian Eckert wrote: Hello, If there are some other bugs in the 21.02 branch which are fixed in master, we can backport the fixed as long as they are not so big. If there is something missing, just ask on the mainling list. Since last weekend the following patch was merged into master. The patch extends ltq-vdsl ubus interface with the missing state_num and power_state_num values. https://github.com/openwrt/openwrt/commit/4407d45d9667ab3d376ad4a6b760e07f4dd43e49#diff-ff00a3f4f318bb11684e008813bd876f0865ce6c2c681ec26b0bf178b4e83163 Could we please backport this to the branch openwrt-21.02 before rc1 stable release? Let's get these two patches in too: 48162e4c0c85a7f64d9007565bf5be2c7ace3ada lantiq: enable G.INP retransmission counters 4f27ea7c33447f4b0c8e577509726927916b9625 lantiq: use ActualNetDataRate for speed reporting With those 3 patches 21.02 matches master with the big ubus dsl metric change. I added these 3 patches, but only after tagging. We should do a 21.02.0-rc2 in 2 to 3 weeks anyway. Nice, thanks! ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1
On 4/19/21 8:59 AM, Andre Heider wrote: On 19/04/2021 08:51, Florian Eckert wrote: Hello, If there are some other bugs in the 21.02 branch which are fixed in master, we can backport the fixed as long as they are not so big. If there is something missing, just ask on the mainling list. Since last weekend the following patch was merged into master. The patch extends ltq-vdsl ubus interface with the missing state_num and power_state_num values. https://github.com/openwrt/openwrt/commit/4407d45d9667ab3d376ad4a6b760e07f4dd43e49#diff-ff00a3f4f318bb11684e008813bd876f0865ce6c2c681ec26b0bf178b4e83163 Could we please backport this to the branch openwrt-21.02 before rc1 stable release? Let's get these two patches in too: 48162e4c0c85a7f64d9007565bf5be2c7ace3ada lantiq: enable G.INP retransmission counters 4f27ea7c33447f4b0c8e577509726927916b9625 lantiq: use ActualNetDataRate for speed reporting With those 3 patches 21.02 matches master with the big ubus dsl metric change. I added these 3 patches, but only after tagging. We should do a 21.02.0-rc2 in 2 to 3 weeks anyway. Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1
On 4/18/21 3:11 PM, Hauke Mehrtens wrote: > On 4/7/21 12:29 AM, Hauke Mehrtens wrote: >> Hi, >> >> How do we want to go forward with OpenWrt 21.02-rc1? >> >> * I think the base system is ok. >> * The http (original wolfssl) problem reported by jow is fixed >> * LuCI in the 21.02 branch still misses DSA support, this was merged >> into master some time ago as far as I understood. >> >> Jow reported this end of March: >>> I found some serious regressions in the luci device config support. >>> not sure yet how long it'll take to sort out. The netifd uci config >>> grew so complex that it'll take a while to try all cases >>> * changing interface settings after previously enabling certain >>> options results in a brick >>> * wireless networks with custom ifnames are improperly bridged >>> * option ipv6 for ppp based protocols is broken because it clashes >>> with option ipv6 in device sections >> >> I would like to merge this update of iproute2 if Russel is fine with >> it, but I do not see this blocking 21.02-rc1: >> https://github.com/openwrt/openwrt/pull/4025 >> >> If there are some other bugs in the 21.02 branch which are fixed in >> master, we can backport the fixed as long as they are not so big. If >> there is something missing, just ask on the mainling list. >> >> In would like to get 21.02-rc1 soon, so more users start testing it >> and we get more bug reports. >> >> How should we continue? >> 1. Tag 21.02-rc1 and do the release in the next days with the current >> state. >> >> 2. Merge the LuCI DSA changes from master to 21.02 branch now and do >> 21.02-rc1 ~3 days to see if some big problems come up. >> >> 3. Wait till the problems reported by jow are fixed and do the 21.02-rc1 >> them. >> >> 4. Wait an other 2 weeks and see how it looks them. >> >> >> I would prefer if we merge the LuCI DSA changes from master to 21.02 >> branch now and do 21.02-rc1 soon. We should list the problems as known >> problems. >> >> It would be nice if someone else could also look into these problems >> and propose fixes. >> >> Hauke >> >> ___ >> openwrt-devel mailing list >> openwrt-devel@lists.openwrt.org >> https://lists.openwrt.org/mailman/listinfo/openwrt-devel > > Hi, > > I backported the changes which were requested and went tough the master > logs and backported some more fixes to 21.02. If something more is > needed please send a mail to the mailing list. I submitted a PR to fix a bug in qos-scripts in the 21.02 and master branches. It would be nice if this finds it's was into rc1 as well. https://github.com/openwrt/openwrt/pull/4092 Greets, Perry > > I would like to tag OpenWrt 21.02-rc1 on tomorrow Monday evening, > without the LuCI DSA support if it does not get merged before. > > Any objections to this plan? > > Hauke > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1
I don't object rc1 now that as there is a bug in the dsa driver that causes probable memory corruption, rc2 should have dsa though, I don't think it will take too long for it to get fixed and merged to the dsa patch and after that we haven't found any issues blocking a merge I think. On Sun, Apr 18, 2021 at 4:15 PM Hauke Mehrtens wrote: > > On 4/7/21 12:29 AM, Hauke Mehrtens wrote: > > Hi, > > > > How do we want to go forward with OpenWrt 21.02-rc1? > > > > * I think the base system is ok. > > * The http (original wolfssl) problem reported by jow is fixed > > * LuCI in the 21.02 branch still misses DSA support, this was merged > > into master some time ago as far as I understood. > > > > Jow reported this end of March: > >> I found some serious regressions in the luci device config support. > >> not sure yet how long it'll take to sort out. The netifd uci config > >> grew so complex that it'll take a while to try all cases > >> * changing interface settings after previously enabling certain > >> options results in a brick > >> * wireless networks with custom ifnames are improperly bridged > >> * option ipv6 for ppp based protocols is broken because it clashes > >> with option ipv6 in device sections > > > > I would like to merge this update of iproute2 if Russel is fine with it, > > but I do not see this blocking 21.02-rc1: > > https://github.com/openwrt/openwrt/pull/4025 > > > > If there are some other bugs in the 21.02 branch which are fixed in > > master, we can backport the fixed as long as they are not so big. If > > there is something missing, just ask on the mainling list. > > > > In would like to get 21.02-rc1 soon, so more users start testing it and > > we get more bug reports. > > > > How should we continue? > > 1. Tag 21.02-rc1 and do the release in the next days with the current > >state. > > > > 2. Merge the LuCI DSA changes from master to 21.02 branch now and do > >21.02-rc1 ~3 days to see if some big problems come up. > > > > 3. Wait till the problems reported by jow are fixed and do the 21.02-rc1 > >them. > > > > 4. Wait an other 2 weeks and see how it looks them. > > > > > > I would prefer if we merge the LuCI DSA changes from master to 21.02 > > branch now and do 21.02-rc1 soon. We should list the problems as known > > problems. > > > > It would be nice if someone else could also look into these problems and > > propose fixes. > > > > Hauke > > > > ___ > > openwrt-devel mailing list > > openwrt-devel@lists.openwrt.org > > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > > Hi, > > I backported the changes which were requested and went tough the master > logs and backported some more fixes to 21.02. If something more is > needed please send a mail to the mailing list. > > I would like to tag OpenWrt 21.02-rc1 on tomorrow Monday evening, > without the LuCI DSA support if it does not get merged before. > > Any objections to this plan? > > Hauke > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1
On 19/04/2021 08:51, Florian Eckert wrote: Hello, If there are some other bugs in the 21.02 branch which are fixed in master, we can backport the fixed as long as they are not so big. If there is something missing, just ask on the mainling list. Since last weekend the following patch was merged into master. The patch extends ltq-vdsl ubus interface with the missing state_num and power_state_num values. https://github.com/openwrt/openwrt/commit/4407d45d9667ab3d376ad4a6b760e07f4dd43e49#diff-ff00a3f4f318bb11684e008813bd876f0865ce6c2c681ec26b0bf178b4e83163 Could we please backport this to the branch openwrt-21.02 before rc1 stable release? Let's get these two patches in too: 48162e4c0c85a7f64d9007565bf5be2c7ace3ada lantiq: enable G.INP retransmission counters 4f27ea7c33447f4b0c8e577509726927916b9625 lantiq: use ActualNetDataRate for speed reporting With those 3 patches 21.02 matches master with the big ubus dsl metric change. Thanks, Andre ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1
Hello, If there are some other bugs in the 21.02 branch which are fixed in master, we can backport the fixed as long as they are not so big. If there is something missing, just ask on the mainling list. Since last weekend the following patch was merged into master. The patch extends ltq-vdsl ubus interface with the missing state_num and power_state_num values. https://github.com/openwrt/openwrt/commit/4407d45d9667ab3d376ad4a6b760e07f4dd43e49#diff-ff00a3f4f318bb11684e008813bd876f0865ce6c2c681ec26b0bf178b4e83163 Could we please backport this to the branch openwrt-21.02 before rc1 stable release? Thanks Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
RE: OpenWrt 21.02-rc1
> -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > On Behalf Of Hauke Mehrtens > Sent: Sonntag, 18. April 2021 15:12 > To: OpenWrt Development List > Cc: Jo-Philipp Wich > Subject: Re: OpenWrt 21.02-rc1 > > On 4/7/21 12:29 AM, Hauke Mehrtens wrote: > > Hi, > > > > How do we want to go forward with OpenWrt 21.02-rc1? > > > > * I think the base system is ok. > > * The http (original wolfssl) problem reported by jow is fixed > > * LuCI in the 21.02 branch still misses DSA support, this was merged > > into master some time ago as far as I understood. > > > > Jow reported this end of March: > >> I found some serious regressions in the luci device config support. > >> not sure yet how long it'll take to sort out. The netifd uci config > >> grew so complex that it'll take a while to try all cases > >> * changing interface settings after previously enabling certain > >> options results in a brick > >> * wireless networks with custom ifnames are improperly bridged > >> * option ipv6 for ppp based protocols is broken because it clashes > >> with option ipv6 in device sections > > > > I would like to merge this update of iproute2 if Russel is fine with > > it, but I do not see this blocking 21.02-rc1: > > https://github.com/openwrt/openwrt/pull/4025 > > > > If there are some other bugs in the 21.02 branch which are fixed in > > master, we can backport the fixed as long as they are not so big. If > > there is something missing, just ask on the mainling list. > > > > In would like to get 21.02-rc1 soon, so more users start testing it > > and we get more bug reports. > > > > How should we continue? > > 1. Tag 21.02-rc1 and do the release in the next days with the current > > state. > > > > 2. Merge the LuCI DSA changes from master to 21.02 branch now and do > > 21.02-rc1 ~3 days to see if some big problems come up. > > > > 3. Wait till the problems reported by jow are fixed and do the > > 21.02-rc1 > > them. > > > > 4. Wait an other 2 weeks and see how it looks them. > > > > > > I would prefer if we merge the LuCI DSA changes from master to 21.02 > > branch now and do 21.02-rc1 soon. We should list the problems as known > > problems. > > > > It would be nice if someone else could also look into these problems > > and propose fixes. > > > > Hauke > > > > ___________ > > openwrt-devel mailing list > > openwrt-devel@lists.openwrt.org > > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > > Hi, > > I backported the changes which were requested and went tough the master > logs and backported some more fixes to 21.02. If something more is needed > please send a mail to the mailing list. > > I would like to tag OpenWrt 21.02-rc1 on tomorrow Monday evening, without > the LuCI DSA support if it does not get merged before. > > Any objections to this plan? > > Hauke No objections, thanks for taking care! :-) Best Adrian > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel openpgp-digital-signature.asc Description: PGP signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1
On 4/7/21 12:29 AM, Hauke Mehrtens wrote: Hi, How do we want to go forward with OpenWrt 21.02-rc1? * I think the base system is ok. * The http (original wolfssl) problem reported by jow is fixed * LuCI in the 21.02 branch still misses DSA support, this was merged into master some time ago as far as I understood. Jow reported this end of March: I found some serious regressions in the luci device config support. not sure yet how long it'll take to sort out. The netifd uci config grew so complex that it'll take a while to try all cases * changing interface settings after previously enabling certain options results in a brick * wireless networks with custom ifnames are improperly bridged * option ipv6 for ppp based protocols is broken because it clashes with option ipv6 in device sections I would like to merge this update of iproute2 if Russel is fine with it, but I do not see this blocking 21.02-rc1: https://github.com/openwrt/openwrt/pull/4025 If there are some other bugs in the 21.02 branch which are fixed in master, we can backport the fixed as long as they are not so big. If there is something missing, just ask on the mainling list. In would like to get 21.02-rc1 soon, so more users start testing it and we get more bug reports. How should we continue? 1. Tag 21.02-rc1 and do the release in the next days with the current state. 2. Merge the LuCI DSA changes from master to 21.02 branch now and do 21.02-rc1 ~3 days to see if some big problems come up. 3. Wait till the problems reported by jow are fixed and do the 21.02-rc1 them. 4. Wait an other 2 weeks and see how it looks them. I would prefer if we merge the LuCI DSA changes from master to 21.02 branch now and do 21.02-rc1 soon. We should list the problems as known problems. It would be nice if someone else could also look into these problems and propose fixes. Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel Hi, I backported the changes which were requested and went tough the master logs and backported some more fixes to 21.02. If something more is needed please send a mail to the mailing list. I would like to tag OpenWrt 21.02-rc1 on tomorrow Monday evening, without the LuCI DSA support if it does not get merged before. Any objections to this plan? Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1
On 08/04/2021 11:14, Mauro Mozzarelli wrote: 2) dsl_control [status|lucistat] was changed with dsl reporting removed https://forum.openwrt.org/t/openwrt-21-02-dsl-control/89962/22 I understand the reason behind this change. I had to write my own command line reporting and adapt batch data collection and router connectivity keepalive scripts that previously depended on dsl_control, but users who have dependencies on these removed command line features are likely to be impacted. My recommendation is that it should be documented (there is no documentation right now). I wonder why backward compatibility was not considered as it would not be difficult to reproduce "status" and "lucistat" functionality. Going by that forum post, I'm that "genius". Ignoring your misplaced tone, it's the same as with most open source projects: upstream you stuff or expect breakage if you rely on internal data. Consumers of these metrics that *are* upstream (luci and prometheus at the time) were adopted to the new ubus metrics, so there is no breakage. Sometimes things need to evolve. And if they do, there's no way to fix or even know about downstream users. If you've got something that's valuable to other users, it's in your interest to upstream it so you won't run into this again. On the other hand, I too use various patches that aren't suitable for upstream. That's on me and I need to adapt those every now and then if things change. But I don't get the right to complain if things change. Cheers, Andre ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1
Hi guys, On 08. 04. 21 11:14, Mauro Mozzarelli wrote: > Hauke, > > I have been using 21.02 for the last 4 weeks and I found 2 importants issues: > > 1) OpenVPN up/down: > https://forum.openwrt.org/t/openwrt-21-02-openvpn-client-up-down-scripts-configuration-ignored/91126 > There are proposed fixes, but I have not seen these yet in the latest 21.02 > branch. > I question the value of the change introduced for openvpn hotplug, which is > un-necessary given the existing native up/down options. The change introduces > additional complexity, cost of maintenance (technical debt) and new possible > points of failure just to reproduce an existing native openvpn function. The > value added is therefore unclear. I would remove it altogether. Yesterday, maintainer of OpenVPN package created PR against OpenWrt 21.02 branch [1], where he cherry-picked commits from master, which fixes the issue, which you are mention and in the same day, it was merged. It should be in a few hours if not already present in OpenWrt 21.02. [1] https://github.com/openwrt/packages/pull/15363 Regards, Josef > > 2) dsl_control [status|lucistat] was changed with dsl reporting removed > https://forum.openwrt.org/t/openwrt-21-02-dsl-control/89962/22 > I understand the reason behind this change. I had to write my own command > line reporting and adapt batch data collection and router connectivity > keepalive scripts that previously depended on dsl_control, but users who have > dependencies on these removed command line features are likely to be > impacted. My recommendation is that it should be documented (there is no > documentation right now). > I wonder why backward compatibility was not considered as it would not be > difficult to reproduce "status" and "lucistat" functionality. > > > On 06/04/2021, 23:37, "openwrt-devel on behalf of Hauke Mehrtens" > wrote: > > Hi, > > How do we want to go forward with OpenWrt 21.02-rc1? > > * I think the base system is ok. > * The http (original wolfssl) problem reported by jow is fixed > * LuCI in the 21.02 branch still misses DSA support, this was merged > into master some time ago as far as I understood. > > Jow reported this end of March: > > I found some serious regressions in the luci device config support. > > not sure yet how long it'll take to sort out. The netifd uci config > > grew so complex that it'll take a while to try all cases > > * changing interface settings after previously enabling certain > > options results in a brick > > * wireless networks with custom ifnames are improperly bridged > > * option ipv6 for ppp based protocols is broken because it clashes > > with option ipv6 in device sections > > I would like to merge this update of iproute2 if Russel is fine with it, > but I do not see this blocking 21.02-rc1: > https://github.com/openwrt/openwrt/pull/4025 > > If there are some other bugs in the 21.02 branch which are fixed in > master, we can backport the fixed as long as they are not so big. If > there is something missing, just ask on the mainling list. > > In would like to get 21.02-rc1 soon, so more users start testing it and > we get more bug reports. > > How should we continue? > 1. Tag 21.02-rc1 and do the release in the next days with the current > state. > > 2. Merge the LuCI DSA changes from master to 21.02 branch now and do > 21.02-rc1 ~3 days to see if some big problems come up. > > 3. Wait till the problems reported by jow are fixed and do the 21.02-rc1 > them. > > 4. Wait an other 2 weeks and see how it looks them. > > > I would prefer if we merge the LuCI DSA changes from master to 21.02 > branch now and do 21.02-rc1 soon. We should list the problems as known > problems. > > It would be nice if someone else could also look into these problems and > propose fixes. > > Hauke > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > > OpenPGP_signature Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1
Hauke, I have been using 21.02 for the last 4 weeks and I found 2 importants issues: 1) OpenVPN up/down: https://forum.openwrt.org/t/openwrt-21-02-openvpn-client-up-down-scripts-configuration-ignored/91126 There are proposed fixes, but I have not seen these yet in the latest 21.02 branch. I question the value of the change introduced for openvpn hotplug, which is un-necessary given the existing native up/down options. The change introduces additional complexity, cost of maintenance (technical debt) and new possible points of failure just to reproduce an existing native openvpn function. The value added is therefore unclear. I would remove it altogether. 2) dsl_control [status|lucistat] was changed with dsl reporting removed https://forum.openwrt.org/t/openwrt-21-02-dsl-control/89962/22 I understand the reason behind this change. I had to write my own command line reporting and adapt batch data collection and router connectivity keepalive scripts that previously depended on dsl_control, but users who have dependencies on these removed command line features are likely to be impacted. My recommendation is that it should be documented (there is no documentation right now). I wonder why backward compatibility was not considered as it would not be difficult to reproduce "status" and "lucistat" functionality. On 06/04/2021, 23:37, "openwrt-devel on behalf of Hauke Mehrtens" wrote: Hi, How do we want to go forward with OpenWrt 21.02-rc1? * I think the base system is ok. * The http (original wolfssl) problem reported by jow is fixed * LuCI in the 21.02 branch still misses DSA support, this was merged into master some time ago as far as I understood. Jow reported this end of March: > I found some serious regressions in the luci device config support. > not sure yet how long it'll take to sort out. The netifd uci config > grew so complex that it'll take a while to try all cases > * changing interface settings after previously enabling certain > options results in a brick > * wireless networks with custom ifnames are improperly bridged > * option ipv6 for ppp based protocols is broken because it clashes > with option ipv6 in device sections I would like to merge this update of iproute2 if Russel is fine with it, but I do not see this blocking 21.02-rc1: https://github.com/openwrt/openwrt/pull/4025 If there are some other bugs in the 21.02 branch which are fixed in master, we can backport the fixed as long as they are not so big. If there is something missing, just ask on the mainling list. In would like to get 21.02-rc1 soon, so more users start testing it and we get more bug reports. How should we continue? 1. Tag 21.02-rc1 and do the release in the next days with the current state. 2. Merge the LuCI DSA changes from master to 21.02 branch now and do 21.02-rc1 ~3 days to see if some big problems come up. 3. Wait till the problems reported by jow are fixed and do the 21.02-rc1 them. 4. Wait an other 2 weeks and see how it looks them. I would prefer if we merge the LuCI DSA changes from master to 21.02 branch now and do 21.02-rc1 soon. We should list the problems as known problems. It would be nice if someone else could also look into these problems and propose fixes. Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- On 2021-04-07 20:07, John Crispin wrote: On 07.04.21 12:16, Bas Mevissen via openwrt-devel wrote: Will Wifi 6 support be added to the interface? We have some support for a couple of AX routers, so it would be nice if they can work without manually tweaking things. The underlying structure seems to support it already: https://forum.openwrt.org/t/got-802-11ax-working-in-linksys-e8450/91533 I have a couple of patches pending that I will post the next few days that will make the primary HE features work on 21.02. I converged my home to 3xe8450 Good to hear. I've an X5000R waiting to be converted to OpenWRT. The E8450 or RT3200 would have been a better choice, but at the time I wanted to order a supported AX router, it was only the X5000R or the UniFi 6 Lite to choose from. The X5000R unfortunately cannot max out the Killer Wifi card in my notebook, but it still makes around 800Mbit/s with iperf3 though. Bas. John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel --- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1 - realtek and mediatek targets
Hi, Op donderdag 8 april 2021 om 8u35 schreef Bjørn Mork : Stijn Segers writes: A vote for keeping the realtek target here, I have three devices here in production. Very happy with them. The main catch I see with relegating the realtek target to master would be less uptake on the end user side (not everyone will want to run hardware that needs OpenWrt master), but I am unqualified to judge the code quality. All I can say is it runs nicely here (including PoE). I agree. The feature set of the realtek target is pretty complete, and the anticipated fast movement of the target in master has not happened yet. So please keep realtek for 21.02. There is one pending series applicable to realtek which I had hoped to get in before exposing the target to innocent users, but this might be too late by now?: https://patchwork.ozlabs.org/project/openwrt/list/?series=237587 Being able to adjust the "bootpartition" variable is crucial to support console-less installation IMHO. Which makes the target more accessible to non-developers. I see Petr just merged them into master (thanks!). I'll be sending in a few fixes that depend on them too, would be good if they could make it into 21.02 as well. Cheers Stijn Bjørn ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1 - realtek and mediatek targets
Stijn Segers writes: > A vote for keeping the realtek target here, I have three devices here > in production. Very happy with them. The main catch I see with > relegating the realtek target to master would be less uptake on the > end user side (not everyone will want to run hardware that needs > OpenWrt master), but I am unqualified to judge the code quality. > > All I can say is it runs nicely here (including PoE). I agree. The feature set of the realtek target is pretty complete, and the anticipated fast movement of the target in master has not happened yet. So please keep realtek for 21.02. There is one pending series applicable to realtek which I had hoped to get in before exposing the target to innocent users, but this might be too late by now?: https://patchwork.ozlabs.org/project/openwrt/list/?series=237587 Being able to adjust the "bootpartition" variable is crucial to support console-less installation IMHO. Which makes the target more accessible to non-developers. Bjørn ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1 - realtek and mediatek targets
Hi, Do we want to keep the realtek and mediatek targets in the 21.02 branch and release or do we want to remove them link the ipq807x target? Hauke keep them for sure. I am running my network on those 2 targets using 21.02 John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1 - realtek and mediatek targets
Hi Hauke, Op woensdag 7 april 2021 om 22u27 schreef Hauke Mehrtens : On 4/7/21 12:29 AM, Hauke Mehrtens wrote: Hi, How do we want to go forward with OpenWrt 21.02-rc1? * I think the base system is ok. * The http (original wolfssl) problem reported by jow is fixed * LuCI in the 21.02 branch still misses DSA support, this was merged into master some time ago as far as I understood. Jow reported this end of March: I found some serious regressions in the luci device config support. not sure yet how long it'll take to sort out. The netifd uci config grew so complex that it'll take a while to try all cases * changing interface settings after previously enabling certain options results in a brick * wireless networks with custom ifnames are improperly bridged * option ipv6 for ppp based protocols is broken because it clashes with option ipv6 in device sections I would like to merge this update of iproute2 if Russel is fine with it, but I do not see this blocking 21.02-rc1: https://github.com/openwrt/openwrt/pull/4025 If there are some other bugs in the 21.02 branch which are fixed in master, we can backport the fixed as long as they are not so big. If there is something missing, just ask on the mainling list. In would like to get 21.02-rc1 soon, so more users start testing it and we get more bug reports. How should we continue? 1. Tag 21.02-rc1 and do the release in the next days with the current state. 2. Merge the LuCI DSA changes from master to 21.02 branch now and do 21.02-rc1 ~3 days to see if some big problems come up. 3. Wait till the problems reported by jow are fixed and do the 21.02-rc1 them. 4. Wait an other 2 weeks and see how it looks them. I would prefer if we merge the LuCI DSA changes from master to 21.02 branch now and do 21.02-rc1 soon. We should list the problems as known problems. It would be nice if someone else could also look into these problems and propose fixes. Hauke Hi, Do we want to keep the realtek and mediatek targets in the 21.02 branch and release or do we want to remove them link the ipq807x target? A vote for keeping the realtek target here, I have three devices here in production. Very happy with them. The main catch I see with relegating the realtek target to master would be less uptake on the end user side (not everyone will want to run hardware that needs OpenWrt master), but I am unqualified to judge the code quality. All I can say is it runs nicely here (including PoE). Cheers Stijn Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1 (backport request, WireGuard, DSA roaming, iproute2 5.11)
Hi Hauke, Op woensdag 7 april 2021 om 23u58 schreef Hauke Mehrtens : On 4/7/21 12:29 AM, Hauke Mehrtens wrote: Hi, How do we want to go forward with OpenWrt 21.02-rc1? * I think the base system is ok. * The http (original wolfssl) problem reported by jow is fixed * LuCI in the 21.02 branch still misses DSA support, this was merged into master some time ago as far as I understood. Jow reported this end of March: I found some serious regressions in the luci device config support. not sure yet how long it'll take to sort out. The netifd uci config grew so complex that it'll take a while to try all cases * changing interface settings after previously enabling certain options results in a brick * wireless networks with custom ifnames are improperly bridged * option ipv6 for ppp based protocols is broken because it clashes with option ipv6 in device sections I would like to merge this update of iproute2 if Russel is fine with it, but I do not see this blocking 21.02-rc1: https://github.com/openwrt/openwrt/pull/4025 If there are some other bugs in the 21.02 branch which are fixed in master, we can backport the fixed as long as they are not so big. If there is something missing, just ask on the mainling list. In would like to get 21.02-rc1 soon, so more users start testing it and we get more bug reports. How should we continue? 1. Tag 21.02-rc1 and do the release in the next days with the current state. 2. Merge the LuCI DSA changes from master to 21.02 branch now and do 21.02-rc1 ~3 days to see if some big problems come up. 3. Wait till the problems reported by jow are fixed and do the 21.02-rc1 them. 4. Wait an other 2 weeks and see how it looks them. I would prefer if we merge the LuCI DSA changes from master to 21.02 branch now and do 21.02-rc1 soon. We should list the problems as known problems. It would be nice if someone else could also look into these problems and propose fixes. Hauke Hi, There are requests for some pretty big changes to get merged into 21.02: Bring WireGuard in-tree for 21.02 #3960 https://github.com/openwrt/openwrt/pull/3960 Adding 63482 lines, mostly backported kernel patches. kernel: DSA roaming fix for Marvell mv88e6xxx https://git.openwrt.org/920eaab1d8179035d0ae1047e75cf9a50da6a6eb Adding 1180 lines of kernel patches build: make sure asm gets built with -DPIC https://git.openwrt.org/af22991e03cae55f96b06996df2ff16752cec5d5 iproute2: backport 5.11 update and improvements, related NLS fixes #4025 https://github.com/openwrt/openwrt/pull/4025 multiple patches for packages Are there any objections to backporting these changes? If no one complains I will merge them into 21.02 in on Friday. Thanks for getting the RC going. I have been running the WireGuard PR on 21.02 for a few weeks now, no issues here. Same for the iproute2 PR but I have done no specific testing on it (just running pretty default configs on DSA devices). No complaints about that PR either. Cheers Stijn Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1 (backport request, WireGuard, DSA roaming, iproute2 5.11)
On 4/7/21 12:29 AM, Hauke Mehrtens wrote: Hi, How do we want to go forward with OpenWrt 21.02-rc1? * I think the base system is ok. * The http (original wolfssl) problem reported by jow is fixed * LuCI in the 21.02 branch still misses DSA support, this was merged into master some time ago as far as I understood. Jow reported this end of March: I found some serious regressions in the luci device config support. not sure yet how long it'll take to sort out. The netifd uci config grew so complex that it'll take a while to try all cases * changing interface settings after previously enabling certain options results in a brick * wireless networks with custom ifnames are improperly bridged * option ipv6 for ppp based protocols is broken because it clashes with option ipv6 in device sections I would like to merge this update of iproute2 if Russel is fine with it, but I do not see this blocking 21.02-rc1: https://github.com/openwrt/openwrt/pull/4025 If there are some other bugs in the 21.02 branch which are fixed in master, we can backport the fixed as long as they are not so big. If there is something missing, just ask on the mainling list. In would like to get 21.02-rc1 soon, so more users start testing it and we get more bug reports. How should we continue? 1. Tag 21.02-rc1 and do the release in the next days with the current state. 2. Merge the LuCI DSA changes from master to 21.02 branch now and do 21.02-rc1 ~3 days to see if some big problems come up. 3. Wait till the problems reported by jow are fixed and do the 21.02-rc1 them. 4. Wait an other 2 weeks and see how it looks them. I would prefer if we merge the LuCI DSA changes from master to 21.02 branch now and do 21.02-rc1 soon. We should list the problems as known problems. It would be nice if someone else could also look into these problems and propose fixes. Hauke Hi, There are requests for some pretty big changes to get merged into 21.02: Bring WireGuard in-tree for 21.02 #3960 https://github.com/openwrt/openwrt/pull/3960 Adding 63482 lines, mostly backported kernel patches. kernel: DSA roaming fix for Marvell mv88e6xxx https://git.openwrt.org/920eaab1d8179035d0ae1047e75cf9a50da6a6eb Adding 1180 lines of kernel patches build: make sure asm gets built with -DPIC https://git.openwrt.org/af22991e03cae55f96b06996df2ff16752cec5d5 iproute2: backport 5.11 update and improvements, related NLS fixes #4025 https://github.com/openwrt/openwrt/pull/4025 multiple patches for packages Are there any objections to backporting these changes? If no one complains I will merge them into 21.02 in on Friday. Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1 (backport request, WireGuard, DSA roaming, iproute2 5.11)
Re:WireGuard - fine by me. Thanks for doing that. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1 - realtek and mediatek targets
On 4/7/21 12:29 AM, Hauke Mehrtens wrote: Hi, How do we want to go forward with OpenWrt 21.02-rc1? * I think the base system is ok. * The http (original wolfssl) problem reported by jow is fixed * LuCI in the 21.02 branch still misses DSA support, this was merged into master some time ago as far as I understood. Jow reported this end of March: I found some serious regressions in the luci device config support. not sure yet how long it'll take to sort out. The netifd uci config grew so complex that it'll take a while to try all cases * changing interface settings after previously enabling certain options results in a brick * wireless networks with custom ifnames are improperly bridged * option ipv6 for ppp based protocols is broken because it clashes with option ipv6 in device sections I would like to merge this update of iproute2 if Russel is fine with it, but I do not see this blocking 21.02-rc1: https://github.com/openwrt/openwrt/pull/4025 If there are some other bugs in the 21.02 branch which are fixed in master, we can backport the fixed as long as they are not so big. If there is something missing, just ask on the mainling list. In would like to get 21.02-rc1 soon, so more users start testing it and we get more bug reports. How should we continue? 1. Tag 21.02-rc1 and do the release in the next days with the current state. 2. Merge the LuCI DSA changes from master to 21.02 branch now and do 21.02-rc1 ~3 days to see if some big problems come up. 3. Wait till the problems reported by jow are fixed and do the 21.02-rc1 them. 4. Wait an other 2 weeks and see how it looks them. I would prefer if we merge the LuCI DSA changes from master to 21.02 branch now and do 21.02-rc1 soon. We should list the problems as known problems. It would be nice if someone else could also look into these problems and propose fixes. Hauke Hi, Do we want to keep the realtek and mediatek targets in the 21.02 branch and release or do we want to remove them link the ipq807x target? Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1
On Tue, Apr 6, 2021 at 3:43 PM Hauke Mehrtens wrote: > > [snip] > > If there are some other bugs in the 21.02 branch which are fixed in > master, we can backport the fixed as long as they are not so big. If > there is something missing, just ask on the mainling list. > Hi! I have a oneliner fix for ZyXEL Keenetic Lite rev.B on the GitHub. [0] It would be an average LZMA ERROR 1 fix in the ramips target, but the device's support commit landed on 8 Jul 2020. [1] 21.02 would be it's first release, but it's already unusable due to the LZMA ERROR 1. Please land the fix on master and backport it to the 21.02 release! Thank you, Szabolcs [0]: https://github.com/openwrt/openwrt/pull/3834 [1]: https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=4dc9ad4af8c921494d20b303b6772fc6b5af3a69 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1
On 07.04.21 12:16, Bas Mevissen via openwrt-devel wrote: Will Wifi 6 support be added to the interface? We have some support for a couple of AX routers, so it would be nice if they can work without manually tweaking things. The underlying structure seems to support it already: https://forum.openwrt.org/t/got-802-11ax-working-in-linksys-e8450/91533 I have a couple of patches pending that I will post the next few days that will make the primary HE features work on 21.02. I converged my home to 3xe8450 John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1
On Tue, Apr 6, 2021 at 7:30 PM Hauke Mehrtens wrote: > > Hi, > > How do we want to go forward with OpenWrt 21.02-rc1? > > * I think the base system is ok. > * The http (original wolfssl) problem reported by jow is fixed > * LuCI in the 21.02 branch still misses DSA support, this was merged > into master some time ago as far as I understood. Hi I would suggest to have some commits cherry-picked to 21.02: 920eaab1d8 kernel: DSA roaming fix for Marvell mv88e6xxx af22991e03 build: make sure asm gets built with -DPIC I consider the first commit critical: without it clients get disconnected for 5 minutes when roaming from an affected AP (Omnia, WRT3200, among others) WLAN port to a LAN port (roaming between LAN-connected APs, for example). The second one is needed to build strongswan for x86_64 [1]. The support commits have already been pushed to the 21.02 branch of the packages feed. Eneas [1] https://downloads.openwrt.org/releases/faillogs-21.02/x86_64/packages/strongswan/compile.txt ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1
On 2021-04-07 12:01, Hannu Nyman wrote: Hauke Mehrtens kirjoitti 7.4.2021 klo 1.29: Hi, How do we want to go forward with OpenWrt 21.02-rc1? * I think the base system is ok. * The http (original wolfssl) problem reported by jow is fixed * LuCI in the 21.02 branch still misses DSA support, this was merged into master some time ago as far as I understood. ... In would like to get 21.02-rc1 soon, so more users start testing it and we get more bug reports. How should we continue? 1. Tag 21.02-rc1 and do the release in the next days with the current state. 2. Merge the LuCI DSA changes from master to 21.02 branch now and do 21.02-rc1 ~3 days to see if some big problems come up. Option 2 of merging the LuCI DSA changes and then making the first 21.02-rc sounds good to me. I would also prefer option 2, as I would like to switch to DSA with 21.02. Also the option 1 of doing the rc now would likely be ok, as the only a few targets actually use DSA, so the absence of LuCI support for DSA does not concern that many users. I would prefer if we merge the LuCI DSA changes from master to 21.02 branch now and do 21.02-rc1 soon. We should list the problems as known problems. It would be nice if someone else could also look into these problems and propose fixes. Like with previous releases, the developers interest mainly stays on the master, and not much happens in the new release branch... It is now 50 days since the 21.02 was branched in February, so a high time to get the rc out. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- On 4/7/21 12:29 AM, Hauke Mehrtens wrote: Hi, How do we want to go forward with OpenWrt 21.02-rc1? * I think the base system is ok. * The http (original wolfssl) problem reported by jow is fixed * LuCI in the 21.02 branch still misses DSA support, this was merged into master some time ago as far as I understood. Jow reported this end of March: > I found some serious regressions in the luci device config support. > not sure yet how long it'll take to sort out. The netifd uci config > grew so complex that it'll take a while to try all cases > * changing interface settings after previously enabling certain > options results in a brick > * wireless networks with custom ifnames are improperly bridged > * option ipv6 for ppp based protocols is broken because it clashes > with option ipv6 in device sections I would like to merge this update of iproute2 if Russel is fine with it, but I do not see this blocking 21.02-rc1: https://github.com/openwrt/openwrt/pull/4025 If there are some other bugs in the 21.02 branch which are fixed in master, we can backport the fixed as long as they are not so big. If there is something missing, just ask on the mainling list. In would like to get 21.02-rc1 soon, so more users start testing it and we get more bug reports. How should we continue? 1. Tag 21.02-rc1 and do the release in the next days with the current state. 2. Merge the LuCI DSA changes from master to 21.02 branch now and do 21.02-rc1 ~3 days to see if some big problems come up. Will Wifi 6 support be added to the interface? We have some support for a couple of AX routers, so it would be nice if they can work without manually tweaking things. The underlying structure seems to support it already: https://forum.openwrt.org/t/got-802-11ax-working-in-linksys-e8450/91533 3. Wait till the problems reported by jow are fixed and do the 21.02-rc1 them. 4. Wait an other 2 weeks and see how it looks them. I would prefer if we merge the LuCI DSA changes from master to 21.02 branch now and do 21.02-rc1 soon. We should list the problems as known problems. It would be nice if someone else could also look into these problems and propose fixes. Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel --- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1
Hauke Mehrtens kirjoitti 7.4.2021 klo 1.29: Hi, How do we want to go forward with OpenWrt 21.02-rc1? * I think the base system is ok. * The http (original wolfssl) problem reported by jow is fixed * LuCI in the 21.02 branch still misses DSA support, this was merged into master some time ago as far as I understood. ... In would like to get 21.02-rc1 soon, so more users start testing it and we get more bug reports. How should we continue? 1. Tag 21.02-rc1 and do the release in the next days with the current state. 2. Merge the LuCI DSA changes from master to 21.02 branch now and do 21.02-rc1 ~3 days to see if some big problems come up. Option 2 of merging the LuCI DSA changes and then making the first 21.02-rc sounds good to me. Also the option 1 of doing the rc now would likely be ok, as the only a few targets actually use DSA, so the absence of LuCI support for DSA does not concern that many users. I would prefer if we merge the LuCI DSA changes from master to 21.02 branch now and do 21.02-rc1 soon. We should list the problems as known problems. It would be nice if someone else could also look into these problems and propose fixes. Like with previous releases, the developers interest mainly stays on the master, and not much happens in the new release branch... It is now 50 days since the 21.02 was branched in February, so a high time to get the rc out. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1
On Tue, Apr 6, 2021 at 5:33 PM Ilya Lipnitskiy wrote: > > Hi Hauke, > > On Tue, Apr 6, 2021 at 3:43 PM Hauke Mehrtens wrote: > > > > Hi, > > > > How do we want to go forward with OpenWrt 21.02-rc1? > > > > * I think the base system is ok. > > * The http (original wolfssl) problem reported by jow is fixed > > * LuCI in the 21.02 branch still misses DSA support, this was merged > > into master some time ago as far as I understood. > > > > Jow reported this end of March: > > > I found some serious regressions in the luci device config support. > > > not sure yet how long it'll take to sort out. The netifd uci config > > > grew so complex that it'll take a while to try all cases > > > * changing interface settings after previously enabling certain > > > options results in a brick > > > * wireless networks with custom ifnames are improperly bridged > > > * option ipv6 for ppp based protocols is broken because it clashes > > > with option ipv6 in device sections > > > > I would like to merge this update of iproute2 if Russel is fine with it, > > but I do not see this blocking 21.02-rc1: > > https://github.com/openwrt/openwrt/pull/4025 > > > > If there are some other bugs in the 21.02 branch which are fixed in > > master, we can backport the fixed as long as they are not so big. If > > there is something missing, just ask on the mainling list. > Can we get a decision on the in-tree WireGuard migration PR? > https://github.com/openwrt/openwrt/pull/3960 Indeed this should happen for 21.02. I won't be supporting the prior compat module in OpenWRT any longer. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt 21.02-rc1
Hi Hauke, On Tue, Apr 6, 2021 at 3:43 PM Hauke Mehrtens wrote: > > Hi, > > How do we want to go forward with OpenWrt 21.02-rc1? > > * I think the base system is ok. > * The http (original wolfssl) problem reported by jow is fixed > * LuCI in the 21.02 branch still misses DSA support, this was merged > into master some time ago as far as I understood. > > Jow reported this end of March: > > I found some serious regressions in the luci device config support. > > not sure yet how long it'll take to sort out. The netifd uci config > > grew so complex that it'll take a while to try all cases > > * changing interface settings after previously enabling certain > > options results in a brick > > * wireless networks with custom ifnames are improperly bridged > > * option ipv6 for ppp based protocols is broken because it clashes > > with option ipv6 in device sections > > I would like to merge this update of iproute2 if Russel is fine with it, > but I do not see this blocking 21.02-rc1: > https://github.com/openwrt/openwrt/pull/4025 > > If there are some other bugs in the 21.02 branch which are fixed in > master, we can backport the fixed as long as they are not so big. If > there is something missing, just ask on the mainling list. Can we get a decision on the in-tree WireGuard migration PR? https://github.com/openwrt/openwrt/pull/3960 Ilya ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
OpenWrt 21.02-rc1
Hi, How do we want to go forward with OpenWrt 21.02-rc1? * I think the base system is ok. * The http (original wolfssl) problem reported by jow is fixed * LuCI in the 21.02 branch still misses DSA support, this was merged into master some time ago as far as I understood. Jow reported this end of March: > I found some serious regressions in the luci device config support. > not sure yet how long it'll take to sort out. The netifd uci config > grew so complex that it'll take a while to try all cases > * changing interface settings after previously enabling certain > options results in a brick > * wireless networks with custom ifnames are improperly bridged > * option ipv6 for ppp based protocols is broken because it clashes > with option ipv6 in device sections I would like to merge this update of iproute2 if Russel is fine with it, but I do not see this blocking 21.02-rc1: https://github.com/openwrt/openwrt/pull/4025 If there are some other bugs in the 21.02 branch which are fixed in master, we can backport the fixed as long as they are not so big. If there is something missing, just ask on the mainling list. In would like to get 21.02-rc1 soon, so more users start testing it and we get more bug reports. How should we continue? 1. Tag 21.02-rc1 and do the release in the next days with the current state. 2. Merge the LuCI DSA changes from master to 21.02 branch now and do 21.02-rc1 ~3 days to see if some big problems come up. 3. Wait till the problems reported by jow are fixed and do the 21.02-rc1 them. 4. Wait an other 2 weeks and see how it looks them. I would prefer if we merge the LuCI DSA changes from master to 21.02 branch now and do 21.02-rc1 soon. We should list the problems as known problems. It would be nice if someone else could also look into these problems and propose fixes. Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
