Yep.  It is enabled on LAN & Wireless Interfaces with Default options.

I understand that you want to increase the priority of your www traffic? You already have hi-priority queues - qOthersUpH / qOthersDownH And, the simple way - define www traffic (80 dest port) to this queues. LAN->WAN|TCP|||Port: 80 (HTTP)|qOthersUpH/qOthersDownH|web HTTP But this rule must be moved up to DNS rules before other (after dns for example) –- And for reset you Shaper settings to default - use ' EZ Shaper wizard '

@vladtheimpaled: Are there any resources around that list hardware compatibility … http://www.pfsense.org/index.php?option=com_content&task=category§ionid=9&id=28&Itemid=47

looks like the zombies were all from bandwidthd, uninstalled and they all went away. looks like syslog is my problem now, and in particular the IPSEC log is really getting hammered. Nov 4 14:02:54 racoon: INFO: fe80::21b:21ff:fe08:3e9c%em0[500] used as isakmp port (fd=21) Nov 4 14:02:54 racoon: [Self]: INFO: 66.193.100.234[500] used as isakmp port (fd=20) Nov 4 14:02:54 racoon: INFO: fe80::21b:21ff:fe08:3e9d%em1[500] used as isakmp port (fd=19) Nov 4 14:02:54 racoon: INFO: fe80::203:47ff:fe40:2bb1%fxp0[500] used as isakmp port (fd=18) Nov 4 14:02:54 racoon: [Self]: INFO: 192.168.1.1[500] used as isakmp port (fd=17) Nov 4 14:02:54 racoon: [Self]: INFO: 127.0.0.1[500] used as isakmp port (fd=16) Nov 4 14:02:54 racoon: INFO: ::1[500] used as isakmp port (fd=15) Nov 4 14:02:54 racoon: INFO: fe80::1%lo0[500] used as isakmp port (fd=14) Nov 4 14:02:54 racoon: INFO: fe80::21b:21ff:fe08:3e9c%vlan0[500] used as isakmp port (fd=13) Nov 4 14:02:54 racoon: [Self]: INFO: 10.10.0.1[500] used as isakmp port (fd=12) Nov 4 14:02:54 racoon: INFO: fe80::21b:21ff:fe08:3e9c%em0[500] used as isakmp port (fd=21) Nov 4 14:02:54 racoon: [Self]: INFO: 66.193.100.234[500] used as isakmp port (fd=20) Nov 4 14:02:54 racoon: INFO: fe80::21b:21ff:fe08:3e9d%em1[500] used as isakmp port (fd=19) Nov 4 14:02:54 racoon: INFO: fe80::203:47ff:fe40:2bb1%fxp0[500] used as isakmp port (fd=18) Nov 4 14:02:54 racoon: [Self]: INFO: 192.168.1.1[500] used as isakmp port (fd=17) Nov 4 14:02:54 racoon: [Self]: INFO: 127.0.0.1[500] used as isakmp port (fd=16) Nov 4 14:02:54 racoon: INFO: ::1[500] used as isakmp port (fd=15) Nov 4 14:02:54 racoon: INFO: fe80::1%lo0[500] used as isakmp port (fd=14) Nov 4 14:02:54 racoon: INFO: fe80::21b:21ff:fe08:3e9c%vlan0[500] used as isakmp port (fd=13) Nov 4 14:02:54 racoon: [Self]: INFO: 10.10.0.1[500] used as isakmp port (fd=12) Nov 4 14:02:54 racoon: INFO: fe80::21b:21ff:fe08:3e9c%em0[500] used as isakmp port (fd=21) Nov 4 14:02:54 racoon: [Self]: INFO: 66.193.100.234[500] used as isakmp port (fd=20) Nov 4 14:02:54 racoon: INFO: fe80::21b:21ff:fe08:3e9d%em1[500] used as isakmp port (fd=19) Nov 4 14:02:54 racoon: INFO: fe80::203:47ff:fe40:2bb1%fxp0[500] used as isakmp port (fd=18) Do i need to force racoon to only use one interface? kind of at a loss now.

By hand - details of the process can be found in a number of threads in the packages forum.  That will not give you a GUI, you'll have to maintain Snort through the config files.  Alternatively, upgrade to 1.2.1 beta and (from what I've read) you'll find Snort available in the package system. You'll also need some reasonable hardware (at least 1 GB of RAM, a 1 GHz CPU that's currently >90% idle and non Realtek NICs) as running Snort has major performance implications.

Many thanks to itshuge for that solution, I'm a total newbie, when it comes to tinkering under the bonnet of linux, this might help other newbies, I had to change value to 840, not 802

Ok well I was able to successfully establish a proxy session via another machine, so apparently the machines I used in my original tests were experiencing similar problems (most likely user error), but the main machine I use (FreeBSD 6), well it would appear to be something wrong that would require more in-depth troubleshooting.  But, bottom line is it is not a problem with pfsense ssh host.

Not possible on pfSense at the time. I think i read something somewhere about being able to use names in firewall-rules in the future so it might be possible with a future release.

Hello. Really i dont Know why the forum members are not answering. Please Brows I need your help. I dont know why when ever any customer try to use torrent it makes my network toooo slow. It seems All the bandwidth going to Torrent and other cant do anything. All the web page takes too long to load when Torrent is running another computer. And most important if i chek status of Queues(while Torrent is running) its nothing on P2Pup/P2pdown queues. But on qlandef its always full when torrent is running. Please please i juset need to limit the bandwidth of torrent. So that other user can use net well way. I will wait for answer. Thank you

Does DNSer support the same method of updating the IP as DynDNS does? (DynDNS update is just a http call to url http://username:password@members.dyndns.org/nic/update?…) You could then have your pfSense box to do all the work of monitoring and updating the IP by using this solution by Perry: http://forum.pfsense.org/index.php/topic,9729.0.html Of course needs some modifications. Hope this helps.

I second the suggestion you try polling. It will probably help squeeze a bit more out of your machine.

What do you mean by a management VLAN for pfSense? Normally, the management VLANs on other devices are just VLANs that the device listens on with management interfaces. You can get to the pfSense interface on any of the VLANs as long as the firewall rules allow it.

This thread hasn't been updated in a while, but worth a look:http://forum.pfsense.org/index.php/topic,7668.0.html

Have you enabled a firewall rule to allow it to be pinged? As for access to the 192.168.2/24 network from the 192.168.1/24 network, do you need that?  By default the pfSense host will be NATing all traffic from 192.168.2/24.  If you want to route instead you'll need to disable NAT.