We are using the mikrotik os on routerboard as gateway for our wi-fi network. Wi-fi network is based on cheap equipment like linksys and is a roof-to-roof network, then inside the building we are cabling.
p2p traffic is shaped (mangle,queuetree+pcq) but there is a big problem on amount of connections the emule is opening, this sometimes block some of teh wi-fi equipments.
questions:
1- is someone setting up a similar network ?
2- is someone using wi-fi equipment with p2p ? any problem ? which equipment ? (we are a bit disperate about it having 1 equipment stcuk per day an dvery low performance)
3- how does work the emule system opening connections, I would like to limit to the appropiate number of connection each user on the emule and then firewall all other p2p programs. If on the dst-nat i put the limit-connection I should be limiting this ?? but which number is correct ?
4- in some cases my IP has been black listed by some emule servers..any idea why?
hope to find others with same problems and also some with teh solutions
many many thanks to all
Gianluca
Not really an answer to your question, but it is something similar I've found...
Emule opens a *lot* of connections and I have some trouble b/w limiting it...
For example:
I have a 128kbit/128kbit link. (I live in a b/w starved country and this is actually *good*)
I can b/w limit any traffic without any problems...It all works a charm. Limiting the traffic to 64kbit peaking at 128kbit (if available) for http and the same with ftp. If I have two http downloads and one ftp, I get 3.5k, 3.5k and 7k downloads, which is all hunky-dory.
However...
If I add a queue to limit p2p traffic (emule specifically in this case). I set it at 16kbit download and peaking at 128kbit if available.
If the http is on priority 5 and ftp is also on priority 5 and emule is on priority 8, then emule completely overwhelms any or all other traffic through that 128kbit link and uses 128kbit of it (more or less since the http downloads are sitting at 0.2k/s (if I'm lucky)).
If I set the peak rate at 96kbit then it will use 96kbit, no matter what traffic is going through the interface. The same happens for 64kbit and for 32kbit and for anything I set it to.
Ideally, if emule is active and a download starts on http, or ftp, then that traffic should get priority and should pretty much download at it's limit-at rate. ie. 64kbit. This does not happen.
One thing I did notice is that the examples in the manual, how-tos etc, all deal with a max-limit to limit p2p traffic to below the maximum line speed. None deal with a max-limit equal to the maximum line speed.
It seems as though emule creates so many connections out that it completely kills any sort of limiting on the system (if the max-limit is set to the line speed) (unless I'm missing something)
Maybe someone has a suggestion for myself and gianluca?
Emule opens a *lot* of connections and I have some trouble b/w limiting it...
For example:
I have a 128kbit/128kbit link. (I live in a b/w starved country and this is actually *good*)
I can b/w limit any traffic without any problems...It all works a charm. Limiting the traffic to 64kbit peaking at 128kbit (if available) for http and the same with ftp. If I have two http downloads and one ftp, I get 3.5k, 3.5k and 7k downloads, which is all hunky-dory.
However...
If I add a queue to limit p2p traffic (emule specifically in this case). I set it at 16kbit download and peaking at 128kbit if available.
If the http is on priority 5 and ftp is also on priority 5 and emule is on priority 8, then emule completely overwhelms any or all other traffic through that 128kbit link and uses 128kbit of it (more or less since the http downloads are sitting at 0.2k/s (if I'm lucky)).
If I set the peak rate at 96kbit then it will use 96kbit, no matter what traffic is going through the interface. The same happens for 64kbit and for 32kbit and for anything I set it to.
Ideally, if emule is active and a download starts on http, or ftp, then that traffic should get priority and should pretty much download at it's limit-at rate. ie. 64kbit. This does not happen.
One thing I did notice is that the examples in the manual, how-tos etc, all deal with a max-limit to limit p2p traffic to below the maximum line speed. None deal with a max-limit equal to the maximum line speed.
It seems as though emule creates so many connections out that it completely kills any sort of limiting on the system (if the max-limit is set to the line speed) (unless I'm missing something)
Maybe someone has a suggestion for myself and gianluca?