Yes, please upload anything you can here: https://nc.netgate.com/nextcloud/s/J28ziC2QCa2pym9

If you are able to please generate a status report and include that.
https://docs.netgate.com/pfsense/en/latest/recipes/diagnostic-data.html

Awesome, thanks for the feedback! 👍

@stephenw10
Ok. Will try later

since disabling trackv6 all good.
I now put a static address in Wireguard interface and all is working.

But i guess that interface with NOARP needs a special treatment !

@stephenw10 Done and resolved the issue.
Thanks
Ted

Mmm, in each case though the first thing logged is that ice0 and the VLAN on it lose link momentarily:

May 16 04:53:26 kernel ice0.1003: link state changed to UP May 16 04:53:26 kernel ice0: link state changed to UP May 16 04:53:26 kernel ice0: Link is up, 10 Gbps Full Duplex, Requested FEC: None, Negotiated FEC: None, Autoneg: False, Flow Control: None May 16 04:53:26 check_reload_status 679 Linkup starting ice0.1003 May 16 04:53:26 check_reload_status 679 Linkup starting ice0 May 16 04:53:26 kernel ice0.1003: link state changed to DOWN May 16 04:53:26 kernel ice0: link state changed to DOWN May 16 04:53:26 check_reload_status 679 Linkup starting ice0.1003 May 16 04:53:26 check_reload_status 679 Linkup starting ice0

Can you try a different port there?

Weird that the switch doesn't show it though...

@Maff

Does your router use PPPoE for the ISP connection?

☕️

https://redmine.pfsense.org/issues/16191

@stephenw10 Yes same blank blue screen with the words "Return to Dashboard" which when clicked on returns me to the dashboard.

Indeed, I'm not aware of anything in beta that should present like that so it might well apply to any upgrade on that specific device. Somehow.

@marcosm I have tested the fix, and it works (not that I ever doubed it wouldn't)

Thanks guys!

@jimp thank you for the clarification. Yes, I think it must have been very late at night when that got added...

@stephenw10 pftop seems a bit flakey. I actually managed to view the rules a couple of times today by just starting pftop and then navigate to rules. But now that doesn't work any more. Running the full command gives randomly either bus error, segmentation fault or the assert

Yep that was it.

Thanks for your help :)

everything seems fine now that main wan is not flapping or manually set to down

@stephenw10 after stopping HAProxy and restarting, I did not have the same issue. It is working as normal right now.

I cannot say console was unresponsive but it was lagging and timing out time to time until I stopped HAProxy.

Here, trying to reboot but I did not see the continuation. Most probably, this also timed out or aborted since uptime was 2d when I managed to get back into the UI.

c2bec4fc-f666-4f20-ac42-6fd8a0ae6853-image.png

When I tried to connect remotely via HAProxy to servers behind. I was always getting ssl handshake error "ssl handshake failed error code 525".

Current ps -auxwwd

edc1bd31-ad18-45f3-b20d-45ef2f9ee0bb-image.png

@marcosm Thanks, Marcos!

@marcosm after applying the patch IPv6 as the second interface address is up and running again.

Thanks you and have a great weekend.

For reference:
https://redmine.pfsense.org/issues/16156

@townsenk64 Same here, no issues since I put the debug version.
Maybe a leftover glitch from the upgrades?