 |
||||
|
|
|
||
|
Contents 
Introduction
D-Link
Dynalink
Netgear
Nortel
Linksys
Allied Telesyn
Specifications
How we tested
Sample scenario
Editor's choice
About RMIT |
|
||
|
|
||||
|
|
||||
Setting up the hardware was easy -- you basically have to plug your phone line into the back of the unit then run a network cable from the unit to your PC. DHCP wasn't enabled on this router so we couldn't see the router until we manually set the IP address of our PC.
Once we could see the router we followed the Quick Start menu to get things rolling. You first have to set the encapsulation and multiplexing parameters and from there you enter your ISP login and password details and then apply the settings. We actually thought this all would have been enough to get it running but not so! In fact we had to resort to contacting the vendor for help and only after a few attempts did we manage to get it all working.
The quick install guide fell well short of providing enough information to help us configure the router. By our understanding it's a new product so there may be some kinks that still need to be ironed out by Allied Telesyn.
As for the rest of the installation, we had set the interface to accept remotely assigned addresses, setup the firewall, NAT, set DHCP, and then create traffic policies so we could see beyond the LAN. It sounds a bit painful and it was, especially compared to the other units, but then again how often would you have to setup your firewall from scratch?
The AR44OS comes with traffic filtering capabilities, giving you control over traffic that passes through the unit. VPNs are supported using AES as well as DES and 3DES. Software quality of service and traffic shaping features were included in this release. In the area of monitoring, management, and diagnostics this unit is really well equipped. The diagnostics in particular can display traffic counters for layers 1, 2, 3, and 4.
|
|
||||||||||||||||||||||||||||||
Way to compare Commodore's or a Falcon's with a Porsche ZDNet.