- This topic is empty.
June 29, 2010 at 7:25 pm #42471
ETH00 is WAN interface with public IPs and net balancing.
ETH01 is LAN with local subnet
Want to very simply throttle upload and download speeds with QOS for a single IP address on the LAN side, 192.168.1.1
Created two rules in Classifier
MARK all opt — in * out ETH01 0.0.0.0/0 -> 192.168.1.1 MARK set 0xf
to put 192.168.1.1 traffic going out LAN port in the slow queue
ETH00 MARK all opt — in * out ETH00 192.168.1.1 -> 0.0.0.0/0 MARK set 0x10
to put 192.168.1.1 traffic going out WAN port in its slow queue.
Whichever rule I put as Seq 1 works (traffic starts flowing down queue), while the other doesn’t (no traffic in that queue).
Is this due to the issue wth net balance vs. qos that I have seen referenced in this forum?
Thanks.June 29, 2010 at 11:14 pm #50580
I think your second rule is wrong. When packets go out of the WAN interface NAT has been applied so the source address no longer is 192.168.1.1. Better match incoming interface and source IP only. If you want to shape something you will have to do it when traffic goes from the high speed interface to the slow. There is no point shaping from the WAN to LAN.June 29, 2010 at 11:57 pm #50581
Are you suggesting that if I have a symmetric WAN connection, say 3 Mbps up and down, and I want to place some users in a queue that limits their upload speed to 512K, that I cannot do it with a rule on the WAN port?June 30, 2010 at 5:27 am #50582
I’m saying the opposite. You can shape the upload. What there is no point in doing is shaping the download, cause the packets have already arrived to you and there is no point dropping them and forcing your peer to retransmit them.June 30, 2010 at 12:20 pm #50583
I understand what you’re saying, now, but in terms of the end user experience, there is a point in queuing some incoming packets on the router. In this case, there are many users at a camp, and the office and admin needs have to be prioritized over the campers’ Facebook browsing. By putting all the campers in a 1 Mbps. incoming queue, the 3 Mbps. pipe does not get bogged down for other users. At least, that’s how it appears to work. Obviously, putting all traffic in a throttled queue would be pointless.July 1, 2010 at 6:29 am #50584
Then you need to shape all these to the uplink and allow them a fragment of bandwdth that will be enough according to you. Also instead of shaping you can simply police and thus limit the bandwidth.July 1, 2010 at 1:40 pm #50585
If you have a moment, I would love to hear more specifically what you mean by “police” and how that would be done.
Thanks.July 1, 2010 at 4:15 pm #50586AtroposXMember
I got a simple QoS bridge setup.
Make your bridge
Make your classes as needed, say 1meg, 768k, etc. in the class manager.
In the QoS interface manager, add the “upload” speed, say the 768k, to the ETH02, and the “download” of 1meg, to the ETH03 interface, save and activate at the top.
Go to the QoS classifier, new, add a “Download” rule that is src=blank, and dest= the host ip, or subnet, then choose the target class of the 1meg.
Then make a new rule, in reverse, for the “upload”. src=the host ip/subnet, and dest=blank, and choose the 768k target class.
Then choose save at the top.
Or you can create just one class called, say 5meg, and add it to both the ETH02 and ETH03, then create the same rules, but point towards the same 5meg class on both rules. If using a subnet, then this entire subnet will share an symmetric 5meg service. Fun stuff.
I don’t have net balancing though, just a basic bridge, not sure if that matters.July 2, 2010 at 2:20 pm #50587
Thanks AtroposX, I have several zeroshell routers with similar setups and all works great. This is the only one using net balancing, and it seems to interfere with the QOS functionality.July 2, 2010 at 2:42 pm #50588AtroposXMember
you could try Atheling’s patch:
or perhaps when the next release, comes out, it should/may have the patch already applied?
- You must be logged in to reply to this topic.