BAlfson said:Hi, Albert, and welcome to the User BB!
Is Web Filtering in a Standard or Transparent mode? Do you have the FTP Proxy enabled?
For more understanding of these sequence issues, see #2 in Rulz and consider the diagram attached to that post. I haven't tried this with outbound traffic, but you might try a DNAT of '{PC} -> Any -> Internet : to {non-existent IP}'. Does that work?
Cheers - Bob
Is this still the best way to block all internal traffic to a given host?
BAlfson said:Hi, Albert, and welcome to the User BB!
Is Web Filtering in a Standard or Transparent mode? Do you have the FTP Proxy enabled?
For more understanding of these sequence issues, see #2 in Rulz and consider the diagram attached to that post. I haven't tried this with outbound traffic, but you might try a DNAT of '{PC} -> Any -> Internet : to {non-existent IP}'. Does that work?
Cheers - Bob
Is this still the best way to block all internal traffic to a given host?
I'm confused by your question, Sean. This thread was about blocking one internal IP from reaching the Internet. Please be more precise about what it is you want to block.
Cheers - Bob
BAlfson said:I'm confused by your question, Sean. This thread was about blocking one internal IP from reaching the Internet. Please be more precise about what it is you want to block.
Cheers - Bob
Sorry I wasn't clear.
I wanting to block all traffic from my network to a specific IP, and would like to know if the solution proposed in this thread would be the most effective method to achieve this.
Not knowing anything about your setup, the quickest sure answer is to use a different NAT rule like 'Any -> Any -> {banned IP} : SNAT from {240.0.0.1}'. If you don't want to see the blocks caused by this in the firewall log, select 'Automatic firewall rule'. Did that work for you?
Cheers - Bob