@stephenw10

I have loaded up 197 driver and will see how that goes.

@stephenw10 Well..it works 😊

I created a VIP on the pfsense.
Created my backend pool
Created my tcp front end.
Created an ACL matching 0.0.0.0/0 and using the default pool for ldap

Works like a charm.

Obviously, for larger implementations, i wouldn't do this but if you are a small to midsize operation with a need for ldap, why not use pfsense with built in proxy to handle it.

@robbiett said in 2.6.0 & 23.01 netgate and custom HW. Web UI extremely slow when no WAN present.:

@stephenw10 said in 2.6.0 & 23.01 netgate and custom HW. Web UI extremely slow when no WAN present.:

This might be better served as a new feature request for an off-line config mode or similar.

Steve

When done, send a copy to Microsoft for attention of the Windows Installation team. 🫠

☕️

Use no@thankyou.com and it will error out and let you continue locally for home. For pro, use domain join. However the best solution is to install linux. 😀

@stephenw10
Hello,
I put another server VM .2 in the same subnet as .1 server and after many attempts i reached to reproduce the latency with pcap and faced the same ACK latency ; so the PfSense is not in charge...i thought that becasue latency appeared when i set it up, weird coincidency.
I think i have to investigate on my vmnic configuration witch was made by a supplier, because .1 and .2 are on 2 differents ESXi hosts, despite that i am up to date on all drivers, patchs and others on my VMWare Infrastructure and on my core switch.
Thanks a lot for your help and time.

Any ideas anyone?

@hwally Does your ISP device require you reboot it when you change devices?

@stephenw10 Thanks Steve!

I was able to reproduce it.
I'll apply this patch.

PHP errors

PHP ERROR: Type: 1, File: /etc/inc/util.inc, Line: 2208, Message: Uncaught TypeError: round(): Argument #1 ($num) must be of type int|float, string given in /etc/inc/util.inc:2208 Stack trace: #0 /etc/inc/util.inc(2208): round('', 2) #1 /usr/local/pfSense/include/www/bandwidth_by_ip.inc(172): format_number('', 2) #2 /usr/local/www/bandwidth_by_ip.php(36): printBandwidth('wan', 'local', 'in', '', 'iftop') #3 {main}

Ok got it sorted.. The "IP Passthrough" state wasn't being recognized on ATT's end, and had to be reset by them to get it to apply, even though I rebooted it on my end. Thats what they tell me anyhow...

I suspect a resent power outage we had somehow messed its configuration and reset it or something.. A theory anyway...

Thanks for the responses all, much appreciated.

Also upgrade from 2.4.5p1 --

Outdated signature.. fixed now. thanks..

@cool_corona thank you for the pointer... I shall investigate!

@johnpoz Hm? It doesn't throw any error when this outages happen, but occasionally Spotify is unhappy with my network rules I suppose, telling me to check my network and refuses to leave that screen. I then have to reboot the player, then works just fine again...

@machu-picchu I did exactly this using two VM's on EXSI when I was testing PF latest release.

...or at the console directly.

@bob-dig said in Can't access web-UI after upgrade from 2.7 to Plus 23.01:

Maybe just bad timing on my part but I got me a VPS the other day and am installing pfSense 2.7 on it. After doing the upgrade to plus, I can't access the web-ui anymore. The VPS only has one NIC.

Can I force an upgrade to the latest RC of 23.05 via ssh?

@stephenw10 said in HELP! pfSense is dead after upgrade to plus:

Like you went from CE 2.7 to Plus 23.01?

That's not valid unless it was a 2.7 snapshot from Feb 15th or earlier because of the php change. You should be able to recover by running a full forced pkg reinstall if that is what you did.
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#forced-pkg-reinstall

@spacebass said in registered for pfSense Plus, no upgrade options from CE:

not to be obtuse, but I have a limited amount of time to fill out the same form.

Most likely you have a plug-in that is making it not work -- it has worded in all browsers and on all major platforms internally following your report.

Could be a DNS issue. But, again, we did thorough testing after your report and could not replicate it.

@stephenw10 Thanks :) I'll give it a try and see how it goes.

root@pve2:~# cat /proc/cpuinfo |grep microcode microcode : 0x24000024 microcode : 0x24000024 microcode : 0x24000024 microcode : 0x24000024

@burgerking31337 after I upgraded my Proxmox machine to latest intel microcode (not debian's latest, the actual latest), I never have a single reboot on any VM.

@stephenw10 sounds good. Thanks for checking

It's trying to open pages that don't exist in pfSense. It probably was previosuly connected to something at the pfSense IP and hasn't updated yet.