That seems to be a poorly functioning behavior. I like the fixed menu on the desktop browser, but I guess I have to turn in off if I ever have to adjust something remotely from my phone because it's unusable.

Its related to Suricata and Unbound...

Deleted the blocks and restarted Unbound.

Then the package updates showed as they should.

@nogbadthebad said in Logfile Filter:

[0-2][0-5][0-5]

That might miss stuff? Its not a mask.. so for example 167.x.x.x ?? Wouldn't it be easier to just do !: for say source IP, any IP with a : in it would be excluded - so all you would see it IPv4

@gertjan Here is the new certification in the new VM.
c3442ea5-d402-414c-a0a9-fadd3d4f4d4f-image.png

@stephenw10 said in After 2.5.0 update, Dashboard never receives update statue for version:

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

The bug report title is: Disabling 'State Table Size' prevents other data being displayed
So don't do that. 😉

...or use the patch linked there is you really don't want the state table size displayed before p2.

Steve

It's a known issue but there is no real workaround.

Resetting the logs also resets the dmesg.boot log which is what gets parsed to check CPU flags for things like AES-NI among others.

See also: https://redmine.pfsense.org/issues/11428

@johnpoz I tried accessing web UI from the LAN device to IP 192.168.1.1
I also had tried from a device on the WAN accessing the router assigned IP of 192.168.1.30.

Neither worked.

@dennis_s ty i will read up.

update: patch applied and working thanks again

@jimp ok, will do in a few minutes

Edit:
Created - https://redmine.pfsense.org/issues/11510

@jimp said in Command Prompt output in WebGUI 2.5.0:

"top" requires an interactive console to output data on a continual basis. It can't work through the GUI. Since there is no active terminal, it only returns the header info.

Thanks - on 2.4.5. I could at least see the "frozen" process tree. Its only cosmetic - if I have a real problem I go to the ssh console.

Thanks again for your time (in these days)
and regards,
fireodo

@bobbenheim Excellent, thanks. I didn't know about the bug tracker!

@gertjan Thanks, this does make sense.

So essentially the key is to treat WebGUI session like any other regular traffic and configure as needed using firewall rules.
Thanks for pointing me in the right direction.