@stephenw10

Thanks for testing and the support. I found the problem in the "unofficial" script. Somehow only using the ip-adress wasn't working anymore. Adding https to it fixed it.
Sometimes the solution is simple but the error was misleading.
This case is closed.
Thanks again.

What exactly was it you tried to import and how?

Yup, test it first is good advice.

https://docs.netgate.com/pfsense/en/latest/recipes/freebsd-pkg-repo.html#concerns-warnings

@stephenw10

Sorry about that, had /32 instead of /24 under aliases. My fault! Thanks for your help. All good now!

Yup you need to manually check each replacement because there's a significant chance you might find the string em0 for example in the certs fields.

If you had to copy it to opt7 then you had not yet re-assigned lan as the bridge0 interface. Once you do that everythign that was applied to the original LAN interface would apply to the bridge and hence all the bridged interfaces.

I just wanted to follow up on this and let everyone know I could never get anywhere. While I did backup/restore last month I kept this box around to try to troubleshoot. No pkg command would yield any results, even trying to install from local.

If anyone winds up in the same boat, I'm afraid this post likely won't help.

@stephenw10 Thank you so much, problem solved, i change the setting that you suggest to me and now work perfectly.

It would usually demote itself, causing a failover, if any interface that has a CARP VIP on it loses link. That can be affected if the interface is a bridge though for example. The bridge itself never goes down.

Ok, so try swapping it to LAN and see if the problem follows the USB NIC.

It may not. You might find it 'just works' as the WAN.

You can restore the config to pull in all the previous settings.

However the new NDI will need to registered for Plus upgrade to get 23.09.1 though.

Yes, they happened simultaneously and crash reports although I didn't adjust any with the secondary.

@alhaunts Nice, just installed it here.

https://redmine.pfsense.org/issues/15119#change-72146

@stephenw10 Thank you!

You're a legend, both of those combined are what restored the internet connection.

Thank you so much for all of your assistance over the past few days.

I greatly appreciate all of your help!

@stephenw10 Perfect example of why I checked here first!

@Fringe1533

Hi
To connect such clients on Mac OS, I recommend using the Apple Configurator program, in which you can create a profile for connecting to a Wi-fi network (WPA-Enterprise).
After creation, this profile is imported to the MacBook, and it connects successfully

f2b0a1cd-2885-4edc-aec0-acd1644a38f1-image.png

da5fa148-047c-4674-a85d-8f7cc6c702bf-image.png

050f7847-3a4d-45da-a9c2-d8364172eb67-image.png

8db8eddb-9eff-426c-aae3-bfb3c84d5e06-image.png

bfc430f0-774f-4430-b611-ce8c7fdfec32-image.png

@stephenw10 thank you for your wisdom.
@pfguy2018 thank you for asking.

@pfsense57352
🤣

You should not have gateways set on LAN or OPT1. (or possibly OPT2). Only the WAN should have a gateway set for pfSense and that is added automatically for DHCP.

When you add a gateway to an interface pfSense treats it as a WAN and that is not the case for LAN or OPT1.

Additionally whatever is at 10.0.2.2 is not responding to ping. That's probably because it's the VBox NAT host. You should set some the external IP address for pfSense to monitor on the WAN.

Steve