<div class="gmail_quote">On Sun, Jun 6, 2010 at 6:23 AM, Michael Sanders <<a href="mailto:dsanders@jsu.edu">dsanders@jsu.edu</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <div><div style="font-family: Verdana; font-size: 10pt; color: rgb(51, 51, 51);">I second Paul that is the way to go, once one finds out they have eyes on them, it "can" fix it's self. We had a problem with an individual serving up files and the big bad record industry sent a letter. That gave us the right to cut the user off. Once turned back on behavior changed. You will get some flack on the front end but over time a majority of the community will get in line. Danny Michael Sanders IT Support Analyst <div><div></div><div class="h5"> ----- "Paul Graydon" <<a href="mailto:paul@paulgraydon.co.uk" target="_blank">paul@paulgraydon.co.uk</a>> wrote: > That will help, but realistically you're going to have to block every "high port" to stop P2P through that method. > > The only way to effectively block P2P is to do packet sniffing and analysis.. and that's just one big hassle. > > My belief is this is usually the wrong way to tackle the problem, looking for a technical solution to a human resource problem. > User education (and LARTing if necessary) is the key. Using software like Cacti to monitor and graph per-port traffic stats, identify the largest bandwidth users and then focus on them and find out just why they're using up so much bandwidth. > It's remarkable just how soon the problem all goes away after you find just one or two individuals who are abusing the network infrastructure and explain to them what the disciplinary procedures are (or enact if it's appropriate and you have concrete evidence.) The message soon spreads! > > Paul > > On 06/04/2010 05:03 AM, Greyson Farias wrote: <blockquote>Hello, > > You can use these iptables rules, because I don't like, don't use and I don't wanna learn ufw. hehehehehe > > # Block P2P connections > iptables -A FORWARD -p tcp --dport 1214:1215 -j DROP > iptables -A FORWARD -p udp --dport 1214:1215 -j DROP > iptables -A FORWARD -p tcp --dport 1981 -j DROP > iptables -A FORWARD -p udp --dport 1981 -j DROP > iptables -A FORWARD -p tcp --dport 2037 -j DROP > iptables -A FORWARD -p udp --dport 2037 -j DROP > iptables -A FORWARD -p tcp --dport 3501 -j DROP > iptables -A FORWARD -p udp --dport 3501 -j DROP > iptables -A FORWARD -p tcp --dport 3531 -j DROP > iptables -A FORWARD -p udp --dport 3531 -j DROP > iptables -A FORWARD -p tcp --dport 3587 -j DROP > iptables -A FORWARD -p udp --dport 3587 -j DROP > iptables -A FORWARD -p tcp --dport 3955 -j DROP > iptables -A FORWARD -p udp --dport 3955 -j DROP > iptables -A FORWARD -p tcp --dport 4242 -j DROP > iptables -A FORWARD -p udp --dport 4242 -j DROP > iptables -A FORWARD -p tcp --dport 4661:4672 -j DROP > iptables -A FORWARD -p udp --dport 4661:4672 -j DROP > iptables -A FORWARD -p tcp --dport 4688 -j DROP > iptables -A FORWARD -p udp --dport 4688 -j DROP > iptables -A FORWARD -p tcp --dport 5121 -j DROP > iptables -A FORWARD -p udp --dport 5121 -j DROP > iptables -A FORWARD -p tcp --dport 5662 -j DROP > iptables -A FORWARD -p udp --dport 5662 -j DROP > iptables -A FORWARD -p tcp --dport 6085:6086 -j DROP > iptables -A FORWARD -p udp --dport 6085:6086 -j DROP > iptables -A FORWARD -p tcp --dport 6346:6347 -j DROP > iptables -A FORWARD -p udp --dport 6346:6347 -j DROP > iptables -A FORWARD -p tcp --dport 6699 -j DROP > iptables -A FORWARD -p udp --dport 6699 -j DROP > iptables -A FORWARD -p udp --dport 6881:6889 -j DROP > iptables -A FORWARD -p tcp --dport 6881:6889 -j DROP > iptables -A FORWARD -p tcp --dport 8473 -j DROP > iptables -A FORWARD -p udp --dport 8473 -j DROP > > > > <div class="gmail_quote">> 2010/6/4 Kaushal Shriyan <<a href="mailto:kaushalshriyan@gmail.com" target="_blank">kaushalshriyan@gmail.com</a>> > <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi, > > is there a howto for blocking p2p traffic on ubuntu 10.04 server ? > > Thanks, > > Kaushal > > -- > ubuntu-server mailing list > <a href="mailto:ubuntu-server@lists.ubuntu.com" target="_blank">ubuntu-server@lists.ubuntu.com</a> > <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-server" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-server</a> > More info: <a href="https://wiki.ubuntu.com/ServerTeam" target="_blank">https://wiki.ubuntu.com/ServerTeam</a> > </blockquote> </div> > > -- > Greyson Farias > Técnico em Informática - CREA/AC 9329TD > Ubuntu user > Eu prefiro receber documentos em ODF. > <a href="http://ubuntu.com/download/getubuntu" target="_blank">http://ubuntu.com/download/getubuntu</a> > Blog Ubuntu Acre: <a href="http://ubuntu-ac.org" target="_blank">http://ubuntu-ac.org</a> > </blockquote> > > </div></div></div></div> -- ubuntu-server mailing list <a href="mailto:ubuntu-server@lists.ubuntu.com">ubuntu-server@lists.ubuntu.com</a> <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-server" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-server</a> More info: <a href="https://wiki.ubuntu.com/ServerTeam" target="_blank">https://wiki.ubuntu.com/ServerTeam</a> </blockquote></div> Hi Again I did followed <a href="http://www.debian-administration.org/articles/562">http://www.debian-administration.org/articles/562</a> when i run the make command i get <a href="http://pastebin.ubuntu.com/445975/">http://pastebin.ubuntu.com/445975/</a> Please suggest/guide. Thanks, Kaushal