Quote from Trader13:Have you tested a downtime scenario? For example, just unplugging one of your network services and watching it failover to the other...
Yes, very interested in this as well since I've never owned one.
Could you unplug your WAN0 and let us know how long it takes a machine on the LAN to failover and resolve on WAN1?
Quote from lwlee:One of the selling points was that it had gigabet ethernet ports.
Not trying to be Debbie-Downer about the gigabit ports but the Peplink website clearly states that the Peplink 20 through 310 can only handle 100mbps throughput.
Since best-practices would assume that you never directly connect a computer or server to your router/firewall why not base your decision on your connection speed and the actual ability of the router/firewall to push data at 10/100/1000 speeds (can the Peplink 20 push data at a sustained gigabit speed across the lan (routed through the router)?
Here is an example of what I mean:
http://www.smallnetbuilder.com/lanw...-features-but-slow-downloads?showall=&start=3
If you have a T1 connection at 1.54mbps a cheap Linksys WRT54GS running DD-WRT could be an awesome router solution for $20. You can attach a gigabit (or even 10GbE) switch to this and push data across your LAN at stupid fast speeds. The Linksys WRT54GS tops out around 25mbps throughput (even though it has 10/100 ports) so you would be well over the capacity of your internet circuit.
Routers & firewalls have CPUs in them just like computers. Most of the time routers & firewalls can not sustain anywhere near the throughput of the interface advertisements (they can't push gigabit speeds but have gigabit ports).