Peerguardian uninstaller install#
Peerguardian uninstaller full#
Peerguardian uninstaller windows#

I may just whip up a little PHP program to chew on the Skips and verify that they're *all* covered elsewhere, but I have yet to find one (on further examination, jumping through the Skip list) that isn't. It did initially give me the impression that something (perhaps important) was being ignored, but that no longer seems to be the case. What I didn't notice is that (so far) every single-address range I've found in the Skipping lines is included within a larger range somewhere above it, so it seems these lines are redundant and properly skipped. I'm using the old commented BLOCKLISTS.īut I only noticed a large coincidence between my 'Skipping' lines in the log and single-address ranges in guarding.p2p.

Single address ranges you say? Do you use the 'old' commented BLOCKLISTS= or the new one (in /etc/cron.daily/moblock-nfq) with nipfilter.dat?Sorry, my bad.

If it all goes south, I may try to force up the latest. So, for now, everything seems mostly stable. By adding 'domain' to WHITE_TCP_OUT and WHITE_UDP_OUT, I was able to keep the VeriSign blocks (in case there could possibly be some nefarious P2P traffic from there.) without compromising my ability to resolve names. etc/moblock/MoBlock-nfq.sh sets a number of WHITE* variables that control passthrough rules. Still, something I read before kept echoing in my head, and today I seem to have stumbled over a better solution. Subsequent to this discovery, I grepped out from the building of guarding.p2p in /etc/cron.daily/moblock-nfq any of those or any having a dotted word with NS and an optional digit, and things became much better.

Peerguardian uninstaller full#

With this full list loaded and moblock running, I lost the ability to resolve an uncached domain name from the root servers (which I seemed to find were blocked by entries labeled 'VeriSign Global Registry Services'). What I didn't realize is that many, if not most or all, of the DNS root servers and various other target domain's servers are included in the blocklists that I get from 'ads-trackers-and-bad-pr0n level1 level2 Microsoft spyware'. My Ubuntu Dapper box is running bind9 with my own tables for internal addresses and bumping up to the root servers for anything unknown - I've traditionally found ISP's DNS's to be slow or unreliable, and I've been very happy with DNS performance since I cut my ISP out of the loop. I did finally have a realization as to the cause of my most major problem, and I'll post it here in case anyone else is in a similar boat and did the same not-thinking I did.

For the time being, I've backtracked to the Old Packages posted by lp7413 in post 239 and made some adjustments, and things appear more stable now. That wouldn't be the ideal solution though.No, I hadn't tried -force, but thanks, I'll keep that in mind for later, in case the progress I've made lately falls apart. If that doesn't do it, i could probably build the latest moblock release for dapper. I'd say you'd be better of compromising moblock than the whole system, so give -force a try.

Peerguardian uninstaller install#

if anyone needs any more information, please ask.Have you tried to install it with -force ? The diffrence between the debian libc and the ubuntu one shouldn't be very large.

Peerguardian uninstaller windows#

i'm running windows xp sp2 on an athlon 64, with stock clock speeds. the program still runs fine on my two other computers, so this problem is a mystery to me. internet connections are working fine, and i have made no major system changes recently. i tried uninstalling and reinstalling boinc and the problem STILL persists. boinc manager would start upon login, freeze for about 30 seconds, then report that it couldn't connect to localhost. so, i rebooted, hoping that would fix the problem but it had no effect. sixtrack was running full power, like always, but the manager was totally useless. Was anything updated on Windows XP (like through an automatic update?) Are you using a firewall (ie zone alarm or Windows FW)? Sometimes you have to explicitly allow communications on the fire walls, even to talk to localhost.Ī few hours ago, I sat down at my computer and decided to casually check my lhc stats but lo and behold, the boinc manager was totally frozen! I popped open the task manager to see if i could figure out what was going wrong but everything seemed normal.