It works fine on a WRAP if you flip the bits as described here:
http://doc.pfsense.org/index.php/NanoBSD_on_WRAP

2.0 might be a little heavy on CPU/RAM for a WRAP but it might work. I haven't tried it on my WRAP yet.

Snort has a p2p policy category, would this help?

just a follow up..

I tried this
http://forum.pfsense.org/index.php/topic,10409.0.html

then

http://forum.pfsense.org/index.php/topic,6998.msg49266.html#msg49266

seemed to load the config.xml file, upon reboot webconfigurator failed again? (NFI) probably missed a step

resolve, just did a re-install from CD…. which fixed the web configurator problem, then restored from the same back up.... seems to be working again... one strange thing was during re-install of packages.. snort was reinstalled, then removed then reinstalled? (is it possible to have installed twice by mistake?) I only say that as it went through the 5% 10%...100% routine twice as I went a made a coffee and came back to find the message "removing snort" then installING snort 5%..%100.... no biggie!

True enough :)

If the additional IPs are routed to your main shared CARP IP, you can use the "other" type VIP. You'll just need to set them up on the backup unit by hand the same way.

Having the same issue, but I believe that practically it's not happening.

1.2.3-RELEASE
P4 2.4
2GiB ram
iwill based motherboard (SGS 5420)

Upload 1.0 Mbit/sec, Download 5.0 Mbit/sec
Uplink 1000 ms, Downlink 110 ms

nut - running
ntop - not running
apache_mod_security - running
snort - not running
ntpd - running
dhcpd - running
miniupnpd - running

Test run from LAN interface, have two VIPs and nothing important expect a port mirroring where WinPcap is always running but even without port mirroring I get the same exact results.

Bridged modem -> pfSense >-LAN-> HP ProCurve switch -> clients

@jimp:

@sofakng:

So the WWW network would be blocking it's own network?

That's not how it really works. The only address in the WWW subnet that will have a WWW subnet IP as a destination, is traffic hitting the router IP itself. All other traffic goes over the switch and not the router.

Ahhh, that makes sense.

I guess if I wanted multiple web servers to communicate on the WWW subnet I would need to adjust that rule but I think I understand what you're saying.

Thanks!

Ouw…. thank you for suggesting
80 GB that I use it only for the squid cache. if Mr. jimp suggest like it, I just follow the advice Mr.jimp.  ;D

Thanks.

@Spoonman2002:

hm, that did not work either…..  ???

No idea why my PFSense box cannot access internet.

Hello

my English is not good, helped me a translator, well, let's see you.

tested Bone default your modem to bridge mode, which utilis ip range your modem in normal mode. for example mine is 192.168.1.x/24. now, have tried without DHCP, bone that is static, just in case try it on static, the pfSense do not assign an address, now you have pinged your modem router, for example to get my modem router is 192.168.1.1 and from the pfSense console will do ping -c 100 192.168.1.1, if the modem router responds, it means that your connection is fine, and now if that does not go to the pc is because something is wrong and in the configuration IP on the LAN. Good luck I hope your observation.

Put it in bridge mode….:) Your WAN on the wireless AP connects to the LAN side of pfsense....

Yep. I didn't need to use VLAN7 and needed to deactivate DHCP on my speedport. No it is working…

hELP

Thanks - sorry so obvious!

I guess 0/0 and 0/0 with an uptime of 2 days, 18:31 is a good thing :D