Hmm, so it tries to connect via em0 before it has an IP and fails. Then retries successfully?

That's what you would see if the device loses it's default route or has an invalid default route.

Check Diag > Routes when it happens.

Make sure the default gateway in System > Routing > Gateways is set to WAN and not automatic.

Steve

@NollipfSense said in Register DHCP WAN address with unbound?:

I found it best also to have a real domain (often a $10/yr cost)

Exact.
And it comes with a free bonus : free certificates.

Checked the connection last night and this morning again, confirmed it's still good. So, I believe this was the issue 100%.

Glad I can go home with no worries. Thanks guys.

@Khoomn oh so you won't be using the dumb switches then?

@michmoor said in interface rename causes brief outage:

Now that i think about it, i think its related to my ticket - https://redmine.pfsense.org/issues/14483

This seems familiar. Applying any changes to an IPsec config even if its phase 1 results in all FRR neighborships flapping.

That should be logged if it's happening.

@stephenw10 Now that 23.05.1 and 2.7 have been released, is it back on the timeline?

Ah, that would do it! 👍

@Gertjan @stephenw10

Thank you for the support. I received the device at my office. So tried all possible commands, but the web gui failed to show up. I also did factory reset to default but that didn't help. Finally I have decided to reinstall the system.

Definitely not the 1100 internal switch. But, yes, could be a bridge somewhere if you have any defined. Bridges in pfSense do support STP.

@mrrobot . I managed to solve the problem, but what exactly is going on? I can't say.
Change DNS Resolution Behavior to "Use remote DNS Servers" and put 9.9.9.9 as your first DNS server.

Open a ticket with us to get the link: https://www.netgate.com/tac-support-request

@jimp said in HAProxy error after upgrade to 23.05.01:

If you still get this try, moving from haproxy-devel to haproxy. The haproxy-devel you were on in past versions is now haproxy.

The version of haproxy on 23.05.1 (now) has the same PHP/package code as haproxy-devel but haproxy-devel is now on an even newer base version of haproxy binaries that may have other problems as it hasn't been tested as much (if at all).

Swapping to HAProxy fixed the issue - thank you.

The resolver log is also rotating every 15mins but, yes, the filter log is was rotating every minute when that data was taken.

I should have been more clear when I said containers, I was actually talking about containers and virtual machines, which I serve via HAProxy.

Everytime I configure a new container I have to use the HAProxy web gui in pfsense, I do this frequently enough that I was wondering if pfsense had an API, which I now know it does not.

I like to automate things when I can, thanks for the responses.

I mean I would expect to see increased CPU usage when passing traffic. But that does look higher than expected. Suricata running on that traffic would explain it though as you say.

@SteveITS said in Trouble Accessing Internet on pfSense fresh install.:

trying to decide how the Cheez-it scale is scored… 🧐

Oh the brand name ones are "meh" you come above them ;-)

@jimp I'm pretty sure at this point that the problem was caused by the MACs changing. Since I set the MACs to static and the problem has not reoccurred.

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