Hello, Ryan I had suspected the syspatches but reverting the few that I thought I had applied since early January didn't seem to work. my focus was diverted when I found that restarting the interface seemed to work with the the latest patches applied. Thanks
On Fri, 20 Mar 2020 at 10:41, Ryan Freeman <[email protected]> wrote: > > On Fri, Mar 20, 2020 at 03:30:52AM -0700, Ryan Freeman wrote: > > On Fri, Mar 20, 2020 at 08:54:40AM +0100, Stefan Sperling wrote: > > > On Fri, Mar 20, 2020 at 01:50:42AM +0000, Tom Smyth wrote: > > > > >Synopsis: <bridge with alot of ports does not forward frames after > > > > >reboot > > > > > >Category: <Network > > > > > >Environment: > > > > System : OpenBSD 6.6 > > > > Details : OpenBSD 6.6 (GENERIC.MP) #7: Thu Mar 12 11:55:22 MDT 2020 > > > > [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > > > > > > > Architecture: OpenBSD.amd64 > > > > Machine : amd64 > > > > >Description: > > > > <if you configure a bridge with hostname.bridge and add 90 vlans as > > > > protected ports > > > > the bridge will not forward frames however if you run sh > > > > /etc/netstart bridgex it does > > > > start to forward > > > > ifconfig bridge101 after reboot compared with ifconfig bridge101 after > > > > the restart of the interface > > > > using sh /etc/netstart appear very similar, the vlans appear to be > > > > members of the bridge fine > > > > both the bridge appears to learn mac addresses on ports both after > > > > reboot and after manual restart > > > > of interface) > > > > the only difference that I observed was the interface index > > > > after reboot bridge index was 6 > > > > after restarting the interface the bridge index was 98 > > > > > >How-To-Repeat: > > > > <create a hostname.bridge101 file add 90 vlans as protected ports > > > > reboot the machine > > > > > >Fix: > > > > <restarting the bridge interface using sh /etc/netstart bridge101 worked > > > > I have added sh /etc/netstart bridge101 to /etc/rc.local > > > > > > Tom, could you share your hostname.bridge101 file? > > > That might make it easier for others to reproduce the issue. > > > > > > Is there any obvious difference in the counters displayed by > > > netstat -nI bridge101 or netstat -s in the working vs non-working states? > > > > > > And does it also happen on -current? > > > > > > > Hey, > > > > I just experienced something very similar to this last night on two > > separate hosts running amd64 6.6. I had rebooted the first machine > > after installing syspatch 021, 022 and noted i couldn't reach the > > vm after reboot. > > Gah, that should say syspatch 022_sysctl, 023_sosplice. Apologies. -- Kindest regards, Tom Smyth.
