how-to block ads
|
|
Share Topic
 |
 |
|
|
|
 gwionwild colonial boyPremium,ExMod 2001-08
join:2000-12-28
Pittsburgh, PA
kudos:1 | reply to wiregauze
Does this help? Here's a log excerpt... it shows how Tiny is still blocking the requests from localhost... a request TO localhost, as I said, is returning to the same machine; one coming out of that address is still processed, as it would be from any other local address, as it should be:
24-05-2001 12:28:47 Local3.Info 10.0.13.1 Rule 'Block NB WAN': Blocked: Out UDP localhost:137->10.6.1.1:137, Owner: SYSTEM
24-05-2001 12:28:46 Local3.Info 10.0.13.1 Rule 'Block NB WAN': Blocked: Out UDP localhost:137->10.6.1.1:137, Owner: SYSTEM
24-05-2001 12:28:44 Local3.Info 10.0.13.1 Rule 'Block NB WAN': Blocked: Out UDP localhost:137->10.6.1.1:137, Owner: SYSTEM
24-05-2001 12:28:37 Local3.Info 10.0.13.1 Rule 'Block NB WAN': Blocked: Out UDP localhost:137->206.46.185.41:137, Owner: SYSTEM
24-05-2001 12:28:36 Local3.Info 10.0.13.1 Rule 'Block NB WAN': Blocked: Out UDP localhost:137->206.46.185.41:137, Owner: SYSTEM
24-05-2001 12:28:34 Local3.Info 10.0.13.1 Rule 'Block NB WAN': Blocked: Out UDP localhost:137->206.46.185.41:137, Owner: SYSTEM
24-05-2001 12:28:33 Local3.Info 10.0.13.1 Rule 'Block NB WAN': Blocked: Out UDP localhost:137->4.0.117.118:137, Owner: SYSTEM
24-05-2001 12:28:32 Local3.Info 10.0.13.1 Rule 'Block NB WAN': Blocked: Out UDP localhost:137->206.46.185.41:137, Owner: SYSTEM
24-05-2001 12:28:32 Local3.Info 10.0.13.1 Rule 'Block NB WAN': Blocked: Out UDP localhost:137->4.0.117.118:137, Owner: SYSTEM
24-05-2001 12:28:31 Local3.Info 10.0.13.1 Rule 'Block NB WAN': Blocked: Out UDP localhost:137->4.0.117.118:137, Owner: SYSTEM
24-05-2001 12:28:31 Local3.Info 10.0.13.1 Rule 'Block NB WAN': Blocked: Out UDP localhost:137->206.46.185.41:137, Owner: SYSTEM
24-05-2001 12:28:31 Local3.Info 10.0.13.1 Rule 'Block NB WAN': Blocked: Out UDP localhost:137->4.0.117.118:137, Owner: SYSTEM
24-05-2001 12:28:30 Local3.Info 10.0.13.1 Rule 'Block NB WAN': Blocked: Out UDP localhost:137->4.0.117.118:137, Owner: SYSTEM
24-05-2001 12:28:29 Local3.Info 10.0.13.1 Rule 'Block NB WAN': Blocked: Out UDP localhost:137->206.46.185.41:137, Owner: SYSTEM
24-05-2001 12:28:29 Local3.Info 10.0.13.1 Rule 'Block NB WAN': Blocked: Out UDP localhost:137->4.0.117.118:137, Owner: SYSTEM
24-05-2001 11:31:45 Local3.Info 10.0.13.1 Rule 'Filtered Ports': Blocked: Out TCP localhost:1080->206.46.170.10:110, Owner: C:\PMAIL\WINPM-32.EXE
--
Man will occasionally stumble over the truth, but most times he will pick himself up and carry on. - Sir Winston Churchill | |
 Zhen-XjellProlific BunnyPremium,VIP,ExMod 2001-04
join:2000-10-08
Bordentown, NJ | Well, like I said, I have never touched Tiny. | | |
|
gwionwild colonial boyPremium,ExMod 2001-08
join:2000-12-28
Pittsburgh, PA
kudos:1 | That's OK... what we really need here is some wallwasher advice, anyway. The way I see this, what's needed is PROXY filters to stop wallwasher from letting out, for example, big fix, without stopping, say, Internet explorer. Whether through Tiny or ZA, or any ther firewall. Wiregauze wants his proxy, and his firewall, so his real problem is how to run WW and not automatically allow it as a "tunnel" through the firewall... way I see it, the most efficient way would be to make some sort of deny filter in the PROXY, but keep in mind tha a proxy - ANY proxy - is not as secure as a good firewall --- but can do things with cookies and content a firewall can't --- so we have a real balancing act... hmmm catch-a-tweneetoo, indeed... 
--
Man will occasionally stumble over the truth, but most times he will pick himself up and carry on. - Sir Winston Churchill | |
|
