Convert your WAN to another LAN for the time it takes you to get in and change things.

@mudmanc4: Thanks for the reply, and I should clarify to insure were on the same page: So would this require adding a route in the VPN client, to allow only the LAN subnet ? Reading what you wrote, I dare say yes, just pushing the route for the local LAN should be sufficient.

Sigh, found it. find / -name syslogd /usr/sbin/syslogd

Most likely BIOS (or "Legacy" boot mode on newer computers)… I don't believe pfSense (or maybe even FreeBSD in general) uses UEFI yet.

Alienvault has now release a pfsense plugin. Check out https://github.com/decay/alienvault-pfsense

Alienvault has now release a pfsense plugin. Check out https://github.com/decay/alienvault-pfsense

Alienvault has now release a pfsense plugin. Check out https://github.com/decay/alienvault-pfsense

It would be best to run your du command when your drive is showing full or nearly full usage. You can then drill down through the directory showing the most use until you get to the directory where the space is being used up. Otherwise it's anyone's guess where your space is being eaten up. Squid might be the culprit, though if your Postfix settings aren't correct your firewall might be queuing large amounts of undelivered mail - possibly system warnings(?).

Multiple things at 192.168.1.1 causing something in the middle (switch) to get confused by different MAC addresses?  Reason for asking is 192.168.1.1 is a pretty common default IP for lots of home network stuff.

@heper: on the general tab there used to be a field "bypass proxy for these source ip's' (or something similar) use that Thanks! That worked! Happy New year!

Thanks!! That solved it!

@tlf30: I would have never found the issue had I not followed your advice and reset it! But, my problem is one that I really don't like. The LCDproc-dev package is the one that causes the issue. If I disable it from the GUI, all interfaces start working again. If I enable it, it is like a time bomb waiting to go off and kill all of my traffic. Does anyone know a solution? Thanks, Trevor Is it possible you have LCDproc-dev as well as LCDproc (hanging out prior to the update)? They will likely interfere with one another.

At this point it's the second reinstall in a few months.  I'm ready to blame the hardware, starting with the disk because fsck just doesn't work.  It's a solid state disk. It's an Atom fanless box that was pre-configured I got on Amazon.  I'll replace the drive with a standard hardware sata.

Dude LAN never talks to pfsense to talk to LAN..  No its not the same thing..  Client on 192.168.0.0/24 doesn't talk to pfsense to go to 192.168.0.0/24 ?? Smarter way to create an alias for a list of networks?

If you're doing any manual ifconfig, you're doing something wrong. Maybe you're trying to manually configure IPs on things, which will get stomped on, and bypasses input validation that prevents invalid configs. Overlapping/conflicting subnets on multiple interfaces might be another reason you'd have issues along those lines. You're losing a link route for the IP where 'route get' shows the IP going via the default gateway.

Ok thanks bummer it doesn't go by the RFC. Doing syslog-ng is an ass