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

Wireless trafic, too slow ?

Discussion in 'Tomato Firmware' started by Urko, Sep 28, 2006.

  1. Urko

    Urko Network Guru Member

    Hello.

    I must say i am very pleased with tomato firmware.
    I have an internet connection 12Mb/1Mb. The problem is that qos is much or less working, but when one of my wireless users is using torrent, or just downloading a file from internet, he's downloading with speed of 1,4MB/s, other clients have an bad ping to router (200ms, 400ms). What can i do, that the ping will be ok?
    Wireless client don't have very good signal, avg -68db.
    Thanks for your time.
     
  2. dvaskelis

    dvaskelis Network Guru Member

    "Bad ping" = high latency... but is that really bad? If this is under load, isn't that what's supposed to happen?

    If you're using QoS, the highest priority classes will have the lowest latency, the lowest priority classes will have the highest latency. Basically, ping uses icmp packets that are likely "Unclassified" traffic, which defaults to "Low" priority unless you changed it. So other traffic with higher priorities is going to come ahead of it, and make ping slower.

    If you just want high ping times, you could go all out configuring QoS to make icmp the lowest latency possible. Set up a QoS class for ICMP (it's the fifth entry on the protocol list, TCP/UDP is the first) for any address that's Highest priority and stick it on the top of the list. In QoS: Basic Settings, tell it to prioritize ICMP. And go wild, turn on the otherwise less-than-useful incoming QoS, make sure that icmp Highest class gets 100% of your bandwidth, maybe even give lower classes less than 100% so their packets get dropped in favor of "unused" icmp bandwidth.

    Do all that, and ping times will be sitting about as good as you can make them, with the lowest latency. And, as a free bonus, absolutely everything else you do on your network will be slower, choppier, and less reliable, but you can be proud of those lowered ping numbers! ;)

    Or, since icmp is rarely used in applications, take my advice and leave it alone. Ignore high ping times under load and accept them for the yummy goodness they represent: QoS working and your router prioritizing other traffic ahead of icmp. Many commercial routers default to icmp packets as below "bulk", basically last in priority and first to get dropped in case of squeezed bandwidth.

    With QoS, "bad ping" is a good thing.
     
  3. wycf

    wycf Network Guru Member

    If just one of your wireless client use heavy torrent download, you may try to set his MAC or IP address to lowest.
     
  4. Urko

    Urko Network Guru Member

    Thanks for the replays.
    I allready tried that. For example port 80(www) has High priority and if 3 or more users are starting downloading large files over http, they completly overlodad wireless transfer. I tried cople times what is the max speed at users and it gets max to 600KB/s, and then if one is just surfing the web that doesn't require much transfer, he get's slow page load.Maybe i'll tray each user set to low prioritiy, so that he'll could not reach transfer over 150KB/s. I have now all trafic set to Low priority,(Outbound Rate / Limit, 1% -4%) and when i run torretns i get about 150KB/s max downloading, the www, ftp and dns have High priority and then i get for downloading file over net 1,4MB/s :)
    I once tried to transfering file over samba, from one user which has a realy good signal and the max speed went to 1,1MB/s, I konw that is not the best way to test transfer,becouse samba uses additional pacets, that aren't file pacets.
     
  5. Urko

    Urko Network Guru Member

    Will this work if i ad that kind of rule to Qos classification
    Dest and Src IP 192.168.1.100 - 192.168.1.150
    Any protocol , any Port
    IPP2P disabled, L7 disabled
    Class Low
     
  6. dvaskelis

    dvaskelis Network Guru Member

    Don't think so. I think the basic implementation that Tomato's based on has iptables dealing with packets that cross the NAT firewall that routes between the WAN and other interfaces, hence the inbound/outbound designation. Otherwise I don't think the router is actually routing packets stricly on the LAN/WLAN, but instead is acting as a MAC-level switch for the LAN ports and a MAC-level bridge for the WLAN.

    It might be configurable manually through the shell, but if so, I'd start with MAC addresses, physical ports, and/or interfaces and not with IP addresses. I have never tried it.
     
  7. Urko

    Urko Network Guru Member

    Thanks i'll try it.
     

Share This Page