Easiest way I have found to troubleshoot rule problems is to turn on
logging for your deny rules and find out what rule is blocking the
traffic. Just add the 'log' or 'log logamount nn' (where nn is a number
of entries to create). Once you try to connect again, you can then read
/var/log/securi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>ipfw add 108 allow tcp from any to xx.250.227.0/22 20,21,25,80,110 via
>bge0
>
>#Outbound from inside
>ipfw add 109 check-state
>ipfw add 110 allow tcp from xx.250.224.0/22 via bge0 keep-state
>ipfw add 111 allow udp from xx.250.224.0/22 via bge0 ke
Please forgive me for asking this, I know it's probably been gone over
numerous times.
I have a network at a colo facility with a freebsd machine and 3 nic's.
Outside nic and the others for the internal networks. I get routed
3 class C's, and the machine is routing and acting as a gateway perfec
