Squid logs locally to its own log, not syslog, so the remote syslog options do not affect squid's logging or reporting for sarg/lightsquid. I prefer lightsquid myself, but sarg can generate some more interesting reports. Careful with sarg though, as I have seen it fill up hard drives on numerous occasions when customers had it configured to keep many old reports.

Thanks,that fixed the error.  I had been sure that those prompts came up in the opposite order (hence my confusion).

Thanks for both of the tips! I have cloned my up to date slice to the other slice and moved settings to /boot/loader.conf.local.

I don't think installing a nano version on a flash drive larger than 4GB yields any benefit.

hi, I followed these steps.. /http://www.yawarra.com.au/tutorials/how-to-install-pfsense-on-an-apu

The most common cause of this going from 1.2.X to 2.X if I recall was a restriction in the character set being used that meant the config file is seen as corrupt. See: https://doc.pfsense.org/index.php/Upgrade_Guide#International.2FSpecial_Characters_in_1.2.x_Configurations Steve

The difficulty here is capturing the traffic you want to prioritise, particularly Skype traffic which can be on any random high port. Even if you've set it to use a static port that only counts for incoming traffic. If your clients are using dynamic IPs then you can't use that to direct traffic either. I believe you can do it using the Layer7 filter but I've not tried that myself. For example: https://forum.pfsense.org/index.php?topic=78092.0 Steve

Post your WAN firewall rules.  It works fine if you configure it correctly.

@stephenw10: It should boot that Nano image from an SD card but that won't allow you to install the SSD if that's what you're trying to do. Searching here the common cause of that is I corretly written card. What OS are you using to write the image? It looks like you're writing to a slice on the card rather than the entire card. Try using: dd if=/Users/me/Downloads/pfSense-2.1.5-RELEASE-1g-amd64-nanobsd-20140825-0744.img of=/dev/rdisk1 obs=64k Assuming /dev/rdisk1 is your sd card. Steve @Derelict: You have an SSD.  You should be installing the full image.  The only question is how you boot the installer. USB thumbdrive is the obvious choice, USB CD is probably second. USB thumbdrive: After recreating the USB boot drive with something else that isn't dd it worked. So that seemed to be the issue. Thanks for the ideas.

@stephenw10: You should put that in loader.conf.local no? Yes, always put user-defined things in .local so upgrades don't overwrite.

Interesting. I tried another one thing. I made a new CF card with pfSense 2.2 RC (perhaps 2.1 would behave the same) and after that I connected the CF card to FreeBSD machine and replaced the boot manager by following command: boot0cfg -B /dev/adx And it works! :-)

You can configure a single interface though. It's useful if you're running as a vpn server exclusively for example. If you do set only a WAN interface the default rules will allow access to the wegui on that interface. However as soon as you assign another interface the firewall rules are reconfigured to those appropriate for a firewall and you loose access via the WAN. That's what happened to you. Steve

We haven't even gotten to the problem of nothing on 10.10.10.0/24 having a route to 192.168.2.0/24.  At best, the router at 10.10.10.1 will issue ICMP redirects and it might work.  At worst it won't work at all without static routes everywhere.  Regardless, it's a lousy way to do things.

so, ping my LAN or my WAN that i have set up on pfsense? oh and i should probably mention that this machine has 3 ethernet ports, so no usb to ethernet. in fact im going to start a new thread to avoid confusion new thread at https://forum.pfsense.org/index.php?topic=86654.0

Original thread for reference: https://forum.pfsense.org/index.php?topic=86122.0 In the last post in that thread the result I was expecting was that there would be reduced or no connectivity at the dd-wrt box. The fact that there isn't implies that somehow the wireless and wired parts of the dd-wrt box are not connecting purely at layer 2. I'm not familiar with dd-wrt but it looks like you might have the wrong wireless mode selected. The connection shouldn't be routed. Steve

Maybe ask in the 2.2 subforum if it's still happening. I don't see anyone else asking sbout it so perhaps you're doing something unusual. Steve

It's in RC, many people are using it, some in production. It depends what your situation is really. At the very least by running it you can report any issues with your hardware you might find and try to get them fixed. Steve

Thank you very much for your help. Everything seems to work fine. We will replace the old hardware sometime in the future. Any news on when 2.1.6 will be available which includes the bugfix for the restore?