Community discussions

 
brundier
just joined
Topic Author
Posts: 23
Joined: Thu Sep 21, 2006 9:04 am

Port(s) of P2P

Fri Aug 10, 2007 5:37 am

Another P2P thread, just wanna know thereis any default port that using by P2P so we can block it at all? Cause i just put :
/ip firewall chain=forward p2p=all-p2p action=drop
and its not help at all, so it`s better to block port that P2P use at all... anyone please?
 
titius
Member
Member
Posts: 338
Joined: Mon Oct 17, 2005 11:43 am
Location: Titel Serbia

Re: Port(s) of P2P

Fri Aug 10, 2007 12:12 pm

1024<>65535

p2p software uses random ports so, block all ports between 1024 and 65535, and then, forward ports that your customers nedd, for example 6667 port, or whaterver, that is the best solution for fighting p2p.
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 24268
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: Port(s) of P2P

Fri Aug 10, 2007 3:33 pm

or you can just allow the ports you need, and block everything else. allow like 80, 443, 8080, 21, 22, 23 and something else you might require. block the rest :) drastic but effective.
 
abab_rafiq
Member Candidate
Member Candidate
Posts: 120
Joined: Thu Aug 24, 2006 12:47 pm
Location: Dhaka

Re: Port(s) of P2P

Sat Aug 11, 2007 2:03 pm

If your p2p-all is not work here then port blocking doesn't make any sense.. I think.

Test with kazza of port 1214.

Rafiq...
 
User avatar
cpresto
Member Candidate
Member Candidate
Posts: 172
Joined: Tue Jul 18, 2006 3:12 pm

Re: Port(s) of P2P

Wed Aug 29, 2007 8:01 pm

Apply mangle to all known traffic is what I'm currently doing and it works quite good, but avery day ports need to be opened to allow newer applications (vpns, custom applications, voip, ...).
Actually I do mangle as follows:
## known traffic-->mark connection(known)-->mark packet(known)-->mark routing(known)
##unknown traffic-->mark connection(!=known)-->mark packet (unknown)

all unknown traffic goes through default gateway and is shaped with a simple queue.

I would like to apply a new mark routing to unknown traffic, in order to route it to a router different from default gateway:
##unknown traffic-->mark connection(!=known)-->mark packet (unknown)-->mark routing (unknown)

Despite the fact that new mark routing rule works (it is matched), this configuration doesn't work: traffic seems not be accepted into simple queue.. :?

Any idea?

Rgds
 
User avatar
ghmorris
Member Candidate
Member Candidate
Posts: 284
Joined: Fri May 28, 2004 12:14 pm
Location: Minden, Ontario, Canada
Contact:

Re: Port(s) of P2P

Thu Aug 30, 2007 1:02 am

We were having a severe problem with encrypted PtP on Port 80 pretending to be HTTP traffic.

This is probably the worst scenario you can imagine. The problem BitTorrent clients capable of encrypton are the newer versions of uTorrent, Azureus and BitComet.

MT couldn't find this stuff at all. We had fair results with connection aging, but yesterday gave up and bought an appliance. Today, no problem with PtP. Closest thing to magic I've seen in years.

I love my MTs, but the new-generation encrypted PtP is tough going.

George
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 24268
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: Port(s) of P2P

Thu Aug 30, 2007 9:09 am

we will work on improving the p2p matcher in v3, something similar to the mentioned L7 filter

Who is online

Users browsing this forum: Petrw and 100 guests