There are at least thee different things, and different types of logs, that you may be talking about.  Can't tell without more info. Bandwidthd data files (*.cdf) are stored in /usr/pbi/bandwidthd-amd64/local/bandwidthd. (Adjust if needed for i386).  To move those, I first would install bandwidthd on the new server, then copy the old *cdf files as well as the old etc/bandwidthd.conf to the new system.  Files in htdocs should be created as needed. System log files are binary in a 'circular log'  format, and live in /var/log.  In a console you can generate plain text by using the clog utility, ie "clog /var/log/system.log |less".  No sense, IMHO, in copying these to a new system. The rrd data files are used to create the rrd graphs you may be referring to, and these live in /var/log/db.  I'm pretty sure there are ways to back up the rrd data, and I think they are moved automatically when upgrading a system, but I'm not sure of the correct way to move old data to a new install with a potentially different configuration.  They are binary, so if you are going i386 to amd64, they are not compatible.  There are ways around that, but require some manual intervention, essentially a dump & restore.  Maybe somebody can chime in with proper way to move rrd data.

See comment #34 The ‘free’ AMIs are gone. We dropped the price on the remaining AMIs. By paying for the AMI, you help support the project.

@hec: Last time i tried carp with vmware we had a lot of packetloss and a the vips did not work. You have a config issue at the ESX level somewhere in that case. Those possibilities are all outlined here: https://doc.pfsense.org/index.php/CARP_Configuration_Troubleshooting#Hypervisor_users_.28Especially_VMware_ESX.2FESXi.29

If all you want is a proxy style VPN then pfSense just needs one NIC, the WAN, and a VPN set up to tunnel all client traffic and NAT it out of the WAN interface. However I would recommend having a LAN interface so you can manage pfSense without allowing WAN traffic to reach the web GUI.

https://doc.pfsense.org/index.php/Upgrade_Guide#Disk_Driver_Changes

how did it work?

it seems when the tunnel is started that time the rule works fine but after a while when in idle state or the states refresh, the tunnel still remains up but the rule doesnt seem to match the traffic and send out of the tunnel gateway. can any1 please help or point me to any bug that was introduced in 2.2.1 or probably fixed relating to this. i tried creating the aliases and rules from scratch but the issue still persists

pfSense will do vlans just fine. In fact it will do everything DD-WRT does and then some.

Easy fix for that: https://doc.pfsense.org/index.php/Boot_Troubleshooting#pfSense_2.2_and_later I assume you're running a cf card in older hardware. Steve

Hi, I upgraded to 2.2 from the Web UI after a successful installation of 2.1.5 and it works. I've got pfSense running on my net6501 and I'm really impressed so far with this project. However, out of curiosity I tried the latest 2.2.1 release to see if this problem is still present–and it is. A USB installation using the memstick serial image does not work on the popular net6501 boards. Details at the beginning of this thread. I think this deserves a bug report. I'll prepare one soon unless someone advises me otherwise. -- GH

Good to know.

Note down the interfaces and their purposes exactly Dump the config Wipe the box Install ESXi Create the networking (vSwitches) Enable allow Promiscuous mode on the vSwitches that pfSense might need it Create a new VM (FreeBSD 64 bit) with the correct number of NICs (VMXNET3) Copy the pfSense ISO to the datastore Mount the ISO and boot off it Note the MAC addresses of the vNICs and which vSwitch they are connected to Install as usual At the console set at least the LAN address Connect your browser to it Restore the config Re-assign the interfaces Reboot Job done Cheers Jon

If you have a notebook available to be repurposed that can be a really inexpensive route (pun).  And as a bonus includes UPS and console.

Thanks for the direction! :) Bummer though its not compatible just for anyone else interested.

Yeah it was. Changed with 2.2.

That configuration is the opposite of ideal.  Also, how are you measuring latency?

Well I set my clients to 8.8.8.8 and 8.8.4.4 when I had them disabled, and I have no issue when I use the schools wifi. I used both resolver with forwarder (setting) and just the forwarder. Was upgrading from 2.2 to 2.2.1. Resolver settings: Default + I had enable DNSSEC, Forwarder, DHCP reg, Static DHCP. I have been using pfsense at my school for that last 2 and half years with no issue (did change hardware from a netbook after the first year), I have always had all the settings setup to handle double NATing, and I so get a reserved IP (10.X.X.X) and it comes from just a jack in the wall. Update: I disabled DNSSEC (even though google supports it) and the seems to help though it might have been mostly pasubio since I re-enabled it and nothing has really changed. After a few days the problem has seem to have mostly gone away. Something will take a little bit longer to load or some elements will still go through the can't find, then found cycle. It almost like the DNS cache was wiped and then it had trouble re-populating it.