It's working beautifully! However, an user is using a noncommon port for p2p sharing- namely the TCP 52525 port. He claims that common BT ports are blocked by some BT users. I assume I should include that port in a lower priority TC class on top of ipp2p?
Thanks for the assistance, Eric! ~D > -----Original Message----- > From: Eric Spakman [mailto:[EMAIL PROTECTED] > Sent: Monday, February 20, 2006 11:43 PM > To: Doug Sampson > Cc: '[email protected]' > Subject: Re: [leaf-user] ipp2p > > > Hello Doug, > > Support for ipp2p isn't compiled into Bering-uClibc-2.3.x, but it's > available for Bering-uClibc-2.4beta. What you could do is upgrade the > packages that are needed for kernel 2.4.32, which can be found at > http://cvs.sourceforge.net/viewcvs.py/leaf/bin/packages/uclibc > -0.9/20/2.4.32/ > : > > initrd_*.lrp (if you use an initrd with included boot modules) > iptables.lrp (compiled against 2.4.32, with included ipp2p module) > modules.lrp (2.4.32 modules with included ipp2p kernel module, add the > extra modules you need from the 2.4.32 tarball) > linux-2.4.3-upx (rename to linux) > > This would be enough to upgrade your setup to kernel 2.4.32 > and have ipp2p > support. > > For traffic shaping you can find a document describing a setup for > Bering-uClibc with shorewall 2.4.x at: > http://www.ucbering.de/?Projects:traffic_control_for_shorewall > > Or optional you can also update to shorewall 3.0.x > (http://cvs.sourceforge.net/viewcvs.py/leaf/bin/packages/uclib c-0.9/20/testing/) where traffic control is included. Eric > Is support for IPP2P traffic shaping already compiled/built into the > default Bering uClibc 2.3x setup as well as the default Shorewall setup > contained within the Bering setup? I would like to classify P2P traffic as > low-priority and saw that IPP2P is being offered as one of the protocols > in /etc/shorewall/tcrules but it warned that support for IPP2P must be > supported in the kernel and iptables. > > ~Doug > > > _______________________________________ > «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?» > ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ > Doug Sampson > Information Technology > Dawn Sign Press > dougs (at) dawnsign dot com _______________________________________ > «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?» > ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 > ------------------------------------------------------------------------ > leaf-user mailing list: [email protected] > https://lists.sourceforge.net/lists/listinfo/leaf-user > Support Request -- http://leaf-project.org/ > > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 ------------------------------------------------------------------------ leaf-user mailing list: [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
