@thomasbredman:

No access to console. No cable.

Normally, you don't need a special cable.
First thing to do when you take possession a 'system' : (whatever system : your router, the fridge, tv-set, etc etc ) : activate ssh access. Because this is the 'real' admin interface ;)
Other explication : when you modify something on your main door, check-out FIRST your secret back-door (the same ssh access).

Btw : when you use something like this https://www.netgate.com/products/sg-1000.html I wouldn't use it before i has this special cable …. (locking myself out, well .... I know .... seen that - been there)

Ah, that one.

Mine is checked.
But I never actually use the 'usb keyboard' and 'vga screen' (I'm using an old Dell Desktop PC as device).
Accessing pfSense using the GUI and / or SSH ( Enable Secure Shell checked - Disable password login for Secure Shell (RSA/DSA key only - checked , means no password, but keys to login).

The GUI is asking for login and password, as it does always. "password protect console screen" checked, or not.

Good new : your setup (parameters) is causing this ;)

Ok good to know. It's been a year since I did the initial setup of this thing so my memory of the defaults is a little foggy. The naming of the CA led me to believe it was a default config.

Anyway, thanks for the reply.

You can close this topic now

Thanks Jim! I did a renew and it picked it up straight away! I am now running on the "prod" cert with my handy green padlock. Great work to the pfsense team!

I don't get it neither.

Unplugged my WAP300N(sorry I write the wrong number previously) was one of the first thing I do.

I reinstalle my pfsense from zero with a 2.2.6 version(I only have a 1GB CF card and the 2.3.x need a least 2GB for the nanobsd if i'm correct) I will try with a serial tu usb cable today and if I can have access this way I'll buy a bigger CF card. For the AP I already buy a new one (Unifi AP AC PRO).

Thank you Gertjan for your time!

On an ordinary LAN, all the devices should have IP addresses in LANnet (the LAN subnet defined by the pfSense LAN IP/CIDR). In any case, the firewall is only going to receive and respond usefully to devices in LANnet. So packets in LANnet are all that needs to be passed.

If you have a more complex setup for some reason, that has other private subnets reached via static routes to another router that is on LANnet, then pfSense LAN could receive packets with source addresses that are not in LANnet. So for that case you need a pass rule wider than just LANnet to let traffic through.

@chicago_cs:

Posed thus, I can not remotely access the webGUI (HTTP) with the URL http://guard.mipagina.com

A default pfSense, with one firewall rule on the WAN interface (redirecting anythhting, port 80 to the firewall ( == pfSense) itself,
or
A default pfSense, with one firewall rule on the WAN interface (redirecting anything, port 443 to the firewall ( == pfSense) itself
and the GUI works from the entire planet.

Of course, if there is another router in front of pfSense, more rules are needed concerning these other routers.

But, such a situation actually never exists.

The real solution is : Use (the build in) VPN.

Btw :

I have created a WAN rule that allows access from a Web Address to another Web Address (guard.dyndns.tv) on port 80.

Can you detail that one ??
(do what others do : post a screen copy of your WAN rules).
The "rule that allows access from a Web Address to another Web Address" seems scarry to me.

Always : make everything work FIRST, starting from a 'default' system.
(and then blow your install out of the water with package like squid or whatever … This way you know what to do to make it work again ;) )

I think both the plus/minus offset graph and stats and the absolute offset graph and stats are useful.
The plus/minus offset average gives you an idea if the offset drifts around but averages close to zero.
The absolute offset gives you an idea of how much off it is, regardless of plus/minus.

So I added the absolute offset stat to the display.

Redmine https://redmine.pfsense.org/issues/7548

PR https://github.com/pfsense/FreeBSD-ports/pull/354

NTP-Graph01.png
NTP-Graph01.png_thumb

@phil.davis:

I checked on 2.3.4-RELEASE and 2.4-BETA.

In 2.3.4-RELEASE it always shows all the top menu items, even if they are empty.

In 2.4-BETA empty ones do not show.

So what you want is coming.

Hi phil.davis,

OH, I've seen the differences of 2 versions, thanks support for me.

Go to System->User Manager, edit the user that you are logged in as. See if the Custom Settings box is checked.
If so, then that user has their own set of custom webGUI settings, which includes the theme. That user has a different theme selected from the default theme (which is selected in System->General Setup)

This quirk still exists in PFSense 2.3.4.

As said above, it has nothing to do with pfSense. The request is coming from your PC.

@NOYB:

Is there a save button at the bottom of the page?  If so, after making changes, click it.

Thanks NOYB.  Just upgraded all my 2.2 boxes and still not familiar with the 2.3.x interface.  I was having the same issue and missed the 'Save' button lighting up.

I can confirm the patch works. Thanks again!

Cheers,

Keith

PR https://github.com/pfsense/pfsense/pull/3707 adds the ability to customize the widget title, for widgets that currently have any customizable options.

(For widgets that do not have anything customizable, the user is not likely to want/need to change the widget tile. And widgets like this do not have any of the code to show the "wrench tool" and open the settings panel. I was basically too lazy to add that to those widgets.)

Ah yeah, much better. Thanks..

So I just had to save a change on the General tab and it reset to 4 columns now. How can I override it till this gets updated in a snapshot?