I hadn't seen it. I guess I am only as good as the search terms I use. :(
Thanks for the link.

Jim

Ok, solved it by resetting the firefox profile… clears all my addons and stuff, but works now.

alt + f, navigate to Help > Troubleshooting Information then click the Reset Firefox button.

Best regards,

V

@jimp:

Do you have any packages installed on the system?
If not, for curiosity's sake, does that error go away if you install one (something small like Cron would be sufficient)

Hello,
I did what Jimp suggested and it works fine. The Services Dashboard is now properly displayed.
Thank You.

Does the checkbox at the bottom of this screenshot not do what you want?


F1 Boot Prompt Duration
https://forum.pfsense.org/index.php?topic=78439.msg427844#msg427844

Hi Steve!
you are perfeclty right!
I have Dns forwarder enabled, and I've seen the description (under dhcp server -> Dns servers):

NOTE: leave blank to use the system default DNS servers - this interface's IP if DNS forwarder is enabled, otherwise the servers configured on the General page.

but I admit I didn't understand the full meaning: maybe that "dash" misleaded me….  :-[

Thanks again for your reply!!
Aronese

Thanks, I've applied the patch manually to my systems.

What are you doing that means you can't select option 8?

Steve

Exactly!

The pfSense firewall blocks connections from the WAN interface by default. To access the pfSense webgui from a client connected to the modem/router you need to do two things:
Add a firewall rule to the WAN interface to allow the traffic. This can be quite restrictive, just the your own IP allowed for example.
Make sure you have unchecked 'block private networks' in the WAN setup page. Your WAN is in a private network.

Steve

@KOM:

"308% packet loss??  LUXURY!!

I must admit I'm spoiled with my ISP for a home gateway… 160/8 isn't that bad  ;D  But shhh... don't tell them  ;)

Chris was tied up getting the pfSense University training curriculum and related materials ready to go for the first classes, which happened this past Fri/Sat. We're looking into options to make up for the missed hangout, stay tuned.

Arfff…

Ok, If I've correctly understood, I do not use the correct command, I must use /sbin/shutdown -h now, like in Linux.

Thank you KOM.