Now I admit it, I dumped Windows last year because I was sick of the nonsense, the problems and such. When I switched (using OpenSUSE at the moment), I was always curious if there was an equivalent to apps that I used to use in Windows. So I took several months looking around the web. For the most, I have found alternatives and ways to pretty much everything. (Well, except for some Windows games...But I'm sure that'll change as WINE gets more mature).

So let's get straight to it, shall we?

Open-source is about community spirit, to share what you have with others and vice versa. To offer choice, such that everyone benefits.

During my research, I found these...

linblock - Automatic IP Blocklists for Linux
http://dessent.net/linblock/

MoBlock
http://moblock.berlios.de/

Now, both serve the SAME purpose as PeerGuardian. Of the two, MoBlock seems to be more in active development. (Last updated on the 15th Feb, this year).

My proposal is that: IF its possible, could the PhoenixLab's team contact the devs of those projects and unite under the same goal?

Because it sure would help fill in that niche that PhoenixLabs is currently suffering in Linux! I personally think a distro is not a good idea given the lack of resources that PhoenixLabs has. BUT *raises finger*, an actively worked on PeerGuardian for Linux would be a much better, less resource intensive alternative for everyone.

If you're worried about Licensing, everyone is under GPL.

What do you folks think?


OT: Now all that's left is for someone to develop a "BlockList Manager"-like solution for Linux!

it seems that your proposal has been accepted :)

phrosty contacted me and proposed to make MoBlock become the official peerguardian linux, so here i am.

I'll make a topic to summarize what is happening, meanwhile you can continue testing MoBlock!

__________________
MoBlock

kool very nice.

To adapt to the recent events, I am trying to package moblock (0.7) for debian.
I modified moblock to fork (detach from the console) to use it as a deamon and to create a pid file. I also changed the code to react to SIGHUP by reopening the logfile for automatic logfile rotation. The upstream maintainer is aware of these modifications and is including them in the next release.
At first glance, everything seems to work. The package installs on my system, guardian.p2p is updated and /etc/init.d/moblock inserts the appropriate rules via iptables.

You can point your apt to

to have a first look.

This repository contains my latest work on peerguardnf and moblock.
It also includes debian packages for libnfnetlink and libnetlink_queue since I have not found them ready for debian anywhere. I tried to get moblock running with libnetlink_queue but did not succeed. The current package uses the old interface - which means that at the moment you should not need to modify your kernel to switch from peerguardnf.
You can also get the source for each of these packages and building them should work at least on debian etch and later.

If you want my gpg-key, you can copy it from http://forums.phoenixlabs.org/t11294...or-debian.html
You can add it with to the apt keyring on your machine.
The key is also at http://mitglied.lycos.de/clessing/ but fetching it there does not make any sense (You are aiming to trust this location using this key...).

If you experience any hiccups, you are welcome to report them or to send me a patch.
You can reach me via clessing at freenet.de (which is also the maintainer address in the debian packages.)
Please be aware of the fact that I may miss cool scripts or tweaks in other parts of this forum. If you want parts of them included - send me an email! (I would be delighted if it's a "diff -u" against any of the files that are included in my packages)

Just noticed that the archives with the original sourcecode were missing in my repository.
Fixed this. You should be able to check out the sources with

apt-get source peerguardnf
or
apt-get source moblock

Building the packages yourself should be a simple matter of "dpkg-buildpackge -rfakeroot"

If the problem is that you get link errors i noticed there's an error in the Makefile, replace:

gcc -o $@ MoBlock.o rbt.o -lnetfilter_queue

with

gcc -o $@ MoBlock.o rbt.o -lnetfilter_queue -lnfnetlink

don't know how it happened...

__________________
MoBlock

No, I did not have problems compiling it. For some reason, moblock did not filter anything (every traffic was blocked).
I will try to reproduce this as soon as possible...

btw, about the windows gaming.. i don't think wine will be handling many games that arent dos, it seems to be thats cedega's job -- http://www.transgaming.com/ -- cedega must be paid for. if you run gtk-gnutella or another p2p app, you can try finding open source/free software that accomplishes the similar task of cedega 4.4.

Whoo-hoo! I made a difference!

Thanks for joining the PeerGuardian team.


It depends on the game.

I use WINE to play Red Alert (Windows version), Star Wars: Jedi Knight - Jedi Academy, and Star Wars: Jedi Knight II - Jedi Outcast...I even use it with DVDShrink! But I can't get Ghost Recon and Metal Gear Solid 2 to work right (it installs, but does not run). MGS 1 works, though! :)

For DOS games (Police Quest, etc), I use DOSBox.

For those classic LucasArts adventure games, I use ScummVM. (Full Throttle, Indiana Jones and the Fate of Atlantis, etc)

And if Cedega is required, just compile the CVS version, that's FREE!