The bandwidthd package will do that. Thank you for that tip.  I had it installed a long time ago but haven't looked at it in quite a while.

Yes, its working for me!!! Great thanks  :) Can you please guide me how to enable joinme in?

yep, you are right stephenw10. I didn't think about him running nano. Well crap, and he already bought a 4GB CF. Personally I would have gone for 30GB or more and stuck with a ordinary HD, but that's me. More questions to be had here. What kind of wireless AP? PCI, PCI Express I assume? What chipset? What version of PfSense When your wireless device connects to it what speed is your wireless device reporting if any? BTW, sorry about my other reply, wasn't thinking straight when I replied.

Yes,  The firewall rule on WAN allowing access to your webconfig port on WAN address. The reason I hesitate to spell it out for you is because it's not a desirable thing to do.  Plenty of examples already out there.

Both are specific to SCTP, which has to be in use for either to be relevant. Nothing in the base system nor any packages does so. It'll be patched in 2.2.1 regardless, but has no applicability to what is available today.

that's not relevant to FreeBSD. With its Linux emulation, it seems it is (or might be), but that isn't something we use nor include.

Looks like a crash unmounting a filesystem. Could be a corrupt filesystem or perhaps the disk and/or driver aren't playing nicely with 2.2

I posted a HOWTO here: https://forum.pfsense.org/index.php?topic=87738.0

hi johnpoz i done as you showed in your pic but still says port closed. please advice many thanks

pfblocker is dead. see pfblockerng here: https://forum.pfsense.org/index.php?topic=86212.0

No such issue. Also, make sure you allow both UDP and TCP (UDP being used for any recent Windows versions).

Depends on what it was.  Looks like a DDoS.  There might have been a bunch of firewall logs at the time.  Not that they would do you much good.

@jimp: Clear your browser cache. :-) Worked for me.

Frankly, I don't see what's your trouble with the DynDNS stuff. This is much more annoying Jan 26 09:17:46 check_reload_status: Restarting ipsec tunnels Jan 26 09:17:46 check_reload_status: Restarting OpenVPN tunnels/interfaces Not only that it's totally and completely useless when nothing changes, worse it disrupts traffic triggers the darned /etc/rc.newwanip{,v6} scripts that cause a whole lot more of useless activity causes a lot of CPU activity on slower boxes To get somewhere, go to System - Routing - Gateways, edit the WAN GW, click Advanced and make latency/packet loss/internal/down/etc settings a whole LOT more relaxed (defaults noted there).

See - Having your DNS hijacked isn't all bad (-:

So I'm tasked with setting up a VLAN to separate our wireless guest network from our actual network, Please bare with me as I am completely new to this. I am really confused by these sorts of questions.. If you don't have clue one about vlans - why in the world would you be given the task??  Are you an intern or something, and the network guys gave you the task and told you to figure it out? Not sure I would allow person that doesn't know anything about vlans touch a production switch?? Confused and Curious..