Port forwarding and filtering problem

RouterOS Beginner Basics
1

I have two scenarios, both seem to be creating the same problem.

Initially I forwarded my BitTorrent port (29999) to my computer.
Command is:

add action=masquerade chain=srcnat comment="" disabled=no out-interface=ether1 
add action=dst-nat chain=dstnat comment="" disabled=no dst-port=29999 in-interface=ether1 protocol=tcp to-addresses=192.168.1.200 \
    to-ports=29999 
add action=dst-nat chain=dstnat comment="" disabled=no dst-port=29999 in-interface=ether1 protocol=udp to-addresses=192.168.1.200 \
    to-ports=29999

(Using Vuze/Azureus client). Vuze has a simple check to see if your port is forwarded, and this passed. Also, my torrents show fully healthy status and I get good download rates. The problem is it seems all other network traffic slows down or is disrupted. Web sites will sit for several seconds and then load, my messenger clients get knocked offline and rejoin, etc. As soon as I close my torrents, everything is fine.

Second: I was attempting to block the port used for World of Warcraft ( :smiley: ) during the day using the filtering with the time component.
Command is:

add action=drop chain=forward comment="" disabled=no dst-port=3724 icmp-options=0:0-255 protocol=tcp time=8h-17h,mon,tue,wed,thu,fri

When this is enabled, the same situation as above occurs. I’m not sure what I’m missing with these commands, but something is not right.

2

I suggest you to make separate topics for different problems, this will make answering easier.

The problem is it seems all other network traffic slows down or is disrupted. Web sites will sit for several seconds and then load, my messenger clients get knocked offline and rejoin, etc. As soon as I close my torrents, everything is fine.

Seems to me that your torrent program is either eating up all your bandwidth, or making too many connections. You should prioritize the HTTP traffic by making a queue with a minimum speed for it, and another Queue for the rest of the traffic (this means also torrents). You can’t put speed limits on just torrent traffic, if it’s encrypted (mostly is).

Second: I was attempting to block the port used for World of Warcraft ( ) during the day using the filtering with the time component.

This is certainly weird, I have no idea what could cause this.