Change QOS terms from 'Inbound' and 'Outbound' to 'Download' and 'Upload'.
Those are more common terms.
Asus RT-N12 with TomatoUSB
Actually, router-centric naming (Inbound/Outbound) makes more sense.
I've seen occasional newbie confusion with inbound/outbound. Instead of changing them, perhaps download/upload can be added as part of the label, in parentheses.
"Download" and "Upload" both imply the transfer of files, and this is even more confusing, not just to the poor newbie, but to all and sundry. Inbound and Outbound seem to me to be very difficult to misunderstand since the terms are in common usage worldwide for buses, trains, airplanes, etc.
Or maybe we should put Coming and Going :-)
Download site http://www.4shared.com/dir/v1BuINP3/Toastman_Builds.html (inc. torrent downloads)
Make a Paypal Donation http://toastmanfirmware.yolasite.com/donations.php
I like the idea of putting download/upload in parentheses.
The again, maybe the wording should be shortened to "in"/"out" with the goal of keeping the needed flash size down.
Asus RT-N12 with TomatoUSB
Maybe Send / Receive.
Sigh……I had a medium-long post this morning but it got lost.
At my previous employer, my department did communications controllers for 30+ years. We were all well-versed in what we were doing, but even we got confused all the time. Problem is the point of view, whether your POV is inside the controller (router) or outside it (PC). And your POV keeps changing all the time, depending on what you happen to be focussing on at the time.
We were continually amused by managers who couldn't understand why we talked about "receiving an outbound messages" or "transmitting an inbound message". Then in the next breath we'd talk about "transmitting the outbound message" and "receiving the inbound message". The one who were convinced that managers knew more than programmers would try to correct us stupid engineers: "No, you SEND outbound and RECEIVE inbound". So then we'd try not to snicker, and asked them what our box did after it RECEIVED an inbound message—-what do you call it when we pass it along to the user host computer? Don't you, like, SEND the inbound message to the host computer? Then we'd roll our eyes. ;-)
It's just like when you hook up a serial cable/adapter to a router. The router TX pin goes to the adapter's RX pin. People are continually wanting to connect TX to TX and RX to RX.
GoBruins is right. router-centric naming (Inbound/Outbound) makes the most sense.
Maybe "From WAN" and "To WAN" would be better. After all for a router inbound, outbound, uploading, and downloading are all ambiguous. e.g. The data is incoming to the router from my laptop on the lan. It is outgoing from the router to an internet web site on the wan. Is that Outbound or Inbound? I send data from my laptop though the router to my desktop on the lan, is that inbound, outbound, or does not count?
Normally I would think LAN-to-LAN transfers wouldn't count. But then on DD-WRT if my WAN went down, I could not play movies on my media player without turning off my QOS. I considered that a bug with DD-WRT. Does Tomato USB have the same behaviour. I don't know. But I do know when I go to QOS and view the graphs, most of the unclassified traffic in the chart is LAN-to-LAN. Since I would not expect LAN-to-LAN traffic to even show-up in the graph, I am suspicious about what the terms really mean…