is there way of putting 1gb download limit for each clients
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
is there way of just giving 1gb download limit, like when he pass that 1gb, his/her is disconnect?
The third party metering program would need to be on a device between the WAN and the switches, almost like a firewall device. It would monitor sending clients and give them limits on download as needed, once limit is hit the firewall blocks that traffic
Ive set it up before and it does work, but its not a common solution if honest.
Im Omada like most networks its not about the volume of traffic being downloaded, rather controlling the speed it can download at. This comes in two flavors
Session Limits and Bandwidth Controls
Session Limits are the number of simultaneous sessions allowed, this can be set per device or network. Say someone opens a torrent and you have a session limit of 5, once 5 peers start sending that user the torrent it wont allow any more sessions to open. Its not specifically for torrents, will affect video streams, web browsing, email etc. Its basically a way of stopping one user taking total control by using hundreds of small connections.
Bandwidth Controls are as they state, a throttle on the bandwidth. Say you have 100mbps down and 50mbps up, you can restrict users to only being able to utilize a max of 70 down and 30 up so as not to exhaust your connection, the extra free bandwidth can be allocated to another user or VLAN. This can be set as Shared or per Device, eg in a guest setup you could allocate 80mbps and all users fight over it (shared).. or set it as 2mbps and each user gets just 2 regardless (per device). Shared is generally the easier way to manage it
Hopefully that helps?
The third party metering program would need to be on a device between the WAN and the switches, almost like a firewall device. It would monitor sending clients and give them limits on download as needed, once limit is hit the firewall blocks that traffic
Ive set it up before and it does work, but its not a common solution if honest.
Im Omada like most networks its not about the volume of traffic being downloaded, rather controlling the speed it can download at. This comes in two flavors
Session Limits and Bandwidth Controls
Session Limits are the number of simultaneous sessions allowed, this can be set per device or network. Say someone opens a torrent and you have a session limit of 5, once 5 peers start sending that user the torrent it wont allow any more sessions to open. Its not specifically for torrents, will affect video streams, web browsing, email etc. Its basically a way of stopping one user taking total control by using hundreds of small connections.
Bandwidth Controls are as they state, a throttle on the bandwidth. Say you have 100mbps down and 50mbps up, you can restrict users to only being able to utilize a max of 70 down and 30 up so as not to exhaust your connection, the extra free bandwidth can be allocated to another user or VLAN. This can be set as Shared or per Device, eg in a guest setup you could allocate 80mbps and all users fight over it (shared).. or set it as 2mbps and each user gets just 2 regardless (per device). Shared is generally the easier way to manage it
Hopefully that helps?
If you set portal authentication, you can set traffic limit for one voucher code, portal authentication need the Controller running online all the time, it's a little complicated but can achieve your need.
