On Fri, Apr 11, 2008 at 7:33 AM, Jan Zorz <[EMAIL PROTECTED]> wrote: > Don't bother with this. I ran through a small flame-war with Scott about > this, wrote my own patches for pfsense, that were working flawlessly on > 1.0.1 and were applying rules on out-traffic, but politic persuation on > dev's side prevented those patches to be implemented... > > Too bad, from my point of view. > What's wrong with only in rules?!
You can do the same blocking as you would do with out and just save your computer from blocking the packet after traversing the whole machine! Ermal > Don't start that all over again, just learn to live with in-only rules. > > /jan > > > > Randy Schultz wrote: > > > Hiya, > > > > We are running 1.2-RELEASE with a bridge across OPT1 and OPT2. Is there > any > > way to block to destination ports? I have found blocking from source > ports > > but cannot find anything that allows me to block traffic to a port. Have > I > > just overlooked something? > > > > -- > > Randy ([EMAIL PROTECTED]) 765.983.1283 <*> > > > > Love with your heart, think with your head; not the other way around. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
