I have modified Steve's solution as follows and it works on [2.2.2-RELEASE]: /etc/rc.linkup interface=opt1 action=start Matt

If you are using pfSense 2.2.2 the log format is very different from what is was when that blog was posted. Have you installed version 2.0.2 of the the TA-pfsense Splunk add-on?

I don't know if it makes a difference either way but personally I would get a standby unit fully working with everything you need in the way of packages, and then rely on config.xml to update it to current rules, aliases, URLs etc.

@Cornelp: @tim.mcmanus: @Cornelp: @tim.mcmanus: You can ssh from your Ubuntu box to your pfSense box and then pull the log files down from there.  Not too tough to do. Is there a way to do this automatically? Thanks… Sure, write a shell script in Ubuntu and add it as a cron job.  You alluded to this in your initial post, I merely provided one method to connect to the box. Could you possibly either point me to how I can accomplish this, or maybe you know how to create such a script? I cannot use logrotate as others have stated, because im trying to copy syslog files, and how logrotate works does not do the job properly. Does anyone copy their syslog-ng log files from their PfSense firewall to another server, for safe-keeping, and how do you accomplish such task? Thanks… I'm not going to write a script for you, but I can offer another suggestion:  Set up another server as a syslog server and point pfSense's logs at that.  They shouldn't rotate and can be kept into perpetuity (disk space pending). I purposely do not keep any logs longer than I have to because it can be a liability (adjusts tinfoil hat).

The log files maintained by pfSense are binary circular log ("clog") files. If you make a plain text log on your own, there isn't a way to have pfSense manage that log in any way (rotation, size limit, etc) at the moment. Perhaps with the syslog-ng package, but I haven't tried that.

Thank you guys. Sorry, I didn't see it when I searched.

see post-reply #1

So you have no firewall logs at all then? Sounds like you've disabled all logging, or at least logging of default block and other rules. Turn on local logging again, and make sure default blocks are all logging.

test

Seems to be more of a HP issues at this point… Will work with them. Thank you for all the advice... It did help to clarify some things for me. Sincerely, Kell

Squid and limiters don't work together.

@NOYB: Though I'm not sure why this Thu Apr 9 date though and whether or not it is an indication of a problem. That's the date on which it was compiled … looks like you are using pfSense 2.2.2

@cmb: Check the "disable" box for the instances you don't want to run. Otherwise they will be started during boot, and at a variety of other times while the system is running depending on what you do to it. Thank you cmb. I totally forgot about that setting. Appreciate your help.

Yep. Agreed. Something for me to experiment with now and create a proper DMZ.

@Supermule: I get the same on VMX0 (vmxnet3) driver and the console is flooded with timeouts. Changing the VM to E1000 NIC instead makes it go away instantly. That has no relation to OP's issue, please post your own thread if you'd like to pursue (and if you're still running some ancient ESX version, upgrade it first).

So you have 2 vlans already on eth2, vlan 10 and vlan 20 - and now you want eth0 to be part of vlan 10, and eth1 to part of vlan 20? Dude if you need more ports in your vlan - connect to a switch with the port configured for that vlan.  Interfaces on pfsense router are NOT switch ports..

I guess…I don't see anything else really on the upgrade guide that deals with potentially outage-causing issues like this, and they have whole sections on HA considerations. You could also say, most people doing HA already have lagg groups configured. And while that is also true, it also doesn't excuse the omission of this critical piece of data. Thanks for the followups and suggestions though, I don't mean to sound ungrateful, this is just a bit too sloppy for what I've come to expect from the pfsense team.