Logging and other Routing features
The 4300's logging is actually pretty good and includes the ability to email logs when full, on demand or on a schedule you can set, and you can also send them to a syslog server. As Figure 10 illustrates, you can limit log entries to particular categories and the log entries themselves are relatively understandable.
Figure 10: The Log interface
(click image to enlarge)
But Figure 10 also illustrates the main weakness of the 4300's logging - that everything ends up in one big pile that it's up to you to wade through to find information of interest. This problem gets even worse when you enable logging Internet access in the Access Control section.
Before I move on to drill down into the Gamefuel features, here's a bullet list of other features of the 4300's routing section:
- VPN passthrough for multiple clients to multiple remote gateways is supported for PPTP, L2TP and IPsec VPN flavors
- You can define up to 32 static routes and control whether RIP dynamic routing information
- There's a built-in dynamic DNS client for 10 different services including the ever-present dyndns.org and TZO.com
- You can reboot and reset the router to factory defaults from the web interface