Quick Start Guide
APconnections, Inc. // 303.997.1300 //
www.netequalizer.com
Page 10 of 14
All rights reserved
Copyright © 2010 to 2015 APconnections, Inc.
rev. 20141125
Step #4: Controlling Peer-to-peer Traffic (P2P)
Many customers have an overload of connections on their network due to P2P file sharing applications. To alleviate
this problem, we suggest setting Connection Limits, which will limit the number of connections (IP pairs) for a single
IP address or an entire Class B or Class C subnet. Connection Limits will restrict traffic whether it is encrypted or
unencrypted P2P. Connection Limits are bi-directional; any limit you set is divided in two and applied. For example, a
Connection Limit of sixty (60) is thirty (30) inbound and thirty (30) outbound connections.
We recommend monitoring your installation for several days before setting Connection Limits. That way, you can
better understand how many inbound and outbound connections you need to support valid activities on your network.
For example, some online games require 60 or more total connections, without being P2P traffic. If you wish to allow
this type of activity, you would need to set your connection limits to 60.
Step #4A (optional): Configure Connection Limits
Monitoring Connections
You can monitor connections using the following command. In this example, we are looking at users
with > 10 connections. You can change this value.
Click on ->
Maintenance
->
[
Run a Command
]
and
then
type in:
/art/count 10.
This will display all IPs that have more than ten (10) connections in either direction,
possibly running P2P. You can check periodically over several days to decide which (if any) IPs to connection limit.
Set Connection Limits
Click on ->
Manage P2P Traffic
->
[
Configure
Connection Limits
]
. The screen to the right comes
up.
Type in your IP address:
To set for an individual IP, use /32.
To set for a Class B subnet, use /16.
To set for a Class C subnet, use /24.
Type in a Value, which is the total number of
connections per IP or subnet. Connection Limits are
bi-directional. The Value you enter is divided in two and
applied to the rule.
Click on ->
[
Add Rule
]
to save changes or
Click on ->
[
Reset
]
to discard changes.
To check that your changes have been applied,
Click on ->
Manage NetEqualizer
->
[
Manage Configuration
]
->
[
Show Configuration
]
. You will see one line in your configuration file for each Connection Limit that you have set.
For example, if you entered a connection limit for Host IP: 10.0.1.25 and /32 (individual IP limit) and Value=60, you
would see the following line in your file: CONNECTION 10.0.1.25/32 30 0. Note that the limit has been divided in two
(30 inbound, 30 outbound). When you implement Connection Limits, once a user has reached their limit ALL NEW
connections for that user will be forbidden. In the example, once 30 inbound or 30 outbound is reached, no new
connections will be allowed. If you have a user call to complain about email or webpages not working, it may be that
the user has reached their connection limit.
Congratulations!
Your NetEqualizer should now be up & running, actively reducing congestion on your network.
Notes
:
Set Individual Connection Limits for special servers like DNS or Web Servers if they are part of a subnet that is
being connection limited. Set to a high value, such as 3000.
Connection Limits apply to all IP's within the range specified, even those that are set up as a Priority Host, but will NOT apply to
MASKED IP addresses. See
User Guide
to learn more about MASKED IP addresses.
