GRE Tunnel Problems

This section lists problems that you might encounter while configuring a GRE tunnel on a Guest Instance in Oracle Cloud.

Waiting for Remote Access Service

Description

The following error message is displayed when you run the run the oc-config-corente-tunnel.ps1 script.

Waiting for Remote Access Service
get-vpns2sinterface : The term 'get-vpns2sinterface' is not recognized as the  name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is  correct and try again.

Solution

This error indicates that the hotfix was applied on Windows Server 2012 R2 instance, but Remote Access, a PowerShell module, is not available.

To add Remote Access as a role using the Windows interface of the Server Manager console:

1. On the Server Manager Dashboard, under Quick Start, click Add roles and features.

   The Add Roles and Features Wizard appears.

2. On the Select role services page, under Remote Access, click Role Services.

   The Role services are listed.

3. Select the DirectAccess and VPN (RAS) check box, and then click Next.

   The Installation progress page appears. When the installation is complete, click Close.

4. On the Server Manager Dashboard, click Tools, and then click Routing and Remote Access.

   The Routing and Remote Access dialog box appears.

5. In the left pane, right-click the name of your Windows server, and then select Configure and Enable Routing and Remote Access.

   The Routing and Remote Access Server Setup Wizard is displayed.

6. On the Configuration page, select Custom configuration, and then click Next.

7. On the Custom Configuration page, select VPN access, and then click Next.

8. On the Completing the Routing and Remote Access Server Setup Wizard page, click Finish. The Routing and Remote Access dialog box appears.

9. Click Start Service, and then wait till the service is initialized.

GRE Script Fails with dig, nslookup

Description

When you run the GRE script, it fails and the following error message is displayed.

/bin/sh: dig: command not found

Solution

This error indicates that the Linux instance on which you are running the GRE script doesn’t have bind-utils installed.

Run the following command, and then rerun the GRE script.

sudo yum install bind-utils