Most Popular Articles
Remote Site Access and Connectivity via Wireline
I set up a remote transmitter site network for WKCR last year, using an inexpensive VPN router from Netgear known as the FVS-318G. At first this may sound a little difficult; but in reality, it wasn't hard at all. If you opt for this method, by all means read the manual first (at least once) and have the VPN router in front of you the first time to configure it. The reason is probably pretty obvious -- if you make a mistake you can always "boot" the router to get back to the factory defaults. (If at first you don't succeed…try, try again. You know how that goes.)
Now in the example I'm pointing out, the network has seven hosts:
■ The VPN router itself, as the gateway
■ A Nautel Exporter
■ A Nautel Importer
■ A Nautel VS2.5
■ A Nautel VS-HD
■ An Audemat Mini-control Silver (remote control)
■ An IP codec, which is the HD2 source.
The FVS318G is set up with a VPN policy that lets you connect remotely assuming you have the VPN client with the correct configuration. Without the VPN client, you won't be able to see the network. There are two ways to connect to this router: Via the public interface; or, if you are at the remote site, by plugging in to the remaining port and setting the local computer for dhcp. (No VPN client needed in this case.)
There are several configurations on the VPN router to be done. Like any device that faces the Internet, you'll need the IP address given by the ISP, along with the gateway and subnet mask. Once you set that, you'll need to configure the LAN network number and subnet mask and the gateway address. Since this is a VPN router, you have two other configs to do: the IKE Policy and the VPN policy. In configuring this router, I used a lot of defaults for the IKE policy as well as the VPN policy, which makes the configuration pretty easy. Look at Figure 1. This is the IKE policy configuration page. There were only three things to configure: the remote and local identifiers, and the pre-shared key. I used factory defaults for the rest. Take a look at Figure 2 now. I had two things to enter -- one in the "general" window, and one in the 'traffic selection" window.
Of course that's only half of the story. You have to have the VPN client from Netgear on your remote computer, and when you get that, it needs to be configured correctly. There are five separate places for configurations, though some are left blank. I'm including them anyway.
Phase 1 (authentication)
Phase 2 (IPSec configuration)
I would recommend for starters configuring your VPN client exactly as I describe to get going. This isn't mean to be a primer, but I do want to demonstrate that the configurations aren't hard.
For phase 1 (authentication) see Figure 3. You need the address of the public interface of the remote VPN router, obviously. You also need the pre-shared key. The other settings match the factory defaults described earlier. For P1 advanced, see Figure 4; you'll need the remote and local identifiers. For Phase 2 (IPsec), see Figure 5. Here you need to know the remote LAN network number and subnet mask. Other configurations remained as the factory defaults.
- continued on page 4
Acceptable Use Policy blog comments powered by Disqus
[an error occurred while processing this directive]
Today in Radio History
The history of radio broadcasting extends beyond the work of a few famous inventors.
Read each issue online in our Digital Edition Format in your Web browser.
EAS Information More on EAS
The feed provides feeds for all US states and territories.
Need a calendar for your computer desktop? Use one of ours.
Browse Back Issues[an error occurred while processing this directive]
Also in the December Issue
- Local Radio Spotlight: Koser Radio Group
- Trends in Technology: Streaming Audio Update
- Contest Rules Rewrite and EAS Issues
- Embedded Computing, With a Side of Pi
- Field Report: TASCAM US-366