| Main Menu|
Warning, before you untar the Arbitrator releases please read the How-To. Also any items in the Changelog relating to the version.
. arbitrator9.62.tar.gz this is the GPL version. It does not come with a GUI, nor is reporting included in this version. Those items are licensed with our commercial products only. This version runs on the Linux 2.6.5 kernel. No other patches are required since iptables and ebtables are already in this kernel. READ THE CHANGE LOG FOR INFO ON THIS VERSION.
. arbitrator8.63.tar.gz this is the GPL version. This is currently the most stable version based on the 2.4.19 kernel. It does not come with a GUI, nor is reporting included in this version. Those items are licensed with our commercial products only. This version runs on the Linux 2.4.19 kernel. READ THE CHANGE LOG FOR INFO ON THIS VERSION.
. callnetplot version 1.0 for plotting MULTIPLE VLANs This is a user donated perl script which should be used with 8.25. Other versions may be able to be tweaked to use this as well with a little work.
Version 1.21 is a watchdog utility type program for the Arbi. You can read the README by clicking here.
This is a beta release and we welcome beta customers. Enforce Bandwidth Caps on monthly/daily or hourly
usage, take actions when caps are exceeded. You can read the README by clicking here.
This is a beta release and we welcome beta customers. You can find the docs for ArbiQos by clicking here.
. apccrond - Perl cron like helper app
. asciiplot2.0 - Perl plot routine that creates ASCII graphs in the form of horizontal bar charts. You could modify the code to output graphics instead of ASCII *'s for use with web apps. Here is the README.
. bridge-nf-0.0.7-against-2.4.19.diff for the 2.4.19 kernels.
Off site links
. 2.6.5 Kernel Source
| Linux help links|
|| webguisetup: Arbitrator Web GUI setup|
The arbitrator GUI interface is provided by a Web Server running on your arbitrator. It may be accessed from any standard browser.|
Starting the GUI interface.
Please read the section on security precautions before running your Arbitrator GUI on a network with uncontrolled or external access.
Make sure your machine has an IP address. An IP address option was available on start up.
Starting your web server requires you type these 5 commands from the command line.
tar zxfv /art/webgui.tar.gz
cp etc/thttpd.conf /etc
Once you have done this , go to your nearest browser and go to
http://x.x.x.x/arbi Where x.x.x.x is the IP address of your Arbi.
From there you have access to the full set of all the admin commands described in this document.
More advanced things you can do with your GUI
You can also look at and edit if desired the file /var/www/etc/thttpd.conf before you copy it to /etc and before you start thttpd and use another port for the web server.
You can also put all of the setup scripts into arbiext on the floppy so that the web GUI will be started upon a reboot. Please read and understand the security precautions!
Please be advised the Web GUI version of the Arbitrator CD contains a full functioning web server. APconnections has provided a simple set of instructions above, to bring up the server. We have purposely decided not to have the web server start up on default installations to allow our customers to first setup safeguards to help prevent any potential risk to their network security. Some suggestions for limiting the risk of having the web GUI available remotely are below.
There is a file /art/arbifw that contains a sample firewall rule or two that may help prevent unauthorized use of the web servers port from machines other than the ones you want to get to it.
Quick Fact: These instructions are taken from standard Linux Firewall utilities, they may be typed in directly from the command line.
iptables -A INPUT -i my -s 192.168.1.100 -j ACCEPT
iptables -A INPUT -i my -s 192.168.1.101 -j ACCEPT
iptables -A INPUT -i my -s 192.168.1.30 -j ACCEPT
iptables -A INPUT -i my -p tcp --destination-port 80 -j DROP
First the -F flushes out any existing firewall rules.
Then the next 4 rules allow machines on IP's 192.168.1.100, 192.168.1.101 and 192.168.1.30 to access ANY port on the Arbitrator machine and if a machine is not in this list and they try to go to port 80 (the default thttpd port) then drop that request. You may want to just enable those 3 machines to access port 80 and maybe the SSH port and not all ports. More in depth firewalling is beyond the scope of this document and you should consult a professional on firewalling if you are not already comfortable doing this yourself.