Along the same lines of Gordons request to add wondershaper - to make use of the available bandwith for business purposes, this contrib blocks different kinds of P2P filesharing programs (kazaa, bittorrent, emule, etc). The software is from ipp2p.org. I (with Shad's help) had made rpms here which seem to work well, and are installed in a disabled state. Could we include them even though there is no panel for changing the settings? I didn't get any feedback that others had used them yet, but they work for me, and I think they'd be useful for others. http://mirror.contribs.org/smeserver/contribs/gswallow/ipp2p-sme7/new/
Closing, see the last two comments
we could try to do it ok :) i'm not realy familiar with kmod too but maybe that's not really complicate to do... do you know if opendpi is realy effective? i think that layer7 is the solution for p2p filtering... but need a kernel patch :/ i'll try to find some spec files for centos/fedora.
hello, It seems that the maintainer is still doing its job but outside of contribs : http://jeremielorente.free.fr/linux/sme/contribs/ipp2p/ Jeremie can you enter in the discussion ? I had just a look at OpenDPI and its at 1.3 version, so it might be really promising to move to this . I would like to help in releasing something but i am not familiar with kmod building and it might need some if the way to work is close to ipp2p
Switch to NEW. If someone is actually working on it then they can move it back to assigned.
(In reply to comment #65) > yes i really do, but i'll probably need help as that's the package i would > maintain Given the status of the ipp2p.org project here http://ipp2p.org/ as being no longer supported, is this smeserver-ipp2p package still being maintained, and in fact is it maintainable ? The last package appears to have been released in the smetest repo in March 2009. See http://mirror.contribs.org/smeserver/releases/7.4/smetest/i386/RPMS/ Is http://opendpi.org/ the way to go now ?
Clearing the patch_or_code_attached flag Assigning to jeremie lorente based on Comment #65, and changing status to Assigned. Changing title slightly as now has a maintainer.
> the smeserver-ipp2p package, at this stage, should > only install ipp2p and kmod-ipp2p packages That's correct. > cheaking kernel version I don't think checking the kernel version is a function of the smeserver-ipp2p package. It should be a function of the kmod-ipp2p packages. Otherwise every kernel release will require smeserver-ipp2p to be recompiled, along with the kmod packages. That would be silly.
(In reply to comment #66) > The integration package deploys template fragments and a config db key, not a > server-manager page. > > Given the simplicity of the package, there is no need for a server manager page > at this stage IMHO. Just recreate the integration package from the SRPM > provided earlier. so if i've understood... the smeserver-ipp2p package, at this stage, should only install ipp2p and kmod-ipp2p packages, cheaking kernel version, right?
The integration package deploys template fragments and a config db key, not a server-manager page. Given the simplicity of the package, there is no need for a server manager page at this stage IMHO. Just recreate the integration package from the SRPM provided earlier.
(In reply to comment #64) > (In reply to comment #63) > > No, I think we should re-open the bug. I think gdbs is volunteering to try > > taking over maintenance. > > Fine by me, but if that is the case perhaps Shad can move the package to the > current RPMS tree, so gdbs can use the commands and structures as described in > http://wiki.contribs.org/Package_Modification > > Gdbs can you confirm you want to be a maintainer for this package? If so we can > assign you to this project. yes i really do, but i'll probably need help as that's the package i would maintain i'll read the wiki page you've mentioned this WE. tell me if this ToDo list is correct to add this package to contrib repo: - change the build method from macro file to the new one - do a smeserver-ipp2p package to integrate configuration in server-manager page
(In reply to comment #63) > No, I think we should re-open the bug. I think gdbs is volunteering to try > taking over maintenance. Fine by me, but if that is the case perhaps Shad can move the package to the current RPMS tree, so gdbs can use the commands and structures as described in http://wiki.contribs.org/Package_Modification Gdbs can you confirm you want to be a maintainer for this package? If so we can assign you to this project.
(In reply to comment #62) > Futhermore I think we need to continue discussions like this on the devinfo > mailinglist rather then in this closed bug, or am I wrong? No, I think we should re-open the bug. I think gdbs is volunteering to try taking over maintenance.
(In reply to comment #60) > (In reply to comment #58) > > You shouldn't be pulling from fisheye. If you pull from sf cvs directly then > > everything should be the way it needs to be. > > but maybe it's somewhere on your computer? :) No, you should be able to check this out like this (according to Shad :-) ):: cvs -z3 -d:ext:smeserver.cvs.sourceforge.net:/cvsroot/smeserver co \ -P smeserver-ipp2p Futhermore I think we need to continue discussions like this on the devinfo mailinglist rather then in this closed bug, or am I wrong?
(In reply to comment #58) > You shouldn't be pulling from fisheye. Perhaps, but that doesn't change the fact that fisheye generates apparently corrupted files (via the 'raw' download link). IIRC, fisheye is also the only source of the suggested file which is known of by google. Anyway, src.rpm has been uploaded now. It's current AFAICT. Please correct me if you think otherwise.
(In reply to comment #58) > You shouldn't be pulling from fisheye. If you pull from sf cvs directly then > everything should be the way it needs to be. but maybe it's somewhere on your computer? :)
(In reply to comment #58) > If you pull from sf cvs directly then everything should be the way it needs to > be. It doesn't appear to exist anymore from the sf smecontribs cvs
You shouldn't be pulling from fisheye. If you pull from sf cvs directly then everything should be the way it needs to be.
(In reply to comment #56) > (In reply to comment #53) > > The archive appears to have been compressed twice. You can uncompress via: > > > > zcat smeserver-ipp2p-1.0.tar.gz | zcat | tar xvf - > > Wouldn't > > tar xzf > > have done the same? No. That would only uncompress once. This would do the same: zcat smeserver-ipp2p-1.0.tar.gz | tar zxvf - The problem is that fisheye is providing the tarfile compressed twice, but with name .tar.gz, not .tar.gz.gz.
(In reply to comment #53) > The archive appears to have been compressed twice. You can uncompress via: > > zcat smeserver-ipp2p-1.0.tar.gz | zcat | tar xvf - Wouldn't tar xzf have done the same?
thank you Charlie....
Created attachment 2289 [details] smeserver-ipp2p SRPM file (reconstructed from fisheye)
(In reply to comment #52) > > ok i've understand how this website work, i'll read the sources tomorow > > oups, tar.gz archive corruped? [Since you are telling us this, not asking, you should omit the '?'. To avoid confusion, you should say "It appears to me that the tar.gz archive is corrupted".] The archive appears to have been compressed twice. You can uncompress via: zcat smeserver-ipp2p-1.0.tar.gz | zcat | tar xvf -
(In reply to comment #51) > (In reply to comment #50) > > (In reply to comment #49) > > > The sources are in FishEye: > > > http://fisheye1.atlassian.com/browse/smeserver/smeserver-ipp2p > > > > i've seen this website but i really don't understand how to download something > > ^^ > > ok i've understand how this website work, i'll read the sources tomorow oups, tar.gz archive corruped?
(In reply to comment #50) > (In reply to comment #49) > > The sources are in FishEye: > > http://fisheye1.atlassian.com/browse/smeserver/smeserver-ipp2p > > i've seen this website but i really don't understand how to download something > ^^ ok i've understand how this website work, i'll read the sources tomorow
(In reply to comment #49) > The sources are in FishEye: > http://fisheye1.atlassian.com/browse/smeserver/smeserver-ipp2p i've seen this website but i really don't understand how to download something ^^
The sources are in FishEye: http://fisheye1.atlassian.com/browse/smeserver/smeserver-ipp2p
(In reply to comment #46) > he integration package (smeserver-ipp2p) needs to be resurrected before this > can go into the repo IMHO. > > Also, wasn't there some issue with the build system that made this impossible > to include in smecontribs? > > From my own limited initial study some weeks ago, it looked like ipp2p required > a bunch of kernel and iptables headers on the system before it would compile. > Perhaps we could patch the source of ipp2p with these headers to allow it to > build correctly within in the buildsystem, without reference to external -devel > packages. I imagine that when the kernel or iptables changed upstream, we would > have to update the patches, but at least this might give us a shot at making > ipp2p compatible with the buildsystem. > > Straight opinion now: this is a much-asked-for package that adds a lot of value > to SME Server as a business platform. Let's see if we can take it live. i've been able to compile it without smeserver-ipp2p sources :) but you're right, i think too that it's a very important contrib!
Hi! can't find the smeserver-ipp2p package and its sources! anyone here have it somewhere? :)
he integration package (smeserver-ipp2p) needs to be resurrected before this can go into the repo IMHO. Also, wasn't there some issue with the build system that made this impossible to include in smecontribs? From my own limited initial study some weeks ago, it looked like ipp2p required a bunch of kernel and iptables headers on the system before it would compile. Perhaps we could patch the source of ipp2p with these headers to allow it to build correctly within in the buildsystem, without reference to external -devel packages. I imagine that when the kernel or iptables changed upstream, we would have to update the patches, but at least this might give us a shot at making ipp2p compatible with the buildsystem. Straight opinion now: this is a much-asked-for package that adds a lot of value to SME Server as a business platform. Let's see if we can take it live.
ok i've compiled it :) see for details: http://forums.contribs.org/index.php/topic,35167.0.html how can i assign it to me? i have to change some build options and need help. i'd like to add ipp2p to contrib repository too... how can i do it?
someone give me the answer on dev mailing list: it's in /etc/rpm thx a lot! i was able to complie ipp2p package for kernel 2.6.9-78.0.13 !!!! where can i find the kernel-devel and kernel-smp-devel package for other versions? like 2.6.9-78.0.8???
I didn't know were to add the macro thing can someone help me telling me what I have to do with this file?: http://smeserver.cvs.sourceforge.net/*checkout*/smeserver/builds_bin/macros thx a lot
This package isn't compatible with the buildsystem as it isn't completely contained in the srpm. You need to tweak with and play with you system to get it in exactly the right state so that the package will build. That is why it was dropped.
(In reply to comment #40) > i've just finish a formation on linux, i'v seen just a little how to build a > rpm on fedora. i'll try to install a dev centos and rebuild the package as i > need ipp2p. i'll tell you if this bug need to be reopen to help me just a > little. thx If you are to do so please have a look on the build system contribs.org is using it is documented here: http://wiki.contribs.org/Package_Modification Also please REOPEN and ASSIGN the bug when you work on it.
i've just finish a formation on linux, i'v seen just a little how to build a rpm on fedora. i'll try to install a dev centos and rebuild the package as i need ipp2p. i'll tell you if this bug need to be reopen to help me just a little. thx
closing
closing as nobody has stepped up to take ownership of this package
anyone actually looking at this bug ?
Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package smeserver-ipp2p.noarch 0:1.0-2.el4.sme set to be updated --> Running transaction check --> Processing Dependency: kmod-ipp2p-smp for package: smeserver-ipp2p --> Processing Dependency: kmod-ipp2p for package: smeserver-ipp2p --> Finished Dependency Resolution Error: Missing Dependency: kmod-ipp2p-smp is needed by package smeserver-ipp2p Error: Missing Dependency: kmod-ipp2p is needed by package smeserver-ipp2p # uname -a Linux mailfish 2.6.9-55.0.6.ELsmp #1 SMP Tue Sep 4 21:36:00 EDT 2007 i686 i686 i386 GNU/Linux # cat /etc/redhat-release SME Server release 7.2
OK! So i think i'm going to read the 119 pages before trying to recompile ipp2p... Is someone can do it for the new kernel please? I don't think i can do it right now... thx
(In reply to comment #33) > thx for your help, but i have a problem. > the result of rpmbuild is: > error: line 7: unknown tag: %{kmod ipp2p 0.8.0 1} You need this in your .rpmmacros file: http://smeserver.cvs.sourceforge.net/*checkout*/smeserver/builds_bin/macros I'm pretty sure that's in the devguide, please check.
thx for your help, but i have a problem. the result of rpmbuild is: error: line 7: unknown tag: %{kmod ipp2p 0.8.0 1}
(In reply to comment #31) > (In reply to comment #30) > > > > With the right stuff at the top of the spec file, you should be able to derive > > _kversion from whichever kernel-devel rpm version is installed. > > Yes, I took away that part to compile the module against multiple versions of > kernel-devel installed on the same box. I doubt that there is ever a real need to have multiple versions of kernel-devel installed at the same time, but that can be catered for. > I think we can derive the _kversion in the spec file if it's not already > defined. Yes, and that is what I think is best, and what we've done in some previous module spec files.
(In reply to comment #30) > > With the right stuff at the top of the spec file, you should be able to derive > _kversion from whichever kernel-devel rpm version is installed. Yes, I took away that part to compile the module against multiple versions of kernel-devel installed on the same box. I think we can derive the _kversion in the spec file if it's not already defined. (PS. Actually I don't remember and I can't check right now but it might be already this way).
(In reply to comment #29) > Build the kmod-ipp2p package using the commands: > > $ rpmbuild -ba \ > --define "_kversion 2.6.9-55.0.2.EL" --target i586 kmod-ipp2p.spec > $ rpmbuild -ba \ > --define "_kversion 2.6.9-55.0.2.EL" --target i686 kmod-ipp2p.spec With the right stuff at the top of the spec file, you should be able to derive _kversion from whichever kernel-devel rpm version is installed. I would also rebuild from the src.rpm file, like so: rpmbuild --rebuild --target i686 kmod-ipp2p-x.y.z.src.rpm
(In reply to comment #28) > > Frederico, if you don't have time to rebuild it, just tell me how to do it. > > I'll do it for every new kernel version quickly > > thx > Install the development packages for the kernel, ex: kernel-devel-2.6.9-55.0.2.EL.i586 kernel-devel-2.6.9-55.0.2.EL.i686 kernel-smp-devel-2.6.9-55.0.2.EL.i586 kernel-smp-devel-2.6.9-55.0.2.EL.i686 Yum won't work, you have to download and install them using rpm -i (don't use -U). Check if the kernel development files are installed here: /usr/src/kernels/2.6.9-55.0.2.EL-i586 /usr/src/kernels/2.6.9-55.0.2.EL-i686 /usr/src/kernels/2.6.9-55.0.2.EL-smp-i586 /usr/src/kernels/2.6.9-55.0.2.EL-smp-i686 Download the kmod-ipp2p srpm from here: http://smeserver.nethesis.it/releases/7/SRPMS/ Build the kmod-ipp2p package using the commands: $ rpmbuild -ba \ --define "_kversion 2.6.9-55.0.2.EL" --target i586 kmod-ipp2p.spec $ rpmbuild -ba \ --define "_kversion 2.6.9-55.0.2.EL" --target i686 kmod-ipp2p.spec
(In reply to comment #25) > Ipp2p 0.8.0 built against last sme 7.3 kernel (2.6.9-55.0.2.EL): > > http://smeserver.nethesis.it/releases/7/i386/ > > About the repository and how to configure yum: http://smeserver.nethesis.it > Frederico, if you don't have time to rebuild it, just tell me how to do it. I'll do it for every new kernel version quickly thx
Great job Federico, been waiting for this! The only problem is that the kernel now moved to 55.0.6, so if you could rebuild it... Thanks.
(In reply to comment #25) > Ipp2p 0.8.0 built against last sme 7.3 kernel (2.6.9-55.0.2.EL): You mean 7.2 right? thx very much for your help. Can you tell me how to compile rpms like you've just did... i would like so much contribute like you just did. thx
Ipp2p 0.8.0 built against last sme 7.3 kernel (2.6.9-55.0.2.EL): http://smeserver.nethesis.it/releases/7/i386/ About the repository and how to configure yum: http://smeserver.nethesis.it
(In reply to comment #23) > Moving to the contribs category > Hi thx Greg for your work... I would like so much know how to build package from source for SME to help like you! Is there anyplace to find a good doc for a simple sme user? do you think ipp2p could be use on sme 7.2? thx a lot again for your great work!
Moving to the contribs category
Created attachment 1238 [details] ipp2p src rpm for SME8 Here's the updated ipp2p src rpm. I am building it successfully with "rpmbuild -ba ipp2p-kmod.spec --define "kversion 2.6.18-8.1.8.el5" --target=i686" for SME8. If you can update the buildsystem with the new iptables rpms I think it will work...
Created attachment 1237 [details] iptables src rpm - centos 4 version Here is the centos 4 version with the same changes made. I don't have a CentOS4 box to build it on, but it should work as well. I did get ipp2p to build on EL5/SME8 with the modified iptables-devel rpm installed - the only change was to add the build requirement iptables-devel, and it even worked with the new 0.8.2 version of ipp2p.
Created attachment 1236 [details] iptables src rpm - centos 5 version OK, starting with the SME8 build - you seem to have built it for SME8 already, but it wouldn't build for me without modifying the iptables rpm - attaching the modified src rpm (only changed the spec file).
(In reply to comment #15) > As I mentioned in comment 13 there is a lot of work involved in getting this > package to build. I've been babying this package along for quite a while. > I've currently got more important things to do at the moment so it won't be > maintained/fixed by me any time soon. I grabbed the ipp2p-kmod spec file, etc. Did it ever build using the kmodtool method? Before the problem with the build was that the iptables-devel rpm was missing a few files...just wondering if that was still the only problem?
rename
Which it will until you build new modules for the newer kernel. If you want to take it over please do.
Understood A temporary fix is to host the 4 files in my repo but I don't want to do this is it breaks at the next kernal change
As I mentioned in comment 13 there is a lot of work involved in getting this package to build. I've been babying this package along for quite a while. I've currently got more important things to do at the moment so it won't be maintained/fixed by me any time soon. We are also in the process of moving to a new buildsystem that ensures packages are built in a "clean room" to ensure the package and spec are put together correctly. This package needs a "LOT" of work in order to be built in this setup. If someone wants to take over maintaining this package and fix it then go ahead. Otherwise it probably won't be fixed/updated anytime soon.
Hi gentlemen, It seems that ipp2p dependencies are not anymore in smedev repo. Trying to install it gives me this : # yum install smeserver-ipp2p --enablerepo smedev ============================================================== WARNING: Additional commands may be required after running yum ============================================================== Loading "smeserver" plugin Loading "fastestmirror" plugin Setting up Install Process Setting up repositories Loading mirror speeds from cached hostfile Reading repository metadata in from local files Parsing package install arguments Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package smeserver-ipp2p.noarch 0:1.0-2.el4.sme set to be updated --> Running transaction check --> Processing Dependency: kmod-ipp2p-smp for package: smeserver-ipp2p --> Processing Dependency: ipp2p for package: smeserver-ipp2p --> Processing Dependency: kmod-ipp2p for package: smeserver-ipp2p --> Finished Dependency Resolution Error: Missing Dependency: kmod-ipp2p-smp is needed by package smeserver-ipp2p Error: Missing Dependency: ipp2p is needed by package smeserver-ipp2p Error: Missing Dependency: kmod-ipp2p is needed by package smeserver-ipp2p ================================================================ No new rpms were installed. No additional commands are required. ================================================================
Issue with this package is that the package doesn't build cleanly. It requires major manipulation to get the iptables source code in just the right place on the filesystem in order to compile.
request to add to smeextras
Moving to correct product...
(In reply to comment #9) > Shouldn't be in base. Still available as separate rpm that can be maintained > as a contrib. Moving to SME Contribs... and reopen...
Shouldn't be in base. Still available as separate rpm that can be maintained as a contrib.
really reopen
Reopen to mark won't fix
verified after closing and opening my applications they could no longer log on the the p2p networks config show ipp2p config setprop ipp2p bit enabled config setprop ipp2p ipp2p enabled signal-event remoteaccess-update cat /etc/rc.d/init.d/masq |grep p2p /sbin/iptables --new-chain ipp2p_block # Block p2p protocols /sbin/iptables -A ipp2p_block -m ipp2p --ipp2p -j denylog /sbin/iptables -A ipp2p_block -m ipp2p --bit -j denylog # ipp2p (apple) disabled # ipp2p (winmx) disabled # ipp2p (soul) disabled # ipp2p (ares) disabled # Block p2p traffic at INPUT and FORWARD /sbin/iptables --append INPUT -j ipp2p_block /sbin/iptables --append FORWARD -j ipp2p_block /sbin/iptables --flush ipp2p_block # Block p2p protocols /sbin/iptables -A ipp2p_block -m ipp2p --ipp2p -j denylog /sbin/iptables -A ipp2p_block -m ipp2p --bit -j denylog # ipp2p (apple) disabled # ipp2p (winmx) disabled # ipp2p (soul) disabled # ipp2p (ares) disabled
installs ok yum update --enablerepo=smetest smeserver-support Updating: smeserver-support noarch 1.6.0-34.el4.sme smetest 81 k Installing for dependencies: ipp2p i686 0.8.0-4.el4.sme smetest 6.1 k kmod-ipp2p i686 0.8.0-1.2.6.9_42.0.10.EL smetest 66 k kmod-ipp2p-smp i686 0.8.0-1.2.6.9_42.0.10.EL smetest 70 k smeserver-ipp2p noarch 1.0-2.el4.sme smetest 12 k
smeserver-support-1.6.0-33 * Sun Feb 18 2007 Stephen Noble <support@dungog.net> 1.6.0-33 - Add ipp2p package (disabled) to block p2p traffic [SME: 38]
You can now do: yum --enable smedev install smeserver-ipp2p Properties have moved to the ipp2p service.
http://forums.contribs.org/index.php?topic=35167.0 are the kernel modules built automatically now yum --enablerepo=smedev localinstall e-smith-ipp2p-0.1.0-01.noarch.rpm a candidate for smeextras ?
Moving to correct component (NFR)