HogStopper.com  Home
How It Works  

Online Demo
How It Works
Contact Us

For more
 information contact
Extensive Networks,
an Authorized NetEqualizer Reseller



The NetEqualizer is a brilliant solution
 to a critical problem

The secret!
Almost all internet communications have a client server model where the client is sending requests and the server is sending data. This is true for ftp transfers, streaming video and streaming audio. Even if the client and server are sending UDP packets there is always a client server relationship. It so happens that the slowing or delaying the client requests is a much better way to throttle the data back than slowing the data coming from the server. The biggest advantage to slowing down client requests is that you get at the source of traffic problems without employing complex queuing algorithms. 

The NetEqualizer Bandwidth Manager uses a version of the Linux operating system with two modifications to the kernel. The first modification is the use of a "brain table". This is a list of active Internet connections and is the heart of system. All the decisions the NetEqualizer makes is a result of analysis on the content of this table. The size of the "brain table" can be changed based upon the size of your network.  

The second modification inserts a set of queues that is used to slow packets down by imposing a penalty. The NetEqualizer reads the content of the brain table every second and does analysis. It then makes a decision based on if there is any bandwidth abuse going on. If it decides there is bandwidth abuse occurring, it levies a penalty on a specific set of IP addresses (source and destination). When a penalty is in effect, all packets are delayed from 10 to 1,000 milliseconds, thus slowing down the traffic and reducing the bandwidth used. The penalty is only levied against subsequent packets with the specific IP source and destination address and after a short time, the penalty expires.   

To set up bandwidth shaping
There are five basic options used to set up bandwidth shaping.  

1) Generic (Don’t touch that dial this is the default). 
Looks at any internet connection regardless of port and scales back bandwidth based on the default rules.
The default rules do the following: 
        Looks at the trunk size
        Looks at the number of active users (ip to ip connections)
        Looks at the persistence of a user to determine if the activity is just a burst, (like a web page) 
        or a big stream
        Then it makes a decision to throttle-down the bandwidth for those users who are consistently 
        using more than their fair share.

2) PRIORITY Percent
When a priority host is active the arbitrator throws out all the generic rules (above) and basically says “if I have a PRIORITY host active then slow down everybody else”, kind of radical so use it sparingly. But if you have a user that must take priority on a busy trunk (VOIP traffic for example) you can insure they will get through at the expense of all other users.

This mode only allows a user up to a specified percent of bandwidth on the trunk. The generic rules stay in effect simultaneously so a user could get slowed by a "generic" rule before reaching its limit. Traffic can also be limited on either the uplink or downlink side.

4) LIMIT by Service (ftp, http etc)
In this mode the NetEqualizer limits the bandwidth on your trunk used for a particular application to a percent of the trunk. If the combined traffic of all the users using this service exceeds the set percent they are collectively scaled back. You also have the option to set a time period for the shaping command to be in effect. For example you can limit ftp downloads to 10 percent of your bandwidth between 1:00 and 2:00 pm. 

The NetEqualizer comes with application shaping for most of the popular P2P file sharing programs. You can shape traffic generated by Kazaa, Gnutella and others.