I’m new to the MikroTik RouterOS and I am very suprised at the great functionality of it.
Nevertheless I have a small problem for which I am not really happy with the documentation.
I am using a routerboard RB153 with two Atheros a/b/g wireless cards.
One of these cards (WLAN2, IP 192.168.1.9) forms a long range wireless link to my backbone net and the other card (WLAN2, IP 192.168.9.1) forms a wireless access point where clients with diffrent kinds of hardware can connect to. Authentication is made on a MAC basis and encryption is done with WPA-PSK and AES cipher.
My problem now is to limit the network bandwith of each client connection to a certain value - e.g. my overall bandwidth to the internet is 16MBit/s download and 1MBit/s upload and I want to limit the bandwidth for the clients to 2Mbit/s down and 256KBit/s up.
It would be very nice if someone could give me some hints on how to proceed with this problem.
Unfortunately I don’t have MT ROS routers as CPE. So I can’t use the “default-tx/rx-limit” feature in the wireless settings.
I did my first tests with a simple queue. As queue- type I use PCQ and use the target address of my wireless net of WLAN1 (192.168.9.0/24).
But when I use WLAN1 as interface for the queue only the download is limited properly. Only if I use my WLAN2-ETHx-Bridge the limitation works in both directions.
My concern is now: Is this really a per client limitation when I attach this queue to the “other side” of the router - or what did I wrong?
Because the manual is not really satisfyingly to me in this topic I have also the following question:
Do you know any kind of a third-party-documentation to this or can you give me some more hints what I can do here?
I’m wondering if limiting traffic on the AP-Side does really help
saving Bandwidth at the WLAN.
The client sends traffic which the AP drops. If there is no mechanism
to stop the client sending it may reduce Backbonetraffic but not
the traffic on the local WLAN.
I’ve seen this with simple queues at the AP. There were a lot of
drops at the AP. I want to have this already dropped at the
client to save bandwidth to the other clients.
The mechanism I know is ICMP Source Quench. But it doesn’t
seem to work as expected.
Thank you for your reply. I will study the examples carefully.
@stefan
The main use of our network ist to bring broadband internet connections to rural areas arround my hometown where the big players can’t provide such services. So the aim of this limitation is not to save bandwidth for the WLAN cell itself but to shape the traffic for the DSL connections that are in- or outgoing to and from my backbone net.
As you don’t have a chance to control the traffic at the CPE it is the best to do it at the AP.
the easiest way I’ve found to limit traffic at the CPEs is the use of Radius Manager. It builds the simple queues dinamically when the client makes the autentication request. However I use the AP as pppoe-server with radius autentication.
We have about 600 CPEs connected on various AP and the Radius Manager still work fine…
Are these simple queues installed at the CPE or the AP?
I would like to install simple queues at the CPE which limit excessive
usage. The normal surfing user should not notice anything at all.
The p2p or netbackup user (some poeple copying there whole disk)
should be limited down to 1MBit until he reduces his traffic again.
So the burst stuff would be the way to go. (I’ve to read and understand
the exact behavior before I’ll implement this).
the Radius Manager builds a simple queue for any CPE (e.g. 1MB download and 256 KB upload regarding that you need) on the AP without the client knows this.This don’t limit the bandwith on the wlan but only on the end-user.
Only you need that the CPE supports pppoe-client.
