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

QOS for router conntecion

Discussion in 'Tomato Firmware' started by Yobo, Jun 26, 2008.

  1. Yobo

    Yobo Addicted to LI Member

    I'm using Tomato 1.19 on a WRT54GL.
    I'm using DropBear on the router to create an SSH tunnel to my office, and using port forwarding to connect to the office SMTP. So port 25 of the router is forwarded to some remote port 25 through this tunnel.
    Now to the problem -
    I want QOS to limit the upload speed of connections in this tunnel, so that sending large files won't clog the network. As far as I understand, Tomato's QOS ignores connection from the LAN to the router. The router's SSH connection does appear on the QOS list, and it is classified as "Medium", as it should. But it seems that the router isn't really prioritizing this connection.
    Is this observation true? Does anyone have an idea how this can be fixed?
  2. fyellin

    fyellin LI Guru Member

    QOS will ignore the port 25 connection from your mail server to the router, but it will still try to manage the port 22 connection between your router and the outside world. Is there any chance of your prioritizing this?

    Alternatively, you might be able to use a separate dropbear sshd listening on a second port. This second port can be used exclusively for your smtp encrypted traffic. In this way, you can apply a different QoS priority to your mail traffic and your other traffic.
  3. Yobo

    Yobo Addicted to LI Member

    Thanks fyellin.
    The port 22 connection appears in QOS list. For some reason, the source and destination get mixed up - i.e. the conenction *source* is my office with port 22, and the connection *destintion* is my WAN IP with some random outgoing port. (even though this is a tunnel created from the router to the office)

    Anyway, I can prioritize this connection using a rule for srcport=22. I set it to Medium, and this is how it appears in the QOS list.
    However, as far as I can tell, Tomato isn't handling this connection right and is not really prioritizing this connection. Perhaps this is some bug in Tomato?

Share This Page