On Mon, May 05, 2025 at 02:30:45PM -0600, Philip Prindeville via openwrt-devel
wrote:
> >> Is that a fixed map? I.e. (1) there is a max of 6 possible egress paths
> >> and
> >> (2) any of the other bits could be used without risk of conflict with
> >> mwan3?
> >
> > That would not work. It is
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 May 5, 2025, at 11:17 AM, J
On Mon, May 05, 2025 at 09:06:02AM -0600, Philip Prindeville via openwrt-devel
wrote:
> > The mask encodes the selected uplink that is used in a policy based
> > routing. One bit could encode only "no decision" and "uplink 1".
>
> Is that a fixed map? I.e. (1) there is a max of 6 possible egress
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 May 5, 2025, at 5:26 AM, Jo
On Sun, May 04, 2025 at 04:16:40PM -0600, Philip Prindeville via openwrt-devel
wrote:
> Does anyone know why MMX_MASK defaults to 0x3f00 in /lib/mwan3/common.sh?
> Given that marking only has 16-bits available, and only 1 seems to be
> necessary, why use 6 of the 16 instead?
>
> Am I missing s
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 ---
Hi,
Does anyone know why MMX_MASK
