@Supermule: When you max out your internet connection, then the traffic from Apinger gets in the cue. Thats why it reports GW offline. You saturate your bandwith and thats why it fails. He's not concerned about how apinger thinks the interface is offline, he's concerned how apinger thinks the interface comes back online and reports the wrong information. apinger has a known bug that gives false readings.

Check out the dashboard. Memory usage is right there.  If the % is high, memory is low.

Not really without captive portal, plus completely futile if done on blacklist instead of whitelist basis.

Hi, OK, got it working! But an upgrade will remove this on me … :-(. Here is what I did (and thanks to this post for some key help! https://forum.pfsense.org/index.php?topic=6087.0), The file I really need to change is /etc/ssh/sshd_config - but it is generated when sshd is started / restarted. The script that builds / creates /etc/ssh/sshd_config is /etc/sshd - so I modified that file, as follows,         /* Hide FreeBSD version */         $sshconf .= "VersionAddendum none\n";         $sshconf .= "SyslogFacility local4\n"; <== This is what I added, just one line ... so sshd logs to the local4 facility (the one I chose). Restarted sshd, and it worked! The log file is now the local4 facility (/var/log/portalauth.log, as noted in /etc/syslog.conf). Is it possible to make this an option (syslog facility for sshd)? Thanks!

Yep, later on you can set a password for the console from web UI. Finish your configuration first and you'll see.

"route anything 10.5.5.1/24 through 10.5.5.1 gateway" There might be some terminology misunderstandings with pass vs route.  For example, that looks a lot like the default LAN pass any any rule in pfSense: Pass IPv4 any source LAN net dest any any Note that rule would typically be on an interface with a 10.5.5.1 address. The actual route for that traffic is the default gateway setting on the hosts on 10.5.5.1/24.  And even then, the route isn't for traffic to 10.5.5.0/24, since that's the local subnet.

What firmware is the 120 on and what MRU have you got the 120 set to? 1492 is UK's, and I see there is a 1500 popping up. Coincidentally, I was supporting a now ex customer with similar setup and you would be the right timescales away to be the one's who took over from them, hence the "coincidentally" amongst other things, of course knowing what the spooks know, you could just be a spook playing me.  ;D Edit. This might also work for you. https://forum.pfsense.org/index.php?topic=86087.msg473517#msg473517

The log is already there. Help also : https://doc.pfsense.org/index.php?title=Special%3ASearch&search=captive Activate the Captive Portal on a dedicated interface … and you up. BTW: no help. A 'sys admin' should first learn how to maintain a system like pfSense. Its something you have to go through yourself.

Certainly nothing on the pfSense box. Completely wrong forum.

wifi routers being used as AP rarely support dhcp on the lan interface..  But sure if they support dhcp then he could create reservations - but they would still be outside the pool, reservations with pfsense dhcp server are always outside the pool.

Just an update on this, the password had nothing to do with it.  In fact I feel like an idiot, as the problem was a conflicting IP address.  I thought I changed the IP of the old router away from the new one, once done I changed the PfSense WAN1 IP.  Neither reported an issue, no logs on the PfSense end showed this either.  It has now been up and running for the past 4-5 hours without failing.

That's just dressing. You're vain. There 's no way to change this order at GUI. However, you can change it in the configuration file: Go to Diagnostic > Backup/Restore and backup the interfaces area. Open the xml file in your text editor and move the interfaces sections to your fit, save the file and re-import it. If you use CARP do the same on each machine!

Sigh. I'm merely suggesting proven tools designed for the purpose and providing pretty much realtime information. Javascript dashboard gimmick refreshed every X seconds is not one of them, not to mention that they - as you have already noticed - heavily affect the system resources.

@bl00d666: fyi i am on 2.2.2 but the alx module is still missing. something to do with the cut before the rc of pfsense or something. So to be clear, 2.2.2 does not detect your ar8171? alc is the proper driver for that chip, not alx. I've raised a bug in redmine asking to update alc(4), if it's not already in place for the 2.2.3 release. https://redmine.pfsense.org/issues/4725 [edit] Looks like that will not be included until 2.3, unless someone submits a patch, but r273366 should drop right in.

Sweet, i have been waiting for this fix as well. Glad it was noted as a bug. Its been an issue for a while like it says in the bug post. Really happy that a fix will make it to the next stable point release.

Ugh, I did save a copy before removing it from /var/dhcpd/var/db, by copying it to /tmp. As part of trying to get everything fixed (shotgun killing dhcpd processes), I wound up in a state where check_reload_status was spinning so I rebooted the firewall… forgetting that /tmp gets cleaned up on reboot :-( So I've managed to lose the evidence from this incident. If it recurs, I'll make sure I get a copy saved before I reboot. Thanks! Tim