-=> Shurato wrote to All <=-

 Sh> I've got a pfsense box running now; it took more of an effort than I
 Sh> thought it would.  pfblockerng-devel and snort may be doing more damage
 Sh> than good. Everytime I try to connect to the secure websocket, I get
 Sh> thrown in the block list...  I'm not sure if others can get to it or
 Sh> not.  Does anyone have any good hints for this firewall and increasing
 Sh> security without breaking stuff?

I don't use either of those with pfSense and it's working fine.  Snort is
complicated and has a steep learning curve.  Most of my errant traffic is
just script kiddies or these so-called "Internet security companies"
portscanning for open ports, both of which my BBS' internal firewall
handles.

Remember that pfSense automatically rejects all traffic on closed ports.  It
will protect you on all closed ports.  Open ports, it's up to the computer
where the ports are pointed to as to protecting itself as pfSense only
forwards the traffic through the firewall.

pfSense has excellent documentation online.  Don't expect to learn pfSense
immediately.  It can do some very complicated things like you're attempting.

snort has a great mailing list if you need help.  There's entire books
dedicated to the setup and maintenance of snort.



... Never make snow angels in a dog park.
--- MultiMail/Linux
 * Origin: Outpost BBS * Johnson City, TN (618:618/1)