@Wepee: Can someone able tell me as to what cause this "notice" to alert me every now and then? Here are some thread you can review - https://forum.pfsense.org/index.php?topic=60146.0 https://forum.pfsense.org/index.php?topic=70558.0

Hi, See the same (like) behaviour for the (open)VPN (users) graph. I have seen the first time I logged into the openvpn as a (usercount) spike, but subsequent logins do not show. (it shows a "0" flatline) Rudi

Never worked with any of the 1.8.x m0n0wall configurations.

Can you enable 'desktop mode' in your browser on Android/iPhone/iPad/etc? I know that enabling that in Dolphin Browser for Android will show the same pfSense theme that's shown in Firefox on my desktop.

@doktornotor: In the order of (my) preference: 0/ Use IPv6. Problem solved. 1/ Use some VPN. 2/ Use NAT (need separate port for each device) 0/ but don't use a /24 of v6. (Don't worry, you won't get a routable /24 of v6.) 1/ he was asking about OpenVPN 99/ this was '2', but NAT sucks so hard that I demoted it.

ZFS is definitely not related and not used at all…

Same here. I've created a group called "admins" in LDAP and I'm getting successful auth, but no group matching. Edit: I've tried creating a new group called "RouterAdmins" in both LDAP and PF. Additionally I've told PF to look in the the groups portion of the tree to find the CN's for groups. Hack that worked but I don't like it. I added an attribute to a user I'm testing with, and made it ou… cn=RouterAdmins,blahblah. PF picked up on that and matched the groups up.

@ptt: https://github.com/pfsense/pfsense/tree/master/usr/local/www Thank you very much :)

Looks like it's from that failed log line parse that happened. We're completely overhauling the log format for 2.2 so it won't be an issue there.

@GruensFroeschli: The + will only show up if there are actually interfaces to assign. Since it does not, i suppose the interface on which the ADSL modem is connected is already assigned. Boy, do I feel stupid right now. This was it! Thanks.

Thanks for the reply! I'd think about updating but I've inherited this thing from a long chain of people who never touched it because it "just worked" and now nobody knows what the hell is going on. I'm loathe to just wing it since this is a "production" service and taking it down is really going to tick people off. As for clog:``` clog /var/log/lighttpd.log

For any others experiencing this issue,  I managed to resolved the problem by reducing the PPPoE MTU from 1492 to 1452

You might want to disable auto CSRF…