@mauro-tridici you can not route a fqdn, you would route the IP or network that IP resides on.

@SteveITS said in Release notes for pfSense Plus?: @furom https://docs.netgate.com/pfsense/en/latest/releases/index.html#current-and-upcoming-supported-releases Thank you! Of all places i looked, documentation was not one of them :)

@CrowFather May have answered this on Reddit…? Just reinstall from ISO and restore your config backup. Fastest way forward.

@emefff That's kind'a as expected , based on my experience when upgrading to Plus 23.01 That's also based on FreeBSD v14 My home boxes uses i5-5250U , that CPU is to old to use the new "Speed/Power stuff" so those behaved as usual, using the "Old Power settings" But my i3 test box was "hit" , and was what i described in the thread i pointed to. /Bingo

Thanks a lot

@pimpmyrouter Yep agreed. SDWAN and Multi-WAN(with tiers) just isnt the same thing. But i dont think pfSense is meant to be in the SD space anyway.

So you mean the credentials pfSense uses to connect to the LDAP server? No, that is contained in the pfSense config. It would be rewritten from the config at boot or when any change was made to the authentication system.

@coxhaus said in 2.7 RC DNSresolver does not work with routed vlans on Cisco L3 switch: None of my Apple devices are responding on my Apple vlan What's your Apple vlan, a switch? Apple doesn't make any network switch...oh, it's a Cisco!

Not sure at this point. We'll update that ticket as we know more.

Yes it depends on the modem. If it has a route to the pfSense WAN you don't need to do anything. Some modems do not and require you NAT to their subnet so they can reply.

@leakin

I've found the answer,because the network burst every 3 minus. [image: 1688057503973-network-resized.png]

Hmm, do you have any traffic shaping enabled? I assume those are igb NICs?

@stephenw10 Thanks for your answer, I understand now the problem

@stephenw10 At the risk of jinx'ing it, I'm going to declare the situation resolved by upgrading to 23.05. My box has been 100% stable for 34 days now which is 20-30 days more than it ever would on 23.01 before crashing with a hardware error. So something is better in 23.05 on my particular 6100 :-) Looking forward to 23.05.1 with the IPsec fix it includes :-)

Ok, well you likely could also correct it by converting A2 to routing only and leaving the VPN on A1 which might be easier for you with all the other clients.

@tjabas said in No-ip auto confirm?: i have installed this plugin What did you chose ? Are you using a docker (whatever that light be) ? A debian setup ? Installed where ?

@jimp Thank you for the info. After upgrading 3 units to the RC, everything works as it should

@johnpoz said in Need help - can't reach website by FQDN or the IP Address: Maybe that fqdn should only be used in the US? Yup, that seems possible.

@stephenw10 Thank you, I can live with what it is. elmo