Like every other website on the planet, SmallNetBuilder uses cookies. Our cookies track login status, but we only allow admins to log in anyway, so those don't apply to you. Any other cookies you pick up during your visit come from advertisers, which we don't control.
If you continue to use the site, you agree to tolerate our use of cookies. Thank you!

Router Charts

Click for Router Charts

Router Ranker

Click for Router Ranker

NAS Charts

Click for NAS Charts

NAS Ranker

Click for NAS Ranker

More Tools

Click for More Tools

LAN & WAN Reviews

VPN

There's a lot of VPN power in the 8200, given that it supports IPsec and PPTP both in pass through and endpoint modes. The problem, I found, is getting to that power, and neither the Connection Wizards nor the User Manual seemed to be much help.

The Connection Wizard was pretty clear in its options of Point-to-Point Tunneling Protocol and Point-to-Point Tunneling Protocol Server that allow the 8200 to connect all LAN clients to a remote PPTP gateway and allow individual users to connect via PPTP connections respectively. The wizards ask only for the basics, though, and you may need to get to the Advanced settings screen (Figure 8) to change settings, or at least to figure out how to set up your PPTP client.

USR8200 - PPTP Advanced Settings
Figure 8: PPTP Advanced Settings
(click on the image for a full-sized view)

Once you set up the PPTP server, you'll need to make a visit to the Users page (more later) to set up an account for each user who'll be visiting the PPTP server.

IPsec wasn't as easy, however. Its Connection Wizard provided only Network-to-Network and Gateway-to-Gateway options, neither of which seem to describe what I wanted to do - connect via an IPsec tunnel with a WinXP client running an IPsec client. So I just picked an option, completed the Wizard entries, then went into the Settings (Figure 9) to tweak things.

USR8200 - IPsec settings
Figure 9: IPsec Settings
(click on the image for a full-sized view)

Although the settlings look like they'd provide what I wanted, entering a remote endpoint and remote subnet in the same Class C subnet (192.168.3.X) threw an error. I was able to successfully get a tunnel working when I switched to using a Linksys USBVPN1 [reviewed here] attached to my notebook instead of an IPsec client.

The 8200 looks like it has a pretty comprehensive selection of connection options - some more of which are shown in Figure 10 - including an option to allow the use of Authentication Header (AH) protocol during Phase 2 negotiation, which isn't normally found in this class of IPsec device. But, once again, you'd better know what you're doing with these settings, because the Wizards and supplied documentation will be of little help.

USR8200 - IPsec Key Exchange Phase 1 settings
Figure 10: IPsec Key Exchange Phase 1 settings
(click on the image for a full-sized view)

More LAN & WAN

Wi-Fi System Tools
Check out our Wi-Fi System Charts, Ranker and Finder!

Support Us!

If you like what we do and want to thank us, just buy something on Amazon. We'll get a small commission on anything you buy. Thanks!

Over In The Forums

I have a problem with IPv6 DNS: I am using Comcast via an ASUS RT-AC86U router with IPv6 enabled. On my LAN I have a Pi-hole on a Raspberry Pi 3B+ and...
Hi all,I have CL GPON fiber with the RT AC86U router connected to the ONT. I am connected using PPPoE & VLAN set to 201. I had a previous line speed o...
Hi there.I have an ASUS RT-AC66U_B1.For some reason, I have extremely slow page loads in the router's GUI since I updated the firmware to 384.12Is the...
Lots of invalid token freed, are these normal?Jul 15 22:29:15 kernel: FPM Pool 0: invalid token 0x00958000 freedJul 15 22:32:03 kernel: FPM Pool 0: in...
I just read this blog article https://www.privateinternetaccess.c...celeration-is-here-for-routers-using-openvpn/ which was very interesting.This is t...

Don't Miss These

  • 1
  • 2
  • 3