Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 2 subscribers
  • Views 12826 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

The "Any -> Any: rule.

Right2Bear
Am I correct in my understanding that if I create a packet filter rule that allows Any - > Any, I am only affecting outbound traffic?  And since this is a home environment and I am not trying to stop any sort of outbound traffic, this sort of rule will be fine and not compromise my security?

AV, Spam and all web proxy stuff will still work, right?

Is there any risk in setting a rule like that if I don't care about blocking what the internal users are doing regarding the sites they are going to?

Thanks.


This thread was automatically locked due to age.
Parents
  • 0
    If you want to force the use of Standard or one of the Authorization modes, you could block outgoing HTTP traffic by putting a drop rule ahead of the Allow rule you discussed above: 'Internal (Network) -> HTTP -> Internet : Drop'.  That way, the only HTTP traffic that gets out is that which goes through the Proxy.

    Cheers - Bob
Reply
  • 0
    If you want to force the use of Standard or one of the Authorization modes, you could block outgoing HTTP traffic by putting a drop rule ahead of the Allow rule you discussed above: 'Internal (Network) -> HTTP -> Internet : Drop'.  That way, the only HTTP traffic that gets out is that which goes through the Proxy.

    Cheers - Bob
Children
No Data