On Sat, Aug 12, 2023 at 9:01 AM Kristof Provost wrote:
>
> On 12 Aug 2023, at 17:42, Kevin Bowling wrote:
> > On Sat, Aug 12, 2023 at 1:45 AM Kristof Provost wrote:
> >>
> >> I also don’t have a setup to reproduce the issues Paul reported.
> >> Given the discussion in the PR I assumed everyone wa
On 12 Aug 2023, at 17:42, Kevin Bowling wrote:
> On Sat, Aug 12, 2023 at 1:45 AM Kristof Provost wrote:
>>
>> I also don’t have a setup to reproduce the issues Paul reported.
>> Given the discussion in the PR I assumed everyone was happy with the fix he
>> posted.
>
> Ok, I happened to be looking
On Sat, Aug 12, 2023 at 1:45 AM Kristof Provost wrote:
>
> I also don’t have a setup to reproduce the issues Paul reported.
> Given the discussion in the PR I assumed everyone was happy with the fix he
> posted.
Ok, I happened to be looking into it when the commit went in.
Please revert, it's n
I also don’t have a setup to reproduce the issues Paul reported.
Given the discussion in the PR I assumed everyone was happy with the fix he
posted.
Best regards,
Kristof
On 12 Aug 2023, at 3:28, Kevin Bowling wrote:
> I think this may be a better fix, currently untested
>
> diff --git a/sys/net
I think this may be a better fix, currently untested
diff --git a/sys/net/if_vlan.c b/sys/net/if_vlan.c
index 6aa872a19364..51f0bc63ebda 100644
--- a/sys/net/if_vlan.c
+++ b/sys/net/if_vlan.c
@@ -2074,7 +2074,7 @@ vlan_capabilities(struct ifvlan *ifv)
if (p->if_capabilities & IFCAP_VLAN_HWC
I am wondering what is going on with this patch, it doesn't seem like
a full fix. At the very least we should clean up the "can't disable
some capabilities" message.
I've been looking at this for a couple hours and am wondering what is
going on in if_bridge.. it looks like it correctly loops over
