My ISP supports MLPPP, as I said, its working… Both links are up as per my ppp.log I would just like to find a way (and maybe I have to parse the log and create my own widget) to show current link status per ppp connection.. [wan] Bundle: Status update: up 2 links, total bandwidth 128000 bps So I would assume that the ppp.log would show if a connection goes down, and when I get a chance I will take one down my unplugging the phone line and see what the log shows.. Not sure if its only on initial connection, or on some fault that it is updated.. But before I went and reinvented the wheel, I wanted to make sure there wasnt a package/script someone else had made to do the same.

Yup, you're correct.  If it was done right, it would be working. Turns it was an IPSEC phase 2 configuration conflict.  I had one of my techs build the tunnels and he decided to use a /16 to summarize the 192.168.0.0 networks in the phase 2 entry.  So the firewall was trying to IPSEC everything.  Fixed the CIDR notation to get away from the networks in use locally on the firewall and all is well now. So yeah, you know, just configure things correctly and things will work…  :D

Rumor has it that the problem was solved yesterday, and we will test it in production, at the start of next week. Solved with adding VIPs as you said Stephen, i will write a status and follow up on this when its in production, with the resolution incase someone else misconfigures the same way i have and stumples on this thread later. Thank you for the help :) /shh

The feature request is specifically for  'auto-disconnect'. There are a lot of providers which charge based on the connection time. So there is a need to bring up and down the ppp session. And ignoring this request is a deal breaker for some of us.

Upgrade to 2.2.4. Looks like you're losing power and ending up with corrupt group and/or passwd files, which is fixed in 2.2.3 and better in 2.2.4.

@cmb: Is the WAN actually link flapping in that case? See re0 link down/up messages in the system log, see the modem and/or WAN NIC losing its link light? Apologies for being unclear. No, by those tests it was not flapping. I usually have a small switch between re1 and the CM to prevent exactly this and dhcpv6 annoyances. I tested both with and without the switch in the middle and the result was the same. (re1 - WAN on the APU2 - and the CM Ethernet port are the only things on that switch.)

In the docs you find some points that should be checked in that case: https://doc.pfsense.org/index.php/Unable_to_Access_Some_Websites If the Router is connected to the ISP there's often an adjustment of the interfaces MTU required.

Well tested it so far with 2.2.3 and its killing off the internal interfaces states in effect working as I'd expected it to work doing the same youtube test as before, but as I write its still not killed off the WAN interface established states some 20mins later with Firewall Optimization Options set to normal. If you have a fixed IP, I wonder if these wan side states will ever get killed off? I know those on a variable ip will get killed when the ISP forces a new IP address, but how will the fixed IP established:established states work if they have scheduled vpn connection between sites? Will we see a build up of established:established states or will they eventually disappear? Edit. The wan side established state to youtube got killed off after 25mins, so google/youtube keep their states open for 25mins, but the vpn situ will be an interesting test.

Shrug; will probably sit there for ages… I essentially gave up on any remote syslogging - unless you have all servers running pretty much the same OS, you always end up with messy crap. Plus, the syslog daemon on pfSense is not exactly a masterpiece when it comes to remote logging (#1940 and others.

The default is checked (disabled), where you had it unchecked it was enabled. That's not the most clear config setting, need to make that description more clear. Glad that took care of it.

@doktornotor: Have you seen this checkbox? As a matter of fact : I saw it. Unchecked it  :) I'm syslogging to a 'huge' NAS, so it never bothered me, this httpd flood. They were just there so they remind me that 'something has to be done'. Now, my logs dropped 75 % in size  :)

No, the WAN in this case is just another private network that my laptop that I'm using for testing resides on. The private IP space from the WAN is valid in this case. I'm simply trying to use PFSense as a router to route the traffic coming from my 172.16.6.0/23 network(The Wan) to my isolated MGT1 10.222.200.0/24 network. I don't want to disable natting and SPF except for a last resort.

OK, I'm sorry guys… I did everything again and I found this option: "Allow remote access - Remote access allows you to manage the AP from the Internet or from a different LAN. To enable remote access, the gateway device needs to be properly configured, such as opening a port for the corresponding IP address of the AP." I didn't check that option the first time. Now It's running well ;) Thanks! At least, I checked my design with you. I hope this will be useful for other users. Now I have to focus on rules ;)

@kejianshi: Is your POS pfsense rig working ok? Runs good. Ordered another!

Genius!  THANK YOU!!!

@phil.davis: 1. The unit is supplied with instructions about where to find the "tuned" image if you need to reinstall completely. And it will look in the special place for updates also. The "community" one works also. I am running that, as it happens, because I often follow the bleeding edge with development snapshots. I believe the "tuning" is things like the content of loader.conf.local but nobody is saying officially. 2. There is no "tuning" in the config.xml AFAIK. You can certainly import a config from elsewhere, reassign interfaces as needed and run. I did that on the 2 SG-2440 that I have in production. Awesome, thank you Phil for the information. I am excited to get it delivered. Hopefully should be here by the end of the week Cheers! Jon

Nested aliases work fine in general. You wouldn't be able to reach this website if they didn't. Check your table contents under Diag>Tables for that alias to verify.

Found out it was just a server that was behaving abnormally. Rebooted the server and all is good  :-X Noticed it by looking though pfTop after logging into the console. Thanks for the help!