Thank you very much. I did find under System->Firmware, Updater Settings tab, a check box for " Disable the automatic dashboard auto-update check.".  In my mind, I would rather see this as a submit button ala "Check for Updates" and then I could just hit it whenever.  I'm sure others will prefer the automated check. Good software lets users make choices and that is exactly what pfSense does in this case. me

http://www.freebsd.org/releases/8.3R/hardware.html

Do you know by any chance how can I accomplish this, what is the configuration in siproxd.

It is covered in the docs: https://doc.pfsense.org/index.php/PfSense_on_Watchguard_Firebox#Serial_Port_Quirk Your instructions are good though. Are you booting from a hard drive? There isn't normally a menu that gives you an option to boot to a prompt if you're booting nanobsd from a cf card. The reboot option should work but you will never be able to shutdown the box from software because the power supply is not atx compatible, it's not software controllable. Steve

[image: hKwiRek.png]

Your wireless can access your LAN clients without any issue so long as you permit it via the rules. My wireless clients connect to my media server which are both on different segments/vlans. True, any service that utilizes broadcast packets might not work, since that requires you to be on the same network/subnet/switch. Something like DLNA or Homegroups (windows vista/7/8). However there's even a work around for that too, but it's a bit over my head. I was just reading about it via another thread where a guy wanted to access windows shares between two different segments. WPA2 isn't bullet proof though, and if you have a bored neighbor they can still weasel their way in. Though you're right, it would take considerable amount of time - especially if you're using a solid random password. Though I'm just naturally paranoid, even when it's not needed :-P

If you want it transparent you need to have it in between your clients and wan router. That means you need two interfaces. Steve

@nothing: A/A is just another source of problems made up by the jews to save money buying cheaper hardware  :P Hahahha….  ;D

Also remember to turn off password protected sharing in Windows 7 or Vista if that is what you are using for sharing.

Easiest solution is on the interface tab (LAN for instance) you should have a pre-existing rule allowing internet, if you click the green arrow it will turn grey, indicating that rule is now "off" - essentially blocking interwebz for that interface. [image: AR9rOYo.png] **When I say "pre-existing" I mean to say a rule you created to allow internet traffic. Most people usually have something like * * * * *  meaning allow everything. I don't think pfsense creates such an internet rule for you automatically, just anti-lockout rules.

@stephenw10: The i350 has been well tested under 2.1, there are many reports of successfully using that card if you search the forum. I've never used one myself though.  ;) Steve Works just fine. I've got an I350-T4 in my system at home and I'm about to add a pair of boxes at work which each have 12 ports of I350. They're great NICs. Low power and fast.