Just out of curiosity, how often do you delve down on the console ?

I have actually never logged in to the console after the install, on any of the sites I have installed on.
So for me I would see no benefit from changing this value.

Please help.

Thanks I will use these options.  ;D

Thanks again.

@i_robot73:

bumping.

Anyone?  Wish I had more than 2 PCs to test better  ::)

Both PC and server are on the same LAN subnet and pings won't go through the pfsense box - they go through the switch.  IMO, you have not configured the server to reply to Pings.

As for RDP, it's probably the same thing in effect.  Make sure that Windows firewall (disgusting tool that I normally disable in lieu of better solutions) is set on the server to allow incoming RDP connections.

short: YES

Long:
1. squid and squidguard need to be installed, if done with opendns it works a little better, do a block rule to prevent them from bypassing opendns, useful for sites that use https as squid does http only
2. yes with firewall rules
3. yes/no ads with squid and a custom config, spyware via http only with havp.

@elade:

Is it going to be possible at version 2
connecting to ISP's at this method ?

i found this topic: http://forum.pfsense.org/index.php/topic,25465.0.html
and i can see this issue was already discussed and better get solved by Micky
are you going to implement is solution at the new upcoming version ?

Not only is there no point, but you'll probably find your network stops working unless you bridge the WAN and LAN interfaces on the pfSense host.

Thanks a lot. That helped.

Thanks for the input. I am not talking about the external USB ports.

I am talking about the pin jack on the board. Pins like this:

…..
....

It's labeled J19 USB. (my typo on r).

So, I am lookin for a mood light that interfaces on the motherboard USB jack port.

Thanks

They are the internal rule numbers the pf(4) filter assigns to the rules. To see the numbers run this in shell or command prompt in the webgui:

Thanks for the responses.

I was getting confused on the procurve definition of 'trunk'.  Trunk in their words means link aggregation/increase the bandwidth.

My problem was that I fat-fingered one of the vlan information on the linux server, which was causing problems.  I fixed everything and everything is perfect.  :)

There are some other packages like bandwidthd that graph traffic on a per-IP basis. Some more info can be found here:
http://doc.pfsense.org/index.php/How_can_I_monitor_bandwidth_usage%3F

Thanks all for the responses.

You are correct, the "trunk" in the procurve is for link aggregation.  The tag / untagged definition related to vlan's.

In the end, I got it to work.  I fat-fingered something on the server which was causing the problems.  Bottom line is that things are working great.  :)

thanks!

I still have not figured this out.  Any more ideas?