Hello,
i'm currently using Outpost 2.5 (370) on my gateway pc together with Fritz!Web (www.avm.de) which is providing NAT.
In Standard-Configuration Internet works from the Gateway PC but from the others it doesn't -> Block Transit Packets.
In Outpost 2.1 ShowNATColumn=YES and Allow ICS in Local Net and Internet (*.*.*.*) solved the problem.
In Outpost 2.5 ShowNATColumn=YES doesn't work anymore. Also global system rules adding Allow Transit (Outbound -> NAT or Transit) doesn't work, only Local works.
But Local is the same as stopping Outpost right?
Example -> Data from 192.168.5.10 -> Gateway (192.168.5.1) (system)
Gateway (192.168.5.1) (system) -> Internet
So I have to allow system everything or? But this isn't good?
Thanks for any help
Flane
Well, I you aren't placing Mark Rule as High Priority, then even though you've allowed all Local packets, application level filtering still works, AFAIK. People Fritz Heese — Darrel Heetland in Spoke's business directory::
People Fritz Heese — Darrel Heetland in Spoke's business directory. Company: M B N A America Bank Nat Assn · Christine Heesters. Title: Web Manager
http://center.spoke.com/info/index-person/hb-he-134HOME |
Welcome to the forums Flare,
The Outpost and Fritz!web DSL Network Connection Sharing (http://outpostfirewall.com/forum/showthread.php?t=6892) thread is the only other one I can find here referring to Fritz!Web and that was for a different issue.
Creating generic "Allow" rules is bad for security as you correctly state - however you may have little choice when running a PC as a gateway if application rules cannot be set for Fritz!Web. The only suggestion I can make is to experiment with these rules to see how much you can limit them (packet type, port range, address range, etc).
 Where's The Advantage In Windows Genuine Advantage?
 Stocks Bounce After S&P Joins Bear Market
|
NAT with Fritz!Web 
PRINT
Add to favorites