On 9/1/21 4:15 AM, Andy Botting wrote:
On Wed, 1 Sept 2021 at 11:56, Alexander E. Patrakov wrote:
Hauke Mehrtens :
On 8/31/21 1:52 PM, Alexander E. Patrakov wrote:
Hauke Mehrtens wrote:
We did the 21.02-rc4, but there is still a problem with flow offloading
as this was not fixed. The oth
Hey Hauke.
On 31/08/2021 00:51, Hauke Mehrtens wrote:
All people who answered agreed to do the release soon and keep this as
a known bug.
I plan to tag 21.02.0 on Wednesday, 1. September if no one objects.
I have a detailed mail to send about the situation with DSA. It's about
documentation
On Wed, 1 Sept 2021 at 11:56, Alexander E. Patrakov wrote:
>
> Hauke Mehrtens :
>
> >
> > On 8/31/21 1:52 PM, Alexander E. Patrakov wrote:
> > > Hauke Mehrtens wrote:
> > >
> > >> We did the 21.02-rc4, but there is still a problem with flow offloading
> > >> as this was not fixed. The other proble
Hauke Mehrtens :
>
> On 8/31/21 1:52 PM, Alexander E. Patrakov wrote:
> > Hauke Mehrtens wrote:
> >
> >> We did the 21.02-rc4, but there is still a problem with flow offloading
> >> as this was not fixed. The other problems should be fixed now.
> >
> >> ...
> >
> >> Some more information can be fo
On 8/31/21 1:52 PM, Alexander E. Patrakov wrote:
Hauke Mehrtens wrote:
We did the 21.02-rc4, but there is still a problem with flow offloading
as this was not fixed. The other problems should be fixed now.
...
Some more information can be found here:
https://forum.openwrt.org/t/software-f
Hauke Mehrtens wrote:
> We did the 21.02-rc4, but there is still a problem with flow offloading
> as this was not fixed. The other problems should be fixed now.
> ...
> Some more information can be found here:
> https://forum.openwrt.org/t/software-flow-offloading-and-conntrack-timeouts/74588
>
On 8/29/21 11:53 AM, Hauke Mehrtens wrote:
Hi,
We did the 21.02-rc4, but there is still a problem with flow offloading
as this was not fixed. The other problems should be fixed now.
On 7/17/21 5:45 PM, Hauke Mehrtens wrote:
Currently we still have these problem:
- IPv6 broken with flow offl
+1 for release. It's just been too long since the last one. The idea
of time-based releases is getting lost and this is a process issue we
definitely should address.
On Sun, 29 Aug 2021 at 11:44, Hannu Nyman wrote:
>
> Hauke Mehrtens wrote at Sun Aug 29 02:53:47 PDT 2021:
>
> > Should we just re
On Aug 29, 2021, at 6:31 AM, Hannu Nyman wrote:
>
> Hauke Mehrtens wrote at Sun Aug 29 02:53:47 PDT 2021:
>
> We have now reverted back to the old "let's wait long for branching and then
> wait even longer for the actual release".
>
> The reality is the same than earlier: almost all devs and e
Hi Hauke
Op zondag 29 augustus 2021 om 11u53 schreef Hauke Mehrtens
:
Hi,
We did the 21.02-rc4, but there is still a problem with flow
offloading as this was not fixed. The other problems should be fixed
now.
On 7/17/21 5:45 PM, Hauke Mehrtens wrote:
Currently we still have these problem:
-boun...@lists.openwrt.org]
On Behalf Of Hauke Mehrtens
Sent: Sonntag, 29. August 2021 11:54
To: OpenWrt Development List
Cc: John Crispin; Jo-Philipp Wich; Kevin 'ldir' Darbyshire-Bryant
Subject: Re: OpenWrt 21.02 status
Hi,
We did the 21.02-rc4, but there is still a problem with flow off
ryant
> Subject: Re: OpenWrt 21.02 status
>
> Hi,
>
> We did the 21.02-rc4, but there is still a problem with flow offloading as
> this
> was not fixed. The other problems should be fixed now.
>
> On 7/17/21 5:45 PM, Hauke Mehrtens wrote:
> > Currently we still h
Hauke Mehrtens wrote at Sun Aug 29 02:53:47 PDT 2021:
> Should we just release with this as a known problem?
>
> Other than this problem I am not aware of any other critical problem.
We should.
It is annoying that 21.02 was branched more than 6 months ago, but no final
release has happened by
Hi,
We did the 21.02-rc4, but there is still a problem with flow offloading
as this was not fixed. The other problems should be fixed now.
On 7/17/21 5:45 PM, Hauke Mehrtens wrote:
Currently we still have these problem:
- IPv6 broken with flow offloading (according to reports, potentially
r
Hi Hauke,
> Could you please try this patch:
> https://patchwork.ozlabs.org/project/openwrt/patch/20210531195732.522580-1-dqf...@gmail.com/
> I do not see this problem with this patch any more, I am not sure which
> change exactly fixed it or if I am unable to reproduce it any more.
>
> I have som
On 7/31/21 9:05 AM, Andy Botting wrote:
Thank you for the link and the description on how to reproduce this:
while [ 1 ]; do curl -k -s -o /dev/null -L -I -w "%{http_code}
'%{time_total}'\n" -H 'Host: www.6connect.com'
https://[2607:fae0:a000::9]; sleep 1; done
I see this problem once every 250
> Thank you for the link and the description on how to reproduce this:
> while [ 1 ]; do curl -k -s -o /dev/null -L -I -w "%{http_code}
> '%{time_total}'\n" -H 'Host: www.6connect.com'
> https://[2607:fae0:a000::9]; sleep 1; done
>
> I see this problem once every 250 tries, but I got a wireshak cap
Folks,
I made a start at documentation for the DSA networking in 21.02. I now realize
that I have neither the knowledge necessary to write good docs, nor will I have
the time to organize this work.
Consequently, I have to step back from the following pages:
Upgrading to OpenWrt 21.02.0: https:
On 7/20/21 9:40 AM, Andy Botting wrote:
- IPv6 broken with flow offloading (according to reports, potentially
related to hw flow offloading)
There is a bug report about this at:
- https://bugs.openwrt.org/index.php?do=details&task_id=3373
I've reproduced it with and without hw flow offloadi
Or we could drop support for it and let the user do it by themselves.
At least for the release of OpenWrt 21.02.
The warning pop-up when the user heads to Network -> Interfaces after
upgrade, could let the user know that, if they have set up packet
mirroring with swconfig, they will have to do it
If the user enabled packet mirroring on swconfig, we need to migrate that too.
I don't think UCI supports packet mirroring via the DSA framework,
yet. Anyone with UCI knowledge want to help out?
tc-full package is needed.
Refer to:
https://biot.com/switches/testing/mirroring
On Wed, Jul 21, 202
Hi Rich
On Wed, Jul 21, 2021 at 2:06 AM Rich Brown wrote:
>
> Hi Arınç
>
> On Jul 20, 2021, at 3:09 PM, Arınç ÜNAL wrote:
>
> Let's say we wrote a script that takes 19.07 network config and
> outputs one with DSA configuration instead, how do we implement it in
> the image that, after upgrade, i
Hey Rich
I'd love to help write an explanation and the steps required to
convert a swconfig setup to DSA. I will start working on the draft.
It should encourage people to upgrade to 21.02 without worrying about
losing their current VLAN setup.
I have a good understanding of swconfig and DSA switc
Hi Arınç
> On Jul 20, 2021, at 12:23 AM, Arınç ÜNAL wrote:
>
> I believe I could try to make one, I have a pretty good understanding
> of swconfig and DSA configuration. If someone can help me out with
> writing the script, I believe we can pull it off as a team effort.
I am in need of experti
> - IPv6 broken with flow offloading (according to reports, potentially
> related to hw flow offloading)
There is a bug report about this at:
- https://bugs.openwrt.org/index.php?do=details&task_id=3373
I've reproduced it with and without hw flow offloading on mt7621.
I think it's very importa
On 19/07/21 21:11, Luiz Angelo Daros de Luca wrote:
This is not a migration script but a mitigation. A 21.02 image should
detect during boot if the current network config was for swconfig in a
system using DSA.
It could happen during early boot stages, after FS are mounted, before
services ar
> It could happen during early boot stages, after FS are mounted, before
> services are started, something similar to uci-defaults, but not in a "run
> once"
> way.
> It would cover both upgrades with confs and restores. We are asking the
> user to upgrade without saving confs but nothing will pre
Hi Hauke,
On Mon, Jul 19, 2021 at 8:05 PM Hauke Mehrtens wrote:
>
> Hi Hans,
>
> On 7/17/21 5:45 PM, Hauke Mehrtens wrote:
> > Hi,
> >
> > In general the 21.02-rc3 looks good, but we still have some problems.
> >
> > Currently we still have these problem:
>
>
>
> > - DHCPv6 broken if lease t
'Jo-Philipp Wich'; 'Kevin 'ldir' Darbyshire-Bryant'; 'John
> Crispin'; 'Rafał Miłecki'
> Subject: Re: OpenWrt 21.02 status
>
> On Sun, Jul 18, 2021 at 10:30:20PM +0200, Adrian Schmutzler wrote:
> > > The last time I
> I believe what he meant to say was to make another 19.07.x point
> release with an updated sysupgrade mechanism which would improve the
> situation when upgrading to 21.02.x and, for example, allow
> flashing with non-matching DEVICE_COMPAT_VERSION already when
> specifying the '-n' flag to not k
Hi Hans,
On 7/17/21 5:45 PM, Hauke Mehrtens wrote:
Hi,
In general the 21.02-rc3 looks good, but we still have some problems.
Currently we still have these problem:
- DHCPv6 broken if lease times < 12h chosen
- https://forum.openwrt.org/t/openwrt-21-02-0-third-release-candidate/9936
On Sun, Jul 18, 2021 at 10:30:20PM +0200, Adrian Schmutzler wrote:
> > The last time I tried it was very confusing. When I first read about "new
> > fresh
> > installation", I thought: "install without keeping settings".
> > However, OpenWrt returned an image check failure, even when I did not
> >
> The last time I tried it was very confusing. When I first read about "new
> fresh
> installation", I thought: "install without keeping settings".
> However, OpenWrt returned an image check failure, even when I did not
> keep the settings (sysupgrade -n). It was the same type of error (image
> va
>> 1) I created a new "Upgrading to OpenWrt 21.02.0" page at:
>> https://openwrt.org/playground/richb/to2102 I distilled the announcement
>> page (https://openwrt.org/releases/21.02/notes-21.02.0) to make this
>> checklist for people that won't read that entire page.
>> Did I get the new page
On Sat, Jul 17, 2021 at 9:48 AM Hauke Mehrtens wrote:
>
> In addition there are multiple problems with specific device, if they
> get fixed it would be nice otherwise we just leave it like it is now.
Configuration of 60 GHz radios via LuCI is still broken (my proposed
patch [1] was not accepted i
> > 2) I was pretty fuzzy about what people should do if their target did
> > migrate to DSA. Do we have a guide to help those people through the
> > transition?
>
> We do not support a migration and people have to start with a new fresh
> installation. Doing a backup and restoring some settings
Hi Rich,
On 7/17/21 11:04 PM, Rich Brown wrote:
Hauke and all,
Thanks for the hard work to corral all those outstanding bug reports.
As we move forward, I want to be sure the documentation side is as good as the
software... I have these comments/questions:
1) I created a new "Upgrading to Op
Hauke and all,
Thanks for the hard work to corral all those outstanding bug reports.
As we move forward, I want to be sure the documentation side is as good as the
software... I have these comments/questions:
1) I created a new "Upgrading to OpenWrt 21.02.0" page at:
https://openwrt.org/p
I would like to bring this to everyone's attention for the final
release of 21.02.
There must be a fundamental change of handling interfaces & VLANs on a
switch on DSA-enabled architectures on OpenWrt.
Please refer to this post:
http://lists.openwrt.org/pipermail/openwrt-devel/2021-July/035787.html
On 2021-07-17 17:45, Hauke Mehrtens wrote:
> Hi,
>
> In general the 21.02-rc3 looks good, but we still have some problems.
>
> Currently we still have these problem:
>
> - IPv6 broken with flow offloading (according to reports, potentially
> related to hw flow offloading)
> - PPPoE allegedly
Hi,
In general the 21.02-rc3 looks good, but we still have some problems.
Currently we still have these problem:
- IPv6 broken with flow offloading (according to reports, potentially
related to hw flow offloading)
- PPPoE allegedly broken (according to reports, not fully reproducible,
likely
41 matches
Mail list logo
