I would create rules in your LAN IF section to only Allow the traffic you want allowed. IE write rules to allow web, https, dns, etc, and then change the default allow all to deny all. You can also make use of the traffic shaper to prioritize traffic.

im pretty poor but I posted small bounty for a tutorial on getting linux binaries to work on pfsense.  I am not sure how hard/easy that would be.

thanks for the help,
Zack

Not sure why it is not working in IE.  Works fine in FF and Opera.

RC3 is quite old.  I am locking this thread to avoid confusion.

Ugh, the forum keeps putting posts in the wrong thread.  This is now the 3rd time this has happened and I don't think it is my mistake.  My apologies, this was not the thread that was supposed to be replied to.

@zboll:

performance-wise, how does pfsense compare to a linux version of router such as endian?  Would I really notice the difference in performance on a P2 400 MHz 384 MB ram?

thanks,
Zack

This is not really related to the topic that you started. Please open new threads for new topics.

v4 and v5 are very very old
pfsense uses the last version of freebsd so that it supurt all new machines
if you got stone aged stuff then use monowall witch uses freebsd 4.x

http://www.oxid.it/cain.html is very powerfull for arp poisened sniffing too but these kind of stuff can be detected. the Hub is probably the easier more "invisible" way to do it.

Problem solved. The other PC works perfectly.
  I don't know what was the problem with the first one.

:) This is called, not enough coffee syndrome. I never mess with config's until the coffee pot is half empty. Hope this helps some other noble fool who dares try to configure thing when they're not 'alert'.. heh..

I'm just thinking the oposite  :D

Ok, I'll have to figure out a way to determine when it disappears exactly.

Nice idea.

Yes, lease or rent a smart-bits unit.

It's a bridge so it's own IP is not needed. Assign an unused IP from an unused IP-Range to it. However then you won't be able to install packages, use DNS and so on at your pfSense.

install the dev version of pfsense that is freebsd 6.1 + pfsense gui + dev tools

pfsense is a version of freebsd with almost all of the freebsd lib and tools removed
and a gui

config.xml from /cf/conf/ stores ALL information related to pfSense and FreeBSD.

The only exception is /etc/sysctl.conf that I can think of of the top of my head.