Forum OpenACS Q&A: Re: OT: Best home-office router?
One thing it does not seem to have is any easy way to say, "Heh router, please send this particular request out over WAN 2, not WAN 1." That can be important, because I've noticed some latency sensitive applications (rdesktop, VNC) perform noticeably better over DSL than cable modem.
The router does let you statically map particular LAN IP addresses to different WAN interfaces. That's a pretty blunt instrument, but I know it's possible to assign multiple IP addresses to a single ethernet interface in Linux. So, maybe I can do that, then somehow control which IP address gets used on the Linux box, whenever I invoke wget or the like.
A few other fancy features of this router that I've noticed:
- It works as an NTP client, but unfortunately you can only give it one NTP server to talk to, and you must enter the IP address of the server, not a host name.
- It is set up to dynamic DNS with either dyndns.org or tzo.com, but I haven't tried that.
- A stateful packet inspection firewall feature, which I also haven't tried.
Unfortunately, AFAICT you can't telnet or ssh to this router, the only way to configure it is via its web UI. No SSL on the web UI, just plain http. Also, you can't even see the router status page unless you first type in the admin password, which is foolish and annoying.