In internet we can find many tips and tricks that are aimed to increase traffic of a website. But it is also become the problem when our website own over traffic. It is because most of the visitor who are come to website want to pick the data that they can done by downloading.
This is what had happened to some of my websites which are located in a server. They have to many impressions as I put some facilities that can be put by every people. It reach until 2000 impression per day meanwhile our server can’t work nice because of the limitation bandwidth.
It is really made me confuse since I have done t
he additional bandwidth for my server until 10 GB but it still can’t solve my problem. This may be possible to come to your website as the bandwidth limitation of your server.
But since yesterday I can sleep well I believe that it won’t happen again to my website. How could it be?
Yesterday I decide to buy virtual server which has unlimited bandwidth capacity. By this virtual server no doubt again to increase and increase my traffic or impression. This is the best solution of my problem than I must take the addition and addition bandwidth which is more expensive when I calculate it.
I say that this is the best way since I realized that my earning that I get over these website is increase during the increase of my websites traffic. Like the revenue of Google adsense which increase fast.
So when you have a website that high impression ensure that your server still able to solve it. This is because some thing over is scourge for you although you hoped to own website with so high traffic. But with unlimited bandwidth virtual server huge impression or traffic is not something over but this is your website wakeness to get the huge income over it.
Incoming search terms for the article:
impression traffic trick (1)
Bandwidth limit can be set up using WISPr Attributes. Two attribute can be used for this purpose, which is
- WISPr-Bandwidth-Max-Down
- WISPr-Bandwidth-Max-Up
These attribute must be define in radreply table or radgroupreply table. Operator := is commonly used, but I figure out that == operator can be use also.
Lets say we want to limit a user bandwidth to 256kbps for download and 32kbps for upload. So we define in the radreply table:
WISPr-Bandwidth-Max-Down := 256000
WISPr-Bandwidth-Max-Up := 32000
However, bandwidth limitation is not successful yet by just applying these attributes, this is because our network users session is being routed in two way to go to Internet, using NAS internal ip (in my case br0) and NAS tunnel (tun0). Seems the br0 interface have more priority than tun0, and it packets will always being routed using this interfaces. This is not good as the attribute we set is only applied to tun0 tunnel which is created by Chillispot.
To overcome the situation we must force all packets to be routed using tun0. We can apply some firewall rules to help us achieve this. Below is the rules I used.
# iptables -P FORWARD DROP
# iptables -F FORWARD
# iptables -A FORWARD -o tun0-j ACCEPT
# iptables -A FORWARD -i tun0 -j ACCEPT
So when I list back the policy for Forward Chain in the Iptables, I’ll get this:
# iptables -nvL FORWARD
Chain FORWARD (policy DROP 17 packets, 1088 bytes)
pkts bytes target prot opt in out source destination
0 0 ACCEPT all — * tun0 0.0.0.0/0 0.0.0.0/0
0 0 ACCEPT all — tun0 * 0.0.0.0/0 0.0.0.0/0
By this rule, the bandwidth will be shape according to what we set in radreply/radgroupeply table. We can test this using iperf command.
So for the upload testing this is what i got:
$ iperf.exe -c 10.20.20.1 -i 10 -t 60
——————————
——————————
Client connecting to 10.20.20.1, TCP port 5001
TCP window size: 8.00 KByte (default)
————————————————————
[1912] local 10.0.1.4 port 3834 connected with 10.20.20.1 port 5001
[ ID] Interval Transfer Bandwidth
[1912] 0.0-10.0 sec 64.0 KBytes 52.4 Kbits/sec
[1912] 10.0-20.0 sec 40.0 KBytes 32.8 Kbits/sec
[1912] 20.0-30.0 sec 40.0 KBytes 32.8 Kbits/sec
[1912] 30.0-40.0 sec 40.0 KBytes 32.8 Kbits/sec
[1912] 40.0-50.0 sec 40.0 KBytes 32.8 Kbits/sec
[1912] 50.0-60.0 sec 32.0 KBytes 26.2 Kbits/sec
[1912] 0.0-65.4 sec 264 KBytes 33.1 Kbits/sec
And this is for download test:
$ iperf -c 10.0.1.4 -i 10 -t 60
——————————
——————————
Client connecting to 10.0.1.4, TCP port 5001
TCP window size: 16.0 KByte (default)
————————————————————
[ 3] local 10.20.20.1 port 60918 connected with 10.0.1.4 port 5001
[ 3] 0.0-10.0 sec 568 KBytes 465 Kbits/sec
[ 3] 10.0-20.0 sec 312 KBytes 256 Kbits/sec
[ 3] 20.0-30.0 sec 296 KBytes 242 Kbits/sec
[ 3] 30.0-40.0 sec 312 KBytes 256 Kbits/sec
[ 3] 40.0-50.0 sec 288 KBytes 236 Kbits/sec
[ 3] 50.0-60.0 sec 264 KBytes 216 Kbits/sec
[ 3] 0.0-60.3 sec 2.00 MBytes 278 Kbits/sec
Finally, we managed to set up bandwidth limit for our network users. However, there is a problem in the way, traffic burst happens when everytime an object is retrieved from the Internet. Imagine a web page that contains 20 objects, there will be 20 traffic burst to happen. The traffic will make the traffic looks inaccurate when being test using bandwidth tester. Except, if we could excluded the beginning of the data transfer from the test, the bandwidth test will looks more accurate.
Incoming search terms for the article:
WISPr-Bandwidth-Max-Down (132),
WISPr-Bandwidth-Max-Up (74),
freeradius bandwidth limit (51),
freeradius WISPr (26),
freeradius limit bandwidth (26),
freeradius traffic limit (23),
freeradius bandwidth (21),
freeradius iptables (18),
WISPr freeradius (16),
freeradius WISPr-Bandwidth-Max-Up (13),
radius bandwidth limit (12),
wispr 2 0 (11),
chillispot bandwidth (10),
pfsense radius bandwidth (7),
WISPr bandwidth max up (6),
freeradius bandwidth management (5),
freeradius download limit (5),
radius bandwidth control (4),
pfsense radius bandwidth limit (3),
pfsense limiter (3)
