The beauty of RRD is that the files do not grow over time. You set a limited size for each data file and never exceeds that. They do seem to grow initially, presumably from a completely empty file, but you shouldn't run out of space. However you can move /var to another media. See this post for a similar project: https://forum.pfsense.org/index.php/topic,67823.0.html Doing this will not get you any further RRD data since, as I said, the files are fixed size but it should free up valuable RAM on the Alix. In nanobsd the RRD graphs are periodically written to the CF card. Since yours will now be on non volatile storage you can adjust that period to some thing very long (maybe disable it?) if you wish. It's in System: Advanced: Miscellaneous: Edit: Looks like you can disable it completely there. Interesting project, let us know how it goes. Has anyone else done this? Steve

No, after writing that post I did some reading and also failed to find the right info. None the less people have used it, there threads here detailing what was required. Edit: https://forum.pfsense.org/index.php/topic,46525.0.html You could try forwarding port 3483 to the Squeezebox server. If the discovery packets are sent to the broadcast address they will hit the interface and should be forwarded. Whether the server will respond or the client is then able to deal with a server in another subnet is anyones guess.  ;) Steve

No problem.  :) To make the firewall rules easier to read you may want to create an alias that contains all your internal subnets, 192.168.200.X, 192.168.10.X etc. Then you can make firewall rules on each interface the allow traffic with destination: not internal subnets. All other traffic will be blocked by default. Steve [image: wifi2rules.jpg] [image: wifi2rules.jpg_thumb]

That could do it. Yes try one of the 2.1.1 snapshots. Go to System: Firmware: Updater Settings: Check the box for a different URL and enter the appropraite URL for your box (32 or 64bit) http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/amd64/pfSense_RELENG_2_1/.updaters/ http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/i386/pfSense_RELENG_2_1/.updaters/ Check the box to allow unsigned images, only the releases are signed. Steve

The packet capturing when you select Filter "All" was fixed up by this commit - https://github.com/pfsense/pfsense/commit/6901d6af97920f816b4dfc1b6d7efebda0bd7633 - and will be in 2.1.1. Try and see if it helps for your situation, transparent mode.

@phil.davis: Normally the "DMZ" is just another ordinary LAN, that happens to have some servers to which public port/s are forwarded from WAN1, WAN2… The DMZ does not have an upstream gateway to the internet on its own subnet. The upstream gateways are on WAN1, WAN2... through which the internet is reached. So do not put a gateway on the DMZ interface. You cleaned it up by going back to a previous config - that works! For others, if you do not easily have a good previous config, remove the gateway specified in the DMZ interface, then go to System->Routing, select the real WAN as the default gateway and delete the DMZ_GW. General rule: If an interface is to an internal LAN (i.e. usually with private IPs) then do not put a gateway. If an interface has an upstream device that is the way out to the internet, then it is a WAN and should have a gateway set. Phil, Sound good! I did see a DMZGW listed under GATEWAYS but I did not find a way to remove it. I will definitely keep this in mind. Thanks for the quick response and heads up!

I'm going to get the most available, but I'm not sure yet what that is. I've been trying to find different options. My goal is to have equipment that can handle a high amount of bandwidth, even if it's not available, so that when it becomes available, we can just connect a better connection. Everyone is interested in building the best possible arrangement, within reason of course. Thank you for your response!

You will have to use VLANs to do that. Put a VLAN switch in place of the ordinary switch (hub) on the first floor. Then you can have 3 VLANs and trunk them on 1 cable back to pfSense. If you are happy to run 100Mbps VLAN trunk to pfSense, then a 100Mbps 8-port VLAN switch is not so expensive.

Yeah why not?  VM is just like any other copy of pfsense running on actual hardware.  But comes down to your connection - is this VM running on the workstation your using on the lan?  If so then really kind of completely pointless to vpn to yourself, etc. Are you setting up the firewall rules to allow your vpn traffic?

Thank you,  Just what I needed. :)

Yup if you don't have smart switches, if you get the mac of this rouge you can look up the maker via a mac vendor lookup site - just google for one. Also - I would change your pfsense lan IP to something else vs .1 for quick fix.  Also IMHO, using .254 and .1 if your going to use 192.168.1.0/24 as your network is prob not a great idea because lots and lots of devices default to these.  So someone brings in a switch, or a soho router, etc. and plugs it in and bam you have a conflict with your gateway device.

Turned on IGMP Snooping on my Zyxel GS1910 switch and on my DAP-2553 Wireless AP. I haven't seen the problem come up yet. So far so good. Thanks for your help, everyone.

pfSense cannot do this in it's default setup. You need a reverse proxy that can read host headers. I believe there are more than one available as a package for pfSense though I've never set this up myself. Have a search through the forum for 'host headers'. Steve