1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Access Restriction on port not working?

Discussion in 'Tomato Firmware' started by JonD, Mar 7, 2008.

  1. JonD

    JonD Network Guru Member

    My ISP caps my bandwidth if i go over 800Mb down / 400Mb up at peak times between 16:00 & 21:00, so I want to block bit torrent connections between these times.

    My bit torrent client is set to use ports 6881-6999 with UPnP disabled. I can see connections been made on this port in the QOS connection details.

    I have created an access restriction rule to block bit torrent connections from the machine between 16:00 & 21:00. However I can still see connections been made during this time and bit torrent is still uploading / downloading. I have tried various combinations of blocking port, IPP2P and layer 7 the only thing that works is when I select 'Block All Internet Access'. See attached image for full settings. Am I doing something wrong or is this a bug in the firmware?

    Currently running version 1.14, I will try the latest version tonight but not holding much hope for it fixing the problem as this issue has not appeared in the change lists.

    A great new feature for me would be the ability to set schedules to the QOS classification so I can restrict the bit torrent bandwidth between 16:00 & 21:00. Despite this problem Tomato is still miles better than any other firmware i've used on my WRT54G or any other router.
     

    Attached Files:

  2. JonD

    JonD Network Guru Member

    Done some more testing and I think it might actualy be blocking new connections but not killing existing ones?

    So when the rule becomes active it doesn't stop the torrents straight away, but if I stop the torrent and restart it then it can't get any connections. Unfortunatly this means my rule doesn't work so well since torrent connections can last a long time.

    Doesn't help that i'm using the bit torrent client on my NAS which has limited functions and connection details.
     
  3. bigclaw

    bigclaw Network Guru Member

    Instead of targeting bittorrent, which in your case is rather difficult, how about blocking Internet access for the NAS box as an alternative? Are you doing something else in the NAS that will be negatively impacted by this?
     

Share This Page