-
Tiny vs ZA
Nulland Void:
"Sorry about the delay,"
I keep forgetting that patience is a virtue.;-)
"but I'm going in about 200 different directions here,"
Ditto.
"also, I think my ISP has gone back to using strings and tin cans again."
Ditto.
"Some answers:
A) freebie
B) no
C)It took a few days to gather a list of suspicious IP #'s and do a whois on them.
I used [url]http://www.blackcode.com/net-tools/[/url] and after drawing up a list (about 50 so far) of IP blocks assigned to the likes of Doubleclick and others, I set up one rule, and used the "Custom" option.
Then, in the Miscellaneous window, I inserted about 50 IP "Network/Range" rules.
And that's about it.
In the main administration interface, I also set up about 20 other individual rules, a list of which I got from a Tiny support site:
[url]http://groups.**********/group/tinyfirewall[/url]"
Thanks for answers and URLs.
"And there you go! *0-4 good buddy, and all that sort of thing."
It's pedal to the metal on Tiny rules for Blacksheep.
"I'm still diggin' in to it, and will post any other interesting stuff I discover about Tiny."
Good. Me too.
"Hope this helps."
Absolutely.
I didn't want to uninstall ZA Pro so I installed Tiny also (not to run simultaneously). Ran Tiny and saw that rules would take considerable mental effort/time on my part to set up properly. As I have too many irons in the fire now, put Tiny on hold for a bit, shut everything down, did a reboot, and back to ZA Pro. Tiny was still blocking packets with absolutely no Tiny running processes as listed by Win*8 System Information. Strange. Uninstalled Tiny, reboot, back to ZA Pro- everything's back to normal.
Gonna try Tiny again later when I understand the rules better. Thanks much for your comments.
Blacksheep
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
Forum Rules