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
Hi Federico,
Le sam. 31 juil. 2021 à 20:33, Federico Capoano
a écrit :
>
> Hi everyone,
>
> I wrote about this issue in the forum and I was advised to post here
> as well so I'm following the advice.
> (Forum discussion:
> https://forum.openwrt.org/t/ssh-mtu-issues-on-openvpn-on-openwrt-21-02-rc3
Hi everyone,
I wrote about this issue in the forum and I was advised to post here
as well so I'm following the advice.
(Forum discussion:
https://forum.openwrt.org/t/ssh-mtu-issues-on-openvpn-on-openwrt-21-02-rc3-linux-kernel-5-4-132/102686).
I upgraded a few devices which were running a custom b
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
On 30/07/2021 20:56, Stijn Tintel wrote:
The generic config has CONFIG_RCU_EXPERT=y, which exposes
CONFIG_RCU_FANOUT. This is set to 32 in the generic config, but the
default for 64bit kernels is 64. This causes a warning during boot:
[0.00] rcu: CONFIG_RCU_FANOUT set to non-default
> 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
