@jimp Almost all of the clients are (heavily) active during the screenshot. NDP does indeed have the MAC addresses and all the devices have associated hostnames. I can get all the correct details from the CLI and there is nothing amiss with IPv6, NDP, dhcpd.leases or dhcpd6.leases (or with IPv4 either). With the CLI I can see that everything is working as normal/expected - not so with the GUI Status display. It's only the sparsely populated and incorrect status listed in the GUI that I am raising. Underneath the GUI everything is working just fine. ️

@Gertjan Thank you very much Gertjan I did the steps you mentioned by changing the port of http and it worked successfully. The proxy server is working normally now and at the same time I can access webgui of pfsense. Thank you again

@jimp said in Interfaces list longer than screen height: It's probably set to Fixed and you'll need to change that to Scrolls with page. Yes, was set to Fixed. This helps, thank you @jimp

@adeparker or try removing the "bad" section from the config file: https://forum.netgate.com/topic/180957/possible-bug-on-23-05-bulk-import-of-aliases-causes-full-brick-of-pfsense/7

@b_hammer said in Fatal Error: /etc/inc/notices.inc(101): fopen('', 'w') The file shouldn't be empty ( '' ) but '/tmp/noctices' What happened is : /etc/inc/notices.inc start be reading (including) /etc/inc/globals.inc and that didn't happen. The most important variables aren't set (unknown) and that breaks ... pretty everything. It's console time. Check free disk space. How to Run a pfSense Software File System Check (5/2020)

@provels said in Status--Monitoring remember the last setting: @insmod Display Advanced, Save View. That will (As OP requested) save the default view to be the current settings, but it's also worth pointing out that clicking + Add View will make a new tab for the current settings so you can quickly access multiple different graphing views without a lot of clicking/changing settings. So you can have a tab for WAN traffic, a tab for the WAN gateway quality, a tab for memory usage, etc, etc.

Thanks for sharing, works in 23.05

@insmod since pfsense is designed to be managed via the web gui, while some stuff can be done via the cli, ie either consoled in or via ssh. What you can do via management is going to be limited via that. Your best bet is to just limit who can access the gui.. Create firewall rules that only allow from say your management network, or admin machine. For example - the web gui is only available via my lan network, only devices on my lan are my main PC, and my nas - all my other segments have no access to the web gui via simple firewall rules blocking access to "this firewall". Dns and ntp is allowed, icmp - but they can not access the web gui port or any other service on the firewall, on any IPs be it its other lan segment Ips or even its public IP from lan side networks. example: here is a locked down segment that would have no access to the firewall gui, or anything else on any pfsense IP other than ping, dns and ntp. [image: 1686427145602-lockdown.jpg]

@SteveITS Got it,thanks!

It's a really handy feature now and I have already used it to diagnose something on the WAN side. A really helpful improvement on the original pcap function and I appreciate the effort people put into it to expand its functionality. ️

remaining images @FSSantanaJr [image: 1685011109877-05.png] [image: 1685011116032-06.png]

pfSense software does not include an API like that. You may have installed some kind of third-party add-on to act as an API, in which case you need to consult their documentation about key management.

@jimp Damn it. Should of looked further. We deploy Atera RMM and I have a scanning agent on that server/IP. I will take the router out of the scan. Thanks @jimp for catching that!

@jimp Thanks, i never used system patches package before. everyday is a day you can learn something new ;)

@steveits The problem seems to have been resolved but I am not sure why. I moved around and reconfigured a few of the widgets and rebooted late last night. (I swear it is harder to get "change management" approval at home than in an organisation of 7500 people ) I no longer get the error. Thus, it could have been (a) by moving around the widgets it "fixed" a corrupted configuration; or (b) there was something hanging around in memory/cached/etc. that rebooting cleared out.