On 2/16/23 13:59, Jan Breuer wrote:
On 16. 2. 2023 16:21, Peter Naulls wrote:
On 2/15/23 13:31, Peter Naulls wrote:
I'm trying to track yet another vendor vs current OpenWrt driver mishandling.
x00
Can you please provide info about the exact SoC and hardware you are using?
Hi Jan,
We only set the RA lifetime to what is configured in UCI when there is a
default route and valid prefix. In any other case, we set it to 0. This
leads to confusion where people believe ra_lifetime is completely
ignored. In case there is a default route, but no valid prefix, a debug
message
We currently only check ra_default when an interface has valid
addresses. This results in ra_default being ignored in case we have an
interface with only link-local addresses. This effectively breaks the
use of value 2 for the ra_default parameter.
Fix this by always checking ra_lifetime,
On Mon, Feb 13, 2023 at 9:18 PM wrote:
>
> We currently only check ra_default when an interface has valid
> addresses. This results in ra_default being ignored in case we have an
> interface with only link-local addresses. This effectively breaks the
> use of value 2 for the ra_default parameter.
On Mon, Feb 13, 2023 at 9:18 PM wrote:
>
> We only set the RA lifetime to what is configured in UCI when there is a
> default route and valid prefix. In any other case, we set it to 0. This
> leads to confusion where people believe ra_lifetime is completely
> ignored. In case there is a default
Switch over from testing version.
Signed-off-by: Tim Harvey
---
target/linux/octeontx/Makefile | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/target/linux/octeontx/Makefile b/target/linux/octeontx/Makefile
index 50c5cd6d217d..5260291d0504 100644
---
On 16. 2. 2023 16:21, Peter Naulls wrote:
>
> On 2/15/23 13:31, Peter Naulls wrote:
> >
> > I'm trying to track yet another vendor vs current OpenWrt driver
> > mishandling.
> >
> x00
Can you please provide info about the exact SoC and hardware you are using?
> >
> > In particular, for the
On 2/15/23 13:31, Peter Naulls wrote:
I'm trying to track yet another vendor vs current OpenWrt driver mishandling.
x00
In particular, for the first read attempt, the value is always the first
value sent as part of the last write. i.e, 3 in this case. After, that,
it's always 0 (the correct
I am repeating myself, but it looks strange that we have only 3 build workers
on packages for the active master branch, while the almost dormant 22.03 has
currently 10 active workers (and concurrent builds).
The packages build cycle in master is currently uncomfortably long.
Hannu
Hi,
it
Including kernel.mk moves the package build folder in the linux one, which
is confusing since this isn't building any kernel modules.
package-defaults.mk is already included my package.mk.
Signed-off-by: Andre Heider
---
package/network/utils/wireguard-tools/Makefile | 2 --
1 file changed, 2
10 matches
Mail list logo
