> On Sep 15, 2025, at 18:54, Chris Ross <[email protected]> wrote:
>
>> On Sep 15, 2025, at 15:01, Ronald Klop <[email protected]> wrote:
>>
>> Are you able to boot a 14.2 kernel?
>> To split the search space in two.
>
> I could do that. What’s the easy way to get an unpacked 14.2 generic amd64
> kernel?
Well, okay, that was something. I extracted a 14.2-RELEASE /boot/kernel and
was able to boot into it. The system came up far more properly than it had
under 14.1-RELEASE-p5 tried earlier. (Resource limits couldn’t be applied
in rc.subr with 14.1). But, the IPv6 routing problem still exposed itself.
Then, just to confirm, I rebooted into 14.1-RELEASE-p5 again. This was
where things stopped being useful. This _also_ failed in the same way
the more recent kernels had. I don’t _think_ I changed anything between
the last time I tested that, just selecting a different kernel from the
boot menu, but this time it didn’t magically work. So, I can’t say any
longer that it’s necessarily a regression between 14.1p5 and 14.3. I
mean, I could try resetting my whole image to a snapshot from 14.1 (ZFS
root), but I don’t think it’s worth that effort.
>> On Sep 15, 2025, at 15:05, Tom Pusateri <[email protected]> wrote:
>>
>> I would try running the 14.3p2 system without the VLAN configuration and a
>> direct connection to the upstream provider hardware (no switch) and see if
>> the problem persists. That will determine if it’s a VLAN issue.
>
> That would be a bit of work. I have an available ix port, so I can run a
> line to the machine
> without vlan. It would still be a VLAN in the switch, because running a
> direct line is not
> possible without much rewiring and very long cables.
So this is my next attempt. I don’t know if I have the energy for the whole
thing tonight, but I’ll start running cables and configuring the switch at
least.
See where I get. :-)
Thanks all for your time, I am just more confused now.
- Chris
