FAQs

Can’t Find what you are looking for? Ask a question!

Your Email (required)

Your Question



CradlePoint Services (21)

View category →

NOTE: Threat Management is only available for the AER 2100, and it requires a feature license. Enable this feature through Enterprise Cloud Manager.

CradlePoint Secure Threat Management leverages Trend Micro‘s security experience and expertise in this one-pass Deep Packet Inspection(DPI) solution. Threat Management includes settings for both IPS (intrusion prevention system) and IDS (intrusion detection system), as well as application identification logging. Use Threat Management to identify and prevent a wide variety of network threats.

This Threat Management solution examines network traffic for both signature matches from Trend Micro’s large signature database of known threats and statistical anomalies to detect previously unknown threats. Trend Micro regularly adds new signatures to its database: update your signature database version to ensure you’re defending yourself against the newest threats. You have the option to update manually or schedule regular updates.

Follow these steps to get started with Threat Management:

  1. To purchase a license or to begin a free trial, log into Enterprise Cloud Manager (ECM) and go to the Applications tab (this is only available to the primary account administrator). Once entitled, the router must be rebooted for Threat Management to begin working.
  2. For complete configuration options, go to Network Settings → Threat Management in the configuration pages (in ECM or locally). See configuration options below.
  3. Set up emailed or logged alerts in the Alerts tab in ECM.
  4. Set up regularly scheduled signature updates in the configuration pages, or update manually in ECM via the Devices or Groups page (click on Commands in the top toolbar and select Update IPS Signatures from the dropdown options).

NOTE: Updating the signature database version causes a network disruption for a couple of seconds. You can schedule these updates to occur during days/times when you expect less traffic on your network.

Status

The Status section shows if Threat Management is enabled. It shows the current signature database version number, the timestamp for the most recent update, and the status of the most recent attempt to update signatures.

image

Click on the Update button to check for a new signature database version.

Configuration

Customize your Threat Management implementation (choose between IPS and IDS, set up a signature update schedule, etc.).

image

Operation Mode: Choose IPSIDS, or neither.

  • Disabled
  • Detect and Prevent (default) – IPS mode
  • Detect Only – IDS mode

Engine Failure/Error Action: In the unlikely event of an error with the Threat Management engine, you have the following options:

  • Allow Traffic (default)
  • Deny Traffic

With Allow Traffic selected, the device will act like a typical router without Threat Management enabled and route traffic as usual. If security is a huge concern, however, you may wish to select Deny Traffic to stop all traffic when Threat Management isn’t working properly.

Application ID Logging: (Disabled by default.) The DPI engine can identify network traffic applications and send this information to the system logs. Depending on your network traffic uses, application ID logging may send huge amounts of data to the system logs. We recommend enabling a syslog server to manage this information.

To view the logs, go to Status → System Logs. For configuration options, including syslog server setup, go to System Settings → Administration and select the System Logging tab.

Signature Update Schedule

You can choose to have a different signature update schedule for modems than for other WANs. This is intended to protect against overages when data usage limits for 3G/4G modems are restricted. For both Non-Modem WANs and Modem WANs, first choose the Frequency for updates:

  • Never
  • Daily
  • Weekly
  • Monthly

Then choose the specifc day and time. These updates cause a minor network disruption, so schedule updates for times with less critical traffic.

Whitelisted Signatures

Specify individual signatures that the Threat Management engine is detecting/preventing when the traffic is actually desired. Click Add and manually input a signature ID to include that signature on the “whitelist.”

image

Permalink

0 Comments - Leave a Comment

Getting Started


Enterprise Cloud Manager Registration


CradlePoint Enterprise Cloud Manager is CradlePoint’s next generation management and application platform. Enterprise Cloud Manager (ECM) integrates cloud management with your CradlePoint devices to improve productivity, increase reliability, reduce costs and enhance the intelligence of your network and business operations.

Click here to learn more and sign up for a free 30-day ECM trial.

Depending on your ordering process, your devices may have already been bulk-loaded into ECM. If so, simply log in at cradlepointecm.comusing your ECM credentials and begin managing your devices seamlessly from the cloud.

If your device has not yet been loaded into your ECM account, you need to register. Log into the device administration pages and go to Getting Started → Enterprise Cloud Manager Registration. Enter your ECM username and password, and click on “Register.”

image

Once you have registered your device, go to https://cradlepointecm.com and log in using your ECM credentials.

image

For more information about how to use CradlePoint Enterprise Cloud Manager, see the following:

First Time Setup


When you log in for the first time, you will be automatically directed to the FIRST TIME SETUP WIZARD, which will walk you through basic steps to customize your CradlePoint AER 2100. To return to the First Time Setup Wizard after your initial login, go to Getting Started → First Time Setup in the dropdown menu. You have the ability to configure any of the following:

  • Administrator Password
  • Time Zone
  • WiFi Network Name
  • Security Mode
  • Access Point Name (APN) for SIM-based modems
  • Modem Authentication
  • Failure Check

Administrator Password

CradlePoint recommends that you change the router’s ADMINISTRATOR PASSWORD, which is used to log into the administration pages. The administrator password is separate from the WiFi security password, although initially the Default Password is used for both.

image

NOTE: If you plan to use your router in a PCI DSS compliant environment, do not use this setting. Use the “Advanced Security Mode” settings under the Router Security tab in System Settings → Administration instead.

Time Zone

You can select your TIME ZONE from a dropdown list. (This may be necessary to properly show time in your router log, but typically your router will automatically determine your time zone through your browser.)

image

Click NEXT.

WiFi Network Name

CradlePoint recommends that you customize your WiFi network name. Type in your personalized network name here. You can also enable the Guest Network feature (for more configuration options, see Network Settings → WiFi / Local Networks).

image

WiFi Security Mode

image

Choose the WIFI SECURITY MODE that best fits your needs:

  • BEST (WPA2): Select this option if your wireless adapters support WPA2-only mode. This will connect to newest devices and is the most secure, but may not connect to older devices or some handheld devices such as the PSP.
  • GOOD (WPA1 & WPA2): Select this option if your wireless adapters support WPA or WPA2. This is the most compatible with modern devices and PCs.
  • POOR (WEP): Select this option if your wireless adapters only support WEP. This should only be used if a legacy device that only supports WEP will be connected to the router. WEP is insecure and obsolete and is only supported in the router for legacy reasons. The router cannot use 802.11n modes if WEP is enabled; WiFi performance and range will be limited.
  • NONE (OPEN): Select this option if you do not want to activate any security features.

CradlePoint recommends BEST (WPA2) WiFi security. Try this option first and switch only if you have a device that is incompatible with WPA2.

Choose a personalized WPA PASSWORD or WEP KEY. This password will be used to connect devices to the router’s WiFi broadcast once the security settings have been saved.

  • WPA Password: The WPA Password must be between 8 and 64 characters long. A combination of upper and lower case letters along with numbers and special characters is recommended to prevent hackers from gaining access to your network.
  • WEP Key: A WEP Key must be either a hexadecimal value of 5 or 13 characters or a text value of 10 or 26 characters.

Click NEXT.

Access Point Name (APN)

image

If you are using a SIM-based modem (LTE/GSM/HSPA) with your CradlePoint router, you may need to configure the APN before it will properly connect to your carrier. Wireless carriers offer several APNs, so check with your carrier to confirm the appropriate one to use. Some examples include:

  • AT&T: “broadband”
  • T-Mobile: “epc.tmobile.com”
  • Rogers LTE: “lteinternet.apn”
  • Bell: “inet.bell.ca”
  • TELUS: “isp.telus.com”

You can either leave this on the Default setting or select Manual and input a specific APN.

If your specific modem or SIM already has APNs programmed into it, you should leave this on the Default setting. After finishing this Wizard go toInternet → Connection Manager, select your modem, and edit the settings. The SIM PIN/APN tab has more available settings than are provided here.

Modem Authentication

Some modems require a username and password to be entered to authenticate with a carrier. Do not fill in these fields unless you are sure your modem needs authentication.

image

  • Authentication Protocol – Set this only if your service provider requires a specific protocol and the Auto option chooses the wrong one. Select from:
    • Auto
    • Pap
    • Chap
  • Username
  • Password

Configuring Failure Check

It is possible for a WAN interface to go down without the router recognizing the failure. (For example: the carrier for a cellular modem goes dormant, or your Ethernet connection is properly attached to a modem but the modem becomes disconnected from its Internet source.) Enable Failure Check to ensure that you can get out to the Internet via your primary WAN connection. This option is disabled by default because it may use data unnecessarily. Use this in combination with failover. For cellular modems, use this in combination with Aggressive Reset (Internet → Connection Manager under Modem Settings in the interface/rule editor).

image

Idle Check Interval: Set the number of seconds the router will wait between checks to see if the WAN is still available. (Default: 30 seconds. Range: 10-3600 seconds.)

Monitor while connected: Select from the dropdown menu. (Default: Off.)

  • Active Ping: A ping request will be sent to the Ping Target. If no data is received, the ping request will be retried 4 times at 5-second intervals. If still no data is received, the device will be disconnected, and failover will occur. When “Active Ping” is selected, the next line gives an estimate of data usage in this form: “Active Ping could use as much as 9.3 MB of data per month.” This amount depends on the Idle Check Interval.
  • Off: Once the link is established the router takes no action to verify that it is still up.

Ping IP Address: If you selected “Active Ping,” you will need to input an IP address that will respond to a ping request. This IP address must be an address that can be reached through your WAN connection (modem/Ethernet). Some ISPs/Carriers block certain addresses, so choose an address that all of your WAN connections can use. For best results, select an established public IP address. For example, you might ping Google Public DNS at 8.8.8.8 or Level 3 Communications at 4.2.2.2.

Click NEXT.

Summary

Review the details and record your wireless network name, administrative password, and WPA password (or WEP key). Move your mouse over your WiFi password to reveal it.

image

Please record these settings for future access. You may need this information to configure other wireless devices.

NOTE: If you are currently using the device’s WiFi network, reconnect to the network using the new wireless network name and security password.

Click APPLY to save the settings and update them to your router.

IP Passthrough Setup


You can quickly enable IP passthrough with the IP Passthrough Setup Wizard available under Getting Started → IP Passthrough Setup. IP passthrough takes a 3G/4G WAN data source (USB, ExpressCard, or CradlePoint business-grade modem) and passes the IP address through to Ethernet LAN.

Using this function requires many changes to your router configuration. The IP Passthrough Setup Wizard will automatically make these changes for you: simply read through the wizard and select Enable IP Passthrough on the second page. For further configuration options, see Network Settings → WiFi / Local Networks.

Review the list of changes to ensure they are compatible with your router needs:

  • All Ethernet ports will be set to LAN (i.e. you cannot use Ethernet as an Internet source for your router).
  • All WAN devices will have Load Balance disabled, and the highest priority device will be used.
  • All network groups except the primary network group will be removed.
  • All wireless interfaces will be removed from the primary network group. (It is possible to have a wireless interface associated with another network.)
  • All router-based VPN and GRE services will be disabled.
  • The Routing Mode will be set to IP Passthrough. (Network Settings → WiFi / Local Networks in the “Local Network Editor” under “IP Settings”)
  • The Subnet Selection Mode will be set to “Automatically Create Subnet” (Network Settings → WiFi / Local Networks in the “Local Network Editor” under “IP Settings” – this shows once IP Passthrough is set as the Routing Mode). You have the option to override this and select Force 24 Subnet, which forces a subnet of 255.255.255.0 and uses the first available address in the network as the gateway. This is for compatibility with equipment that may not handle modem addressing schemes; this should not be used unless necessary.

Any Ethernet WAN connections should be disconnected before IP passthrough is enabled.

Permalink

0 Comments - Leave a Comment

Table of Contents

Purpose

This article will explain in detail the process of migrating group configurations from WiPipe Central (WPC) to Enterprise Cloud Manager (ECM).

Requirements

  1. An Administrator or Full-Access WPC account
  2. Existing group configurations in WPCNote: It is recommended to migrate group configurations first without any devices. This process allows for a review of the new ECM configurations prior to assigning any devices to the group.
  3. An Administrator or Full-Access ECM accountNote: Settings for logs and alerts will not transfer in the migration. Settings for data capture and historical information, such as saved reports, will not transfer. Migrated groups will take ECM defaults for any settings not migrated.
  4. At least one WPC group for Series 3 devices (excluding the MBR95 and CTR35)

Directions

Initiate Group Migration from WPC

Note: Prior to migrating groups from WPC, please ensure groups and devices are at firmware 4.4.0 or above as described in Preparing to Migrate from WPC to ECM

First, log into WPC.

Select Group

  1. Navigate to the Groups tab.
  2. Select the group you wish to migrate, you can select multiple groups.
  3. Click on the Migrate button.

Group Migration dialog appears. This dialog has the following items:

Input ECM Credentials

  1. An Overwrite existing ECM group configuration checkboxChecking this option will overwrite the ECM group configuration with the current WPC group configuration. If no ECM group with the same name exists, this option has no effect.
  2. Migrate devices in selected groups checkboxLeaving this option unchecked will only migrate the group configuration to ECM. Checking this option will migrate all devices that currently belong to the WPC group into the matching ECM group. If no ECM group exists, the group will be created first.Note: In order to detach from WPC and connect to ECM the router must reboot. Depending on the synchronization timer on the router, this reboot may not be immediate and will occur the next time it checks in with WPC.

WPC Group Migrated

Validate Group Migration in ECM

Immediately after migrating the group configuration it will be visible in ECM; it is highly recommended to validate the ECM configuration prior to migrating any devices into it.

ECM Group Migrated

  1. Group name migrated from WPC
  2. No devices in the group (unless the Migrate devices in selected groups option was checked)Note: Settings for logs and alerts have changed from WPC and were no longer a part of the group configuration.
  3. Select the migrated group
  4. Click on the Settings link above the group list: the group settings dialog will display.

ECM Group Logging Review

  1. Reporting – Enable log and usage reporting as desired
  2. Connection PulseThe Connection Pulse is how often the “heartbeat” is sent to the ECM server. It is recommended to leave this at its default setting. Adjusting it to a higher frequency will increase data usage. Lowering the frequency risks dropping the ECM session. If the session is dropped, the router will be forced to reestablish the SSL connection, which requires significantly more data than the keep-alive.

Click “OK” to confirm Reporting, and Connection Pulse settings

Note: Alerts are configured under the Alerts tab in ECM and are not saved as part of the group configurations like they were in WPC.

Open the group Edit Configuration window to review the group configuration settings:

ECM Group Settings Review

  1. Select the group from the groups list
  2. Click the Configuration dropdown
  3. Choose Edit

Review the group settings to ensure the new ECM group is configured as desired.

ECM Group Settings Review

Note: ECM no longer has the Group tab in group configuration pages. All of the necessary functions still exist in the following locations:

ECM Group Tab Features

  1. Alert Config – in the group Settings dialog
  2. Commands – in the group Commands dropdown
  3. Device List – filter the Devices (3a) tab using the Show Accounts (3b) show accounts feature
  4. Rename Group – Click the pencil icon next to the Name field in the Groups list (only shows when the group is highlighted)
  5. Firmware – use the Firmware dropdown
  6. Sync Config – Adjusting the status reportinglog reporting, and heartbeat notification interval are in the group settings dialog (item 1). Firmware updates are now pushed to the device (item 2), instead of the device checking with the server for updates at set intervals.

Alternative: Create Groups in ECM First

Instead of migrating group configurations from WPC, you can create and configure groups in ECM first.  In order to use this method, the group must:

  1. Have the same group name
  2. Be assigned the same device model
  3. Be assigned the same firmware version
  4. Belong to the same account not a sub-account

Note: When creating ECM groups first, it is recommended to migrate devices from the WPC device list. If the ECM group configurations do not match the WPC group configurations, WPC will require a group configuration overwrite in order to migrate devices. Migrating from the device list does not require the group configurations to match.

Migrating Devices

After the group configuration is migrated, and the new settings are reviewed, the next step is to migrate devices.

Next Step: WPC to ECM Migration: Devices

Permalink

0 Comments - Leave a Comment

It is possible to manage a CradlePoint router through Enterprise Cloud Manager (ECM) with no active WAN connection, such as when it is used a failover device or configured in WiFi Bridge mode on an existing network. With the default settings, the router requires an active WAN connection to connect to ECM or obtain the current date/time from an NTP Server. To instead use the LAN to connect to ECM, you must set the CradlePoint to use the LAN Gateway feature.

  1. Log into the device’s administration pages.
  2. Go to System Settings > Administration.
  3. Select the Router Services tab.
  4. Select Use LAN Gateway and input the LAN Gateway Address. (This is the LAN IP address of the router that the CradlePoint is connected to.)                                                                                                                  Enabling a LAN gateway for Router Services
  5. The DNS server fields might not need to be changed: these match the static DNS values (set at Network Settings > DNS). You can leave the default values or set them manually here.

Once Router Services has been configured to use a LAN gateway, the device can now be managed by ECM via the LAN. However, because the device still does not have an active WAN connection, ECM will report the IP Address for the WAN source of the network the CradlePoint is connected through.



Notes

  • Setting up a LAN gateway for router services can be used to save money when a CradlePoint router is configured for 3G/4G failover behind another router. If your 3G/4G data plan is small/expensive, you can set router services to use the LAN connection (following the above steps) so that ECM doesn’t use 3G/4G data unnecessarily.
  • In addition to ECM, other “router services” also require a WAN connection by default but can be configured to use the LAN instead. For example, the above steps will enable a connection to an NTP (Network Time Protocol) server via the LAN.

Permalink

0 Comments - Leave a Comment

Welcome to CradlePoint Enterprise Cloud Manager

Enterprise Cloud Manager is the next generation management and application platform from CradlePoint. Enterprise Cloud Manager (ECM) integrates cloud management with your CradlePoint devices to improve productivity, increase reliability, reduce costs, and enhance the intelligence of your network and business operations.

Getting Started

Connecting Devices to Enterprise Cloud Manager:
Using Enterprise Cloud Manager:

Connecting Devices to Enterprise Cloud Manager

Upgrading Firmware

NOTE: Currently only Series 3 devices can connect to ECM (see: How to identify the Series of your CradlePoint router).
Connecting devices to CradlePoint Enterprise Cloud Manager requires at least firmware version 4.3.2 – you may need to upgrade firmware. You can upgrade firmware through the individual device’s administration pages or through WiPipe Central.

Upgrading Firmware through the Device Administration Pages

  1. Log into the device administration pages. Open a browser window and type “cp/” or “192.168.0.1” (these are the defaults – you may have changed them) in the address bar. Press ENTER/RETURN.
  2. When prompted for your password, type the eight character DEFAULT PASSWORD found on the product label – this is also the last eight characters of the MAC address. You may have personalized this password.
  3. Once you are logged in, navigate to System Settings → System Software. Under Firmware Upgrade, select the Automatic (Internet)option to upgrade to the newest firmware version. It is recommended that you save your settings using System Config Save/Restore.

Upgrading Firmware through WiPipe Central

  1. Log into WiPipe Central.
  2. Select the group that you want updated firmware for.
  3. Click on Group and select Firmware from the dropdown menu.
User-added image
  1. Select at least firmware version 4.3.2.

Registering Devices

Log into the device administration pages and go to Getting Started → Enterprise Cloud Manager Registration. Enter your ECM username and password, and click on “Register”.
User-added image
Your device is now registered in ECM.

Migrating Devices from WiPipe Central

The following articles detail the steps for safely migrating devices from WiPipe Central to Enterprise Cloud Manager:


Using Enterprise Cloud Manager

Navigating the User Interface

Once you have upgraded firmware to at least 4.3.2 and registered your devices, go to https://cradlepointecm.com and log in using your ECM credentials.
ECM login
Once you are logged in, the left navigation menu shows the following tabs:
  • Dashboard – Provides powerful insight into your network through WAN analytics including connectivity, data usage, and performance.
  • Devices – Monitor all the devices loaded into ECM. View statuses, change configurations, and update firmware by device.
  • Groups – Monitor devices by group. Add new groups and view statuses, change configurations, and update firmware by group.
  • Accounts & Users – Add new users and subaccounts and edit the existing ones.
  • Alerts – View a list of alerts generated by your devices and edit settings for alerts, including emailed alerts.
  • Reports – Select the date range, type of report, group(s), and identifier fields and export CSV reports.
  • Applications – Trial, buy, and manage cloud-based applications (e.g., CP Secure Threat Management). This tab is only available for top-level account administrators.

For contextual help, open the Help Panel by clicking on the question mark symbol in the top right corner.

ECM Help Panel
You have the ability to collapse or resize the Help Panel. Also, use your operating system/browser “Find” function to search the help text (e.g. click Ctrl+F or ⌘+F).The DevicesGroups, and Alerts → Log pages all display as grids. The grids are customizable. Reorder columns by dragging and dropping the column headers. Resize columns by dragging the edge of the column headers. Click on the column headers to sort rows by ascending/descending order.
To remove or add columns, click on the “Column Selection” icon in the top right corner of the grid. Select/deselect columns from the popup list that appears.
ECM column selection
To filter the display to show a subset of the grid items, you have two main options:
  1. Some of the fields in the grid are hyperlinks for filtering the grid (e.g. “Product”). From within the grid, click on a hyperlinked field and the grid will be filtered to display only the devices of that type. For example, click on “MBR1400v2” to display only MBR1400v2 devices.
  2. Input a string of characters into the search box (top right) to filter by devices that have that string in one of their fields. You can use partial strings, and the field does not have to start with the partial string. For example, “600” will display devices that have “IBR600” in the Product field. This searches most (but not all) of the fields.
ECM search box

Creating a New User

NOTE: Creating a new user is only available to account administrators.

  1. Click on Accounts & Users in the left menu.
  2. Select the desired account from the table.
  3. Click on Add in the top toolbar. Select “User” from the dropdown menu.
Add User
  1. Enter the information in the “Add User” dialog box. Note that the “Role” will determine the permissions the user will have in the account and all included subaccounts. Choose from the following roles:
    • Administrator: Administrators have full access to the account they are in, along with all subaccounts within that account.
    • Full Access User: Same access as administrators except cannot create/edit other users.
    • Read Only User: Cannot make any configuration changes or change settings; can only view information within Enterprise Cloud Manager (ECM) and run reports.
Add User Dialog Box
  1. Click on “OK” to save the new user.

Creating a Subaccount

NOTE: Creating a new subaccount is only available to account administrators.

  1. Click on Accounts & Users in the left menu.
  2. Select the desired account from the table.
  3. Click on Add in the top toolbar. Select “Subaccount” from the dropdown menu.
Add Subaccount
  1. Enter the name of the subaccount and click “OK”.
Add Subaccount Dialog Box

Managing Devices

Once you have added a device to ECM, you will see it listed in the Devices page. Manage individual devices within this page: view a device’s status, make configuration changes, move devices into a group, etc. The Devices page has three main views: RoutersNetwork Interfaces, and Rogue AP. In the views menu at the top, next to Devices, select one of these options (default view is Routers).
  • Routers displays all the routers.
  • Network Interfaces displays every network interface, including both LAN and WAN (e.g. modems, Ethernet connections, WiFi).
  • Rogue AP shows a list of wireless access points that your devices have seen; use this list to search for Rogue APs that could threaten your networks.

From within the Routers view, click on a device name to view in-depth WAN analytics for that device. This reveals the device dashboard, with charts for data usage, signal strength, and more.

Device dashboard
The most common way of managing devices is in groups. By putting devices in groups you can change the configuration and upgrade firmware by making a change to the group that is applied to all of the devices in that group.To create a group, select Groups in the left menu and click “Add” in the top toolbar.
Add Groups
Enter the Group Name you want to use, select the Product type you will be adding to that group (e.g., MBR1400v2, IBR600), and select theFirmware you want the devices in that group to have. You can also change the Subaccount (if desired). Click on “OK.NOTE: All the devices in a group must have the same type and same firmware.
Add Group Dialog Box
The new group is now listed on the Groups page.Now that the group is created, you can move devices into the group by first selecting them in the Devices page and then clicking “Move” on the top toolbar.
Move Device to Group
A popup window appears. Select a group (only groups with the appropriate device type are displayed) and click OK.
Select a Group
NOTE: The router will IMMEDIATELY be upgraded or downgraded to the version of firmware defined for the group. This could cause a router reboot if the firmware version of the router does not match the firmware version configured for the group.

Upgrading Firmware

Router firmware can be upgraded by group. Select a group from within the Groups page and click on Firmware in the top toolbar. In the dropdown menu, select the firmware version number.
Upgrading Firmware
You will be prompted to accept the firmware version change.
Confirm Firmware Upgrade
Click on “Yes” and the firmware upgrade will be applied IMMEDIATELY to all of the routers in the group.NOTE: The routers in the group will IMMEDIATELY be upgraded (or downgraded) to the version of firmware defined for the group. This will cause a router reboot if the firmware version of the router does not match the firmware version configured for the group.

Configuring Devices

You can apply a configuration change to a group or a specific device within a group (e.g. change failover priority, enable GPS, add a guest WiFi network, etc.). Configuration settings created for a group apply to all the devices within the group. Configuration settings created for a device apply only to that device and override configuration settings defined for the group it is in.1To change the configuration of a group select Group in the Application panel, select the group you want to configure, click “Configuration” in the top toolbar, and select “Edit” in the dropdown menu.
Configuring Devices
The Edit Configuration window shows, allowing you to make configuration changes.
Configuration Window
When making changes in the Edit Configuration window you must select “Apply” on each configuration page before leaving the page in order to save the changes made. Once you have completed all changes, select from the following buttons on the bottom of the window:
  • View Pending Changes – view all of the changes you made on all of the configuration pages
  • Commit  Changes – apply all of the changes made on all of the configuration pages to the group or device(s)
  • Discard Changes – close the configuration window without applying any of the changes made on the configuration pages

To configure an individual device, select Device in the left menu and select the device in the list. Click on “Configuration in the top toolbar” and then select “Edit” from the dropdown menu. The same rules and guidelines apply to device configuration that apply to the group configuration described above.

Setting Up Alerts

The Alerts page has two views for tracking device status changes:
  • The Log view shows a list of alerts sent from the routers to ECM.
  • The Settings view shows rules for alerts, including email notifications.

Toggle between these two views by clicking on the buttons at the top left.

Alerts

Alerts are of the following types:

  • Configuration Change
  • Configuration Rejected
  • Data Cap Threshold
  • ECM Connection State
  • Failed Login Attempt
  • Firmware Upgrade
  • Modem State
  • Reboot
  • Unrecognized Client
  • WAN Service Type
  • WAN Status Change
To enable alerts, including emailed notifications, first select the Settings view and then click on Add at the top left. Create an alert notification rule by completing the fields.
Alert notification rule
Complete the following fields to create an alert notification rule:
  • Accounts/Groups (required) – Choose which sets of devices will follow the notification rule. If you select an account, both grouped and ungrouped devices within that account (including all subaccounts) will be assigned to this rule.
  • Alerts (required) – Select the alert types from the dropdown options.
  • Users (optional) – If you want emailed notifications for these alerts, select users from the list to receive those emails. If you just want these alerts logged, leave this field blank.
  • Interval (optional – Select a time interval from the dropdown options. If you select “Immediately,”  an email notification is sent every time one of the selected types of alerts are logged. Otherwise, the alerts are stored over the course of the time interval and then sent together.

Exporting Reports

Reports allow you to create a summary of information about groups of devices and export that information as a CSV file. Select from several fields to customize your reports. Select the type of report (Data Usage or Signal Quality), a range of dates, the group(s), and identifying fields and then click Run Report to view the report. You also have the option to save the settings of a report for future use.

Reports

Exporting Logs

To export a device’s logs as a CSV file, first enable log reporting for the group the device is in. (This is disabled by default because some users won’t use this functionality – it would unnecessarily use data.) Navigate to the Groups page, select the desired group, and click on Settings.
Enable log reporting
In the popup window that appears, ensure that “Enable Log Reporting” is selected.
Enable Log Reporting
Once log reporting is enabled, navigate to the Devices page, select the desired device, and click on Export → Export Logs to export the device’s logs as a CSV file.
Export logs

 


1  Both group and device settings apply to the device unless they are mutually exclusive, in which case the device settings win. If a configuration update causes an error, the configuration will roll back to the previous configuration, and the device is “suspended:” it will still operate, but new configuration settings are not accepted until the suspension is removed.

Permalink

0 Comments - Leave a Comment

General M2M Question (24)

View category →

Yes, the GX440 fully supports fallback to 3G and 2G networks. The default setting for the GX440, when it comes to network service preference, is “”LTE Preferred””, meaning the GX440 will always look to connect to a LTE service first, if available. If LTE service is not available, then the GX440 will connect to the next fastest service available.

Customers who purchase the GX440, but who do not yet have LTE service in their area, there is a configuration option under the “”WAN/Cellular”” tab in ACEmanager 4.0 to set the GX440 to “”CDMA Only””. When this configuration is used the GX440 will not actively scan for LTE service.

 

Learn More about the Sierra Wireless Gx440

 

Permalink


Verizon: Band 13 – UL 777-787Mhz, DL 746-756Mhz

AT&T (future product): Band 17 – UL 704-716Mhz, DL 734-746Mhz (also Band 1 and Band 4 used outside the US

GX440 supports Verizon OR AT&T LTE frequencies, different embedded modules are required for Verizon and AT&T, therefore, there will be two distinct GX440 SKUs

GX440 does NOT support public safety Band 14 (D block) – UL 788-798Mhz, DL 758-768Mhz

 

Learn More about the Sierra Wireless Gx440

 

Permalink


The SIM slot is located on the front left (as you are looking at the side with the lights and the reset button) behind the plastic cover. To access the SIM slot on the device you must remove the plastic cover with a 2mm or 5/64″ hexagon Allen wrench. Install the SIM card with the gold contacts facing down and the cut-out facing to the right. The GX400/440 also includes a SIM lock-down feature to prevent the SIM from moving during extreme vibration. The cover has a tab to mechanically secure the SIM in place during extreme vibration. When replacing the cover, first place the front into the lip and push back to make sure the four holes are aligned before screwing the bolts back in place.

 

Learn More about the Sierra Wireless Gx440

 

Permalink


The LTE networks that supports the GX440 are the Verizon Wireless Network and the AT&T LTE Network in the US.

 

Learn More about the Sierra Wireless Gx440

 

Permalink


The GX400 for EVDO networks does NOT require a SIM card and activation can be done with the appropriate network operator representative and the ESN of the device located on the bottom.

The GX400 for HSPA+ DOES require a SIM card, which can be procured from the appropriate network operator representative.

  • Sim cards used for other AirLink HSPA devices CAN be used in the GX400.

The GX440 DOES require a SIM card. This is notable, since this is the first time that an AirLink device on the VZW network requires a SIM card. SIMs can be procured from your VZW representative during the course of account activation.

Permalink

0 Comments - Leave a Comment

Cradlepoint Products (2)

View category →

IPv6 Settings

This is the product manual section for IPv6 Settings for the WAN. To edit these settings, go to Internet → Connection Manager. Select a WAN Interface and click on Edit to open up the WAN Configuration editor. IPv6 Settings is one of the tabs:

IPv6 configuration window


The IPv6 configuration allows you to enable and configure IPv6 for a WAN device. These settings should be configured in combination with the IPv6 LAN settings (go to Network Settings → WiFi / Local Networks, select the LAN under Local IP Networks, and click Edit) to achieve the desired result.

This is a dual-stacked implementation of IPv6, so IPv6 and IPv4 are used alongside each other. If you enable IPv6, the router will not allow connections via IPv4. When IPv6 is enabled, some router features are no longer supported. These are:

  • RADIUS/TACACS+ accounting for wireless clients and admin/CLI login
  • IP Passthrough (not needed with IPv6)
  • NAT (not needed with IPv6)
  • Bounce pages
  • UPnP
  • Network Mobility
  • DHCP Relay
  • VRRP, GRE, GRE over IPSec, OSPF, NHRP
  • Syslog
  • SNMP over the WAN (LAN works)

There are two main types of IPv6 WAN connectivity: native (Auto and Static) and tunneling over IPv4 (6to4, 6in4, and 6rd).

  • Native – (Auto and Static) The upstream ISP routes IPv6 packets directly.
  • IPv6 tunneling – (6to4, 6in4, and 6rd) Each IPv6 packet is encapsulated by the router in an IPv4 packet and routed over an IPv4 route to a tunnel endpoint that decapsulates it and routes the IPv6 packet natively. The reply is encapsulated by the tunnel endpoint in an IPv4 packet and routed back over an IPv4 route. Some tunnel modes do not require upstream ISPs to route or even be aware of IPv6 traffic at all. Some modes are utilized by upstream ISPs to simplify the configuration and rollout of IPv6.

Enable IPv6 and select the desired IPv6 connection method for this WAN interface.

  • Disabled (default) – IPv6 disabled on this interface.
  • Auto – IPv6 will use automatic connection settings (if available).
  • Static – Input a specific IPv6 address for your WAN connection. This is provided by the ISP if it is supported.
  • 6to4 Tunnel – Encapsulates the IPv6 data and transfers it to an automatic tunnel provider (if your ISP supports it).
  • 6in4 Tunnel – Encapsulates the IPv6 data and sends it to the configured tunnel provider.
  • 6rd Tunnel (IPv6 rapid deployment) – Encapsulates the IPv6 data and sends it to a relay server provided by your ISP.

When you configure IPv6, you have the option to designate DNS Servers and Delegated Networks. Because of the dual-stack setup, these settings are optional: when configured for IPv6, the router will fall back to IPv4 settings when necessary.

DNS Servers

Each WAN device is required to connect IPv4 before connecting IPv6. Because of this, DNS servers are optional, as most IPv4 DNS servers will respond with AAAA records (128-bit IPv6 DNS records, most commonly used to map hostnames to the IPv6 address of the host) if requested. If no IPv6 DNS servers are configured, the system will fall back to the DNS servers provided by the IPv4 configuration.

Delegated Networks

A delegated network is an IPv6 network that is inherently provided by or closely tied to a WAN IP configuration. The IPv6 model is for each device to have end-to-end IP connectivity without relying on any translation mechanism. In order to achieve this, each client device on the LAN network needs to have a publicly routable IPv6 address.

Auto

IPv6 auto-configuration mode uses DHCPv6 and/or SLAAC to configure the IPv6 networks. When you select Auto, all of the following settings are optional (depending on your provider’s requirements):

  • PD Request Size – Prefix Delegation request size. This is the size of IPv6 network that will be requested from the ISP to delegate to LAN networks. (Default: 63)
  • Primary IPv6 DNS Server – (optional) Depending on your provider, this may be required. This only takes effect if the default global DNS setting on the Network Settings → DNS page is “Automatic”.
  • Additional IPv6 DNS Server – Secondary DNS server.
  • Delegated IPv6 Network – (optional) Network available for delegation to LANs. Depending on your provider, this may be required. Prefixes specified here only take effect if those supplied by the connection are insufficient to configure your LANs.
  • Delegated IPv6 Network – Additional network available for delegation to LANs.

Example Configuration:

Static

As with IPv4, static configuration is available for situations where the WAN IPv6 topology is fixed.

  • IPv6 Address/CIDR – Input the IPv6 static IP address and mask length provided by your ISP (see the Wikipedia explanation of CIDR).
  • IPv6 Gateway IP – Input the IPv6 remote gateway IP address provided by your ISP.
  • Primary IPv6 DNS Server – (optional) Depending on your provider/setup, this may be required. This only takes effect if the default global DNS setting on the Network Settings → DNS page is “Automatic”.
  • Additional IPv6 DNS Server – Secondary DNS server.
  • Delegated IPv6 Network – (optional) Network available for delegation to LANs. Depending on your provider, this may be required. Prefixes specified here only take effect if those supplied by the connection are insufficient to configure your LANs.
  • Delegated IPv6 Network – Additional network available for delegation to LANs.

Example Configuration:

6to4 Tunnel

Out of the box, 6to4 is the simplest mode to enable full end-to-end IPv6 connectivity in an organization if the upstream ISP properly routes packets to and from the 6to4 unicast relay servers.

  • Primary IPv6 DNS Server – (optional) Depending on your provider, this may be required. This only takes effect if the default global DNS setting on the Network Settings → DNS page is “Automatic”.
  • Additional IPv6 DNS Server – Secondary DNS server.
  • Delegated IPv6 Network – (optional) Network available for delegation to LANs. Depending on your provider, this may be required. Prefixes specified here only take effect if those supplied by the connection are insufficient to configure your LANs.
  • Delegated IPv6 Network – Additional network available for delegation to LANs.

Example Configuration:

6in4 Tunnel

The 6in4 tunnel mode utilizes explicit IPv4 tunnel endpoints and encapsulates IPv6 packets using 41 as the specified protocol type in the IP header. A 6in4 tunnel broker provides a static IPv4 server endpoint, decapsulates packets, and provides routing for both egress and ingress IPv6 packets. Most tunnel brokers provide a facility to request delegated networks for use through the tunnel.

  • Tunnel Server IP – Input the tunnel server IP address provided by your tunnel service.
  • Local IPv6 Address – Input the local IPv6 address provided by your tunnel service.
  • Primary IPv6 DNS Server – (optional) Depending on your provider, this may be required. This only takes effect if the default global DNS setting on the Network Settings → DNS page is “Automatic”.
  • Additional IPv6 DNS Server – Secondary DNS server.
  • Delegated IPv6 Network – (optional) Network available for delegation to LANs. Depending on your provider, this may be required. Prefixes specified here only take effect if those supplied by the connection are insufficient to configure your LANs.
  • Delegated IPv6 Network – Additional network available for delegation to LANs.

Example Configuration:

6rd Tunnel

IPv6 Rapid Deployment (6rd) is a method of IPv6 site configuration derived from 6to4. It is different from 6to4 in that the ISP provides explicit 6rd infrastructure that handles the IPv4 ↔ IPv6 translation within the ISP network. 6rd is considered more reliable than 6to4 as the ISP explicitly maintains infrastructure to support tunneled IPv6 traffic over their IPv4 network.

  • 6rd Prefix – The 6rd prefix and prefix length should be supplied by your ISP.
  • IPv4 Border Router Address – This address should be supplied by your ISP.
  • IPv4 Common Prefix Mask – Input the number of common prefix bits that you can mask off of the WAN’s IPv4 address.
  • Primary IPv6 DNS Server – (optional) Depending on your provider, this may be required. This only takes effect if the default global DNS setting on the Network Settings → DNS page is “Automatic”.
  • Additional IPv6 DNS Server – Secondary DNS server.
  • Delegated IPv6 Network – (optional) Network available for delegation to LANs. Depending on your provider, this may be required. Prefixes specified here only take effect if those supplied by the connection are insufficient to configure your LANs.
  • Delegated IPv6 Network – Additional network available for delegation to LANs.

Example Configuration:

Permalink


Connection Manager


The router can establish an uplink via Ethernet, WiFi as WAN, or 3G/4G modems (integrated or external USB). If the primary WAN connection fails, the router will automatically attempt to bring up a new link on another device: this feature is called failover. If Load Balance is enabled, multiple WAN devices may establish a link concurrently.

WAN Interfaces

This is a list of the available interfaces used to access the Internet. You can enable, stop, or start devices from this section. By using the priority arrows (the arrows in the boxes to the left – these show if you have more than one available interface), you can set the interface the router uses by default and the order that it allows failover.

In the example shown, Ethernet is set as the primary Internet source, while a 4G LTE modem is attached for failover. The Ethernet is “Connected” while the LTE modem is “Available” for failover. A WiFi-as-WAN interface is also attached and “Available”.

  • Load Balance: If this is enabled, the router will use multiple WAN interfaces to increase the data transfer throughput by using any connected WAN interface consecutively. Selecting Load Balance will automatically start the WAN interface and add it to the pool of WAN interfaces to use for data transfer. Turning off Load Balance for an active WAN interface may require the user to restart any current browsing session.
  • Enabled: Selected by default. Deselect to disable an interface.

Click on the small box at the top of the list to select/deselect all devices for either Load Balance or Enabled.

Click on a device in the list to reveal additional information about that device.

Selecting a device reveals the following information:

  • State (Connected, Available, etc.)
  • Port
  • UID (Unique identifier. This could be a name or number/letter combination.)
  • IP Address
  • Gateway
  • Netmask
  • Stats: bytes in, bytes out
  • Uptime

Click “Edit” to view configuration options for the selected device. For 3G/4G modems, click “Control” to view options to activate or update the device.

WAN Configuration

Select a WAN interface and click on Edit to open the WAN Configuration editor. The tabs available in this editor are specific to the particular WAN interface types.

General Settings

Device Settings
  • Enabled: Select/deselect to enable/disable.
  • Force NAT: Normally NAT is part of the Routing Mode setting which is selected on the LAN side in Network Settings → WiFi / Local Networks. Select this option to force NAT whenever this WAN device is being used.
  • Priority: This number controls failover and failback order. The lower the number, the higher the priority and the more use the device will get. This number will change when you move devices around with the priority arrows in the WAN Interfaces list.
  • Load Balance: Select to allow this device to be available for the Load Balance pool.
  • Download bandwidth: Defines the default download bandwidth for use in Load Balance and QoS (quality of service, or traffic shaping) algorithms. (Range: 128 Kb/s to 1 Gb/s.)
  • Upload bandwidth: Defines the default upload bandwidth for use in Load Balance and QoS (quality of service, or traffic shaping) algorithms. (Range: 128 Kb/s to 1 Gb/s.)
  • MTU: Maximum transmission unit. This is the size of the largest protocol data unit that the device can pass. (Range: 46 to 1500 Bytes.)
  • Hostname (This only shows for certain devices.)
IPv4 Failure Check (Advanced)

If this is enabled, the router will check that the highest priority active WAN interface can get to the Internet even if the WAN connection is not actively being used. If the interface goes down, the router will switch to the next highest priority interface available. If this is not selected, the router will still failover to the next highest priority interface but only after the user has attempted to get out to the Internet and failed.

Idle Check Interval: The amount of time between each check. (Default: 30 seconds. Range: 10-3600 seconds.)

Monitor while connected: (Default: Off) Select from the following dropdown options:

  • Passive DNS (modem only): The router will take no action until data is detected that is destined for the WAN. When this data is detected, the data will be sent and the router will check for received data for 2 seconds. If no data is received the router behaves as described below under Active DNS.
  • Active DNS (modem only): A DNS request will be sent to the DNS servers. If no data is received, the DNS request will be retried 4 times at 5-second intervals. (The first 2 requests will be directed at the Primary DNS server and the second 2 requests will be directed at the Secondary DNS server.) If still no data is received, the device will be disconnected and failover will occur.
  • Active Ping: A ping request will be sent to the Ping Target. If no data is received, the ping request will be retried 4 times at 5-second intervals. If still no data is received, the device will be disconnected and failover will occur. When “Active Ping” is selected, the next line gives an estimate of data usage in this form: “Active Ping could use as much as 9.3 MB of data per month.” This amount depends on the Idle Check Interval.
  • Off: Once the link is established the router takes no action to verify that it is still up.

Ping IP Address: If you selected “Active Ping”, you will need to input an IP address. This must be an address that can be reached through your WAN connection (modem/Ethernet). Some ISPs/Carriers block certain addresses, so choose an address that all of your WAN connections can use. For best results, select an established public IP address. For example, you might ping Google Public DNS at 8.8.8.8 or Level 3 Communications at 4.2.2.2.

IPv6 Failure Check (Advanced)

The settings for IPv6 Failure Check match those for IPv4 Failure Check except that the IP address for Active Ping is an IPv6 address.

Failback Configuration (Advanced)

This is used to configure failback, which is the ability to go back to a higher priority WAN interface if it regains connection to its network.

Select the Failback Mode from the following options:

  • Usage
  • Time
  • Disabled

Usage: Fail back based on the amount of data passed over time. This is a good setting for when you have a dual-mode EVDO/WiMAX modem and you are going in and out of WiMAX coverage. If the router has failed over to EVDO it will wait until you have low data usage before bringing down the EVDO connection to check if a WiMAX connection can be made.

  • High (Rate: 80 KB/s. Time Period: 30 seconds.)
  • Normal (Rate: 20 KB/s. Time Period: 90 seconds.)
  • Low (Rate: 10 KB/s. Time Period: 240 seconds.)
  • Custom (Rate range: 1-100 KB/s. Time Period range: 10-300 seconds.)

Time: Fail back only after a set period of time. (Default: 90 seconds. Range: 10-300 seconds.) This is a good setting if you have a primary wired WAN connection and only use a modem for failover when your wired connection goes down. This ensures that the higher priority interface has remained online for a set period of time before it becomes active (in case the connection is dropping in and out, for example).

Disabled: Deactivate failback mode.

Immediate Mode: Fail back immediately whenever a higher priority interface is plugged in or when there is a priority change. Immediate failback returns you to the use of your preferred Internet source more quickly which may have advantages such as reducing the cost of a failover data plan, but it may cause more interruptions in your network than Usage or Time modes.

IP Overrides

IP overrides allow you to override IP settings after a device’s IP settings have been configured.

Only the fields that you fill out will be overridden. Override any of the following fields:

  • IP Address
  • Subnet Mask
  • Gateway IP
  • Primary DNS Server
  • Secondary DNS Server

IPv6 Settings

The IPv6 configuration allows you to enable and configure IPv6 for a WAN device. These settings should be configured in combination with the IPv6 LAN settings (go to Network Settings → WiFi / Local Networks, select the LAN under Local IP Networks, and click Edit) to achieve the desired result.

This is a dual-stacked implementation of IPv6, so IPv6 and IPv4 are used alongside each other. If you enable IPv6, the router will not allow connections via IPv4. When IPv6 is enabled, some router features are no longer supported. These are:

  • RADIUS/TACACS+ accounting for wireless clients and admin/CLI login
  • IP Passthrough (not needed with IPv6)
  • NAT (not needed with IPv6)
  • Bounce pages
  • UPnP
  • Network Mobility
  • DHCP Relay
  • VRRP, GRE, GRE over IPSec, OSPF, NHRP
  • Syslog
  • SNMP over the WAN (LAN works)

There are two main types of IPv6 WAN connectivity: native (Auto and Static) and tunneling over IPv4 (6to4, 6in4, and 6rd).

  • Native – (Auto and Static) The upstream ISP routes IPv6 packets directly.
  • IPv6 tunneling – (6to4, 6in4, and 6rd) Each IPv6 packet is encapsulated by the router in an IPv4 packet and routed over an IPv4 route to a tunnel endpoint that decapsulates it and routes the IPv6 packet natively. The reply is encapsulated by the tunnel endpoint in an IPv4 packet and routed back over an IPv4 route. Some tunnel modes do not require upstream ISPs to route or even be aware of IPv6 traffic at all. Some modes are utilized by upstream ISPs to simplify the configuration and rollout of IPv6.

Enable IPv6 and select the desired IPv6 connection method for this WAN interface.

  • Disabled (default) – IPv6 disabled on this interface.
  • Auto – IPv6 will use automatic connection settings (if available).
  • Static – Input a specific IPv6 address for your WAN connection. This is provided by the ISP if it is supported.
  • 6to4 Tunnel – Encapsulates the IPv6 data and transfers it to an automatic tunnel provider (if your ISP supports it).
  • 6in4 Tunnel – Encapsulates the IPv6 data and sends it to the configured tunnel provider.
  • 6rd Tunnel (IPv6 rapid deployment) – Encapsulates the IPv6 data and sends it to a relay server provided by your ISP.

When you configure IPv6, you have the option to designate DNS Servers and Delegated Networks. Because of the dual-stack setup, these settings are optional: when configured for IPv6, the router will fall back to IPv4 settings when necessary.

DNS Servers

Each WAN device is required to connect IPv4 before connecting IPv6. Because of this, DNS servers are optional, as most IPv4 DNS servers will respond with AAAA records (128-bit IPv6 DNS records, most commonly used to map hostnames to the IPv6 address of the host) if requested. If no IPv6 DNS servers are configured, the system will fall back to the DNS servers provided by the IPv4 configuration.

Delegated Networks

A delegated network is an IPv6 network that is inherently provided by or closely tied to a WAN IP configuration. The IPv6 model is for each device to have end-to-end IP connectivity without relying on any translation mechanism. In order to achieve this, each client device on the LAN network needs to have a publicly routable IPv6 address.

Auto

IPv6 auto-configuration mode uses DHCPv6 and/or SLAAC to configure the IPv6 networks. When you select Auto, all of the following settings are optional (depending on your provider’s requirements):

  • PD Request Size – Prefix Delegation request size. This is the size of IPv6 network that will be requested from the ISP to delegate to LAN networks. (Default: 63)
  • Primary IPv6 DNS Server – (optional) Depending on your provider, this may be required. This only takes effect if the default global DNS setting on the Network Settings → DNS page is “Automatic”.
  • Additional IPv6 DNS Server – Secondary DNS server.
  • Delegated IPv6 Network – (optional) Network available for delegation to LANs. Depending on your provider, this may be required. Prefixes specified here only take effect if those supplied by the connection are insufficient to configure your LANs.
  • Delegated IPv6 Network – Additional network available for delegation to LANs.

Example Configuration:

Static

As with IPv4, static configuration is available for situations where the WAN IPv6 topology is fixed.

  • IPv6 Address/CIDR – Input the IPv6 static IP address and mask length provided by your ISP (see the Wikipedia explanation of CIDR).
  • IPv6 Gateway IP – Input the IPv6 remote gateway IP address provided by your ISP.
  • Primary IPv6 DNS Server – (optional) Depending on your provider/setup, this may be required. This only takes effect if the default global DNS setting on the Network Settings → DNS page is “Automatic”.
  • Additional IPv6 DNS Server – Secondary DNS server.
  • Delegated IPv6 Network – (optional) Network available for delegation to LANs. Depending on your provider, this may be required. Prefixes specified here only take effect if those supplied by the connection are insufficient to configure your LANs.
  • Delegated IPv6 Network – Additional network available for delegation to LANs.

Example Configuration:

6to4 Tunnel

Out of the box, 6to4 is the simplest mode to enable full end-to-end IPv6 connectivity in an organization if the upstream ISP properly routes packets to and from the 6to4 unicast relay servers.

  • Primary IPv6 DNS Server – (optional) Depending on your provider, this may be required. This only takes effect if the default global DNS setting on the Network Settings → DNS page is “Automatic”.
  • Additional IPv6 DNS Server – Secondary DNS server.
  • Delegated IPv6 Network – (optional) Network available for delegation to LANs. Depending on your provider, this may be required. Prefixes specified here only take effect if those supplied by the connection are insufficient to configure your LANs.
  • Delegated IPv6 Network – Additional network available for delegation to LANs.

Example Configuration:

6in4 Tunnel

The 6in4 tunnel mode utilizes explicit IPv4 tunnel endpoints and encapsulates IPv6 packets using 41 as the specified protocol type in the IP header. A 6in4 tunnel broker provides a static IPv4 server endpoint, decapsulates packets, and provides routing for both egress and ingress IPv6 packets. Most tunnel brokers provide a facility to request delegated networks for use through the tunnel.

  • Tunnel Server IP – Input the tunnel server IP address provided by your tunnel service.
  • Local IPv6 Address – Input the local IPv6 address provided by your tunnel service.
  • Primary IPv6 DNS Server – (optional) Depending on your provider, this may be required. This only takes effect if the default global DNS setting on the Network Settings → DNS page is “Automatic”.
  • Additional IPv6 DNS Server – Secondary DNS server.
  • Delegated IPv6 Network – (optional) Network available for delegation to LANs. Depending on your provider, this may be required. Prefixes specified here only take effect if those supplied by the connection are insufficient to configure your LANs.
  • Delegated IPv6 Network – Additional network available for delegation to LANs.

Example Configuration:

6rd Tunnel

IPv6 Rapid Deployment (6rd) is a method of IPv6 site configuration derived from 6to4. It is different from 6to4 in that the ISP provides explicit 6rd infrastructure that handles the IPv4 ↔ IPv6 translation within the ISP network. 6rd is considered more reliable than 6to4 as the ISP explicitly maintains infrastructure to support tunneled IPv6 traffic over their IPv4 network.

  • 6rd Prefix – The 6rd prefix and prefix length should be supplied by your ISP.
  • IPv4 Border Router Address – This address should be supplied by your ISP.
  • IPv4 Common Prefix Mask – Input the number of common prefix bits that you can mask off of the WAN’s IPv4 address.
  • Primary IPv6 DNS Server – (optional) Depending on your provider, this may be required. This only takes effect if the default global DNS setting on the Network Settings → DNS page is “Automatic”.
  • Additional IPv6 DNS Server – Secondary DNS server.
  • Delegated IPv6 Network – (optional) Network available for delegation to LANs. Depending on your provider, this may be required. Prefixes specified here only take effect if those supplied by the connection are insufficient to configure your LANs.
  • Delegated IPv6 Network – Additional network available for delegation to LANs.

Example Configuration:

Ethernet Settings

While default settings for each WAN Ethernet port will be sufficient in most circumstances, you have the ability to control the following:

  • Connect Method: DHCP (Automatic), Static (Manual), or PPPoE (Point-to-Point Protocol over Ethernet).
  • MAC Address: You have the ability to change the MAC address, but typically this is unnecessary. You can match this address with your device’s address by clicking: “Clone Your PC’s MAC Address”.

Connect Method

Select the connection type that you need for this WAN connection. You may need to check with your ISP or system administrator for this information.

  • DHCP (Dynamic Host Configuration Protocol) is the most common configuration. Your router’s Ethernet ports are automatically configured for DHCP connection. DHCP automatically assigns dynamic IP addresses to devices in your networks. This is preferable in most circumstances.
  • Static allows you to input a specific IP address for your WAN connection; this should be provided by the ISP if supported.
  • PPPoE should be configured with the username, password, and other settings provided by your ISP.

If you want to use a Static (Manual) or PPPoE connection, you will need to fill out additional information.

Static (Manual):

  • IPv4 Address
  • Subnet Mask
  • Gateway IP
  • Primary DNS Server
  • Secondary DNS Server

PPPoE:

  • Username
  • Password
  • Password Confirm
  • Service
  • Auth Type: None, PAP, or CHAP

Modem Settings

Not all modems will have all of the options shown below; the available options are specific to the modem type.

On Demand: When this mode is selected a connection to the Internet is made as needed. When this mode is not selected a connection to the Internet is always maintained.

IP WAN Subnet Filter: This feature will filter out any packets going to the modem that do not match the network (address and netmask).

Aggressive Reset: When Aggressive Reset is enabled the system will attempt to maintain a good modem connection. If the Internet has been unreachable for a period of time, a reset of the modem will occur in attempt to re-establish the connection.

Automatically check for new firmware: (Default: selected) The modem will automatically check for firmware updates by default.

Enable Aux Antenna: (Default: selected) Enable or disable the modem’s auxiliary diversity antenna. This should normally be left enabled.

GPS Signal Source: Select the antenna to be used for receiving GPS coordinates. Some products support a dedicated GPS antenna, while others use the auxiliary diversity antenna only (and some products support both).

Enable eHRPD: (Default: selected) Enable or disable the modem’s ability to connect via eHRPD (enhanced High Rate Packet Data) when connecting to a 3G EVDO network on Sprint. eHRPD routes EVDO traffic through the LTE systems, enabling easy transitions between LTE and EVDO. In rare cases it may make sense to bypass the LTE core, so this field allows you to disable eHRPD.

Modem Connection Mode: Specify how the modem should connect to the network. Not all options are available for all modems; this will default to Auto if an incompatible mode is selected.

  • Auto (all modes): Let the modem decide which network to use.
  • Auto 3G (3G or less): Let the modem decide which 2G or 3G network to use. Do not attempt to connect to LTE.
  • Force LTE: Connect to LTE only and do not attempt to connect to 3G or WiMAX.
  • Force WiMAX: Connect to WiMAX only and do not attempt to connect tot 3G or LTE.
  • Force 3G (EVDO, UMTS, HSPA): Connect to 3G network only.
  • Force 2G (1xRTT, EDGE, GPRS): Connect to 2G network only.

Network Selection Mode: Wireless carriers are assigned unique network identifying codes known as PLMN (Public Land Mobile Network). To manually select a particular carrier, select the Manual radio button and enter the network PLMN. Choose from the following options:

  • None/No Change
  • Auto: Selected by default
  • Home only
  • Manual: Input the PLMN code

Functional Mode: Selects the functional mode of the modem. IPPT (IP passthrough) mode causes the modem to act as a transport, passing Internet data and IP address information between the modem and the Internet directly. NAT mode causes the modem to NAT the IP address information. Consequently, IPPT mode does not allow user access to the modem web UI and NAT mode does allow user access to the modem web UI.

  • None/No Change
  • IPPT
  • NAT

Network-Initiated Alerts: This field controls whether the Sprint network can disconnect the modem to apply updates, such as for PRL, modem firmware, or configuration events. These activities do not change any router settings, but the modem connection may be unavailable for periods of time while these updates occur. The modem may also require a reset after a modem firmware update is complete.

  • Disabled: The request to update will be refused.
  • When Disconnected: The request to update will only be performed when the modem is either in a disconnected state or dormant state. If the modem is not in one of these states when the request is received, then the router will remember the request and perform the update when the modem becomes disconnected/dormant.
  • On Schedule: The request to update will only be performed at the specified scheduled time, no matter what the state of the modem is.

Network-Initiated Schedule: When you select “On Schedule” for Network-Initiated Alerts, you also select a time from this dropdown list. Modem updates will take place at this scheduled time.

AT Config Script: Enter the AT commands to be used for carrier specific modem configuration settings. Each command must be entered on a separate line. The command and associated response will be logged, so you should check the system log to make sure there were no errors.

NOTE: AT Config Script should not be used unless told to do so by your modem’s cellular provider or by a support technician.

AT Dial Script: Enter the AT commands to be used in establishing a network connection. Each command must be entered on a separate line. All command responses must include “OK”, except the final command response, which must include “CONNECT”.

Example:

AT
ATDT*99***2#

WiMAX Settings

WiMAX Realm: Select from the following dropdown options:

  • Clear – clearwire-wmx.net
  • Rover – rover-wmx.net
  • Sprint 3G/4G – sprintpcs.com
  • Xohm –xohm.com
  • BridgeMAXX – bridgeMAXX.com
  • Time Warner Cable – mobile.rr.com
  • Comcast – mob.comcast.net

TTLS Authentication Mode: TTLS inner authentication protocol. Select from the following dropdown options:

  • MSCHAPv2/MD5 (Microsoft Challenge Handshake Authentication Protocol version2/Message-Digest Algorithm 5)
  • PAP (Password Authentication Protocol)
  • CHAP (Challenge Handshake Authentication Protocol)

TTLS Username: Username for TTLS authentication.

TTLS Password: Password for TTLS authentication.

WiMAX Authentication Identity: User ID on the network. Leave this blank unless your provider tells you otherwise.

CDMA Settings

These settings are usually specific to your wireless carrier’s private networks. You should not set these unless directed to by a carrier representative. If a field below is left blank, that particular setting will not be changed in the modem. You should only fill in fields that are required by your carrier.

  • Persist Settings: If this is not checked, these settings will only be in place until the router is rebooted or the modem is unplugged.
  • Active Profile: Select a number from 0-5 from the dropdown list.

The following fields can be left blank. If left blank they will remain unchanged in the modem.

  • NAI (Username@realm): Network Access Identifier. NAI is a standard system of identifying users who attempt to connect to a network.
  • AAA Shared Secret (Password): “Authentication, Authorization, and Accounting” password.
  • Verify AAA Shared Secret
  • HA Shared Secret: “Home Agent” shared secret.
  • Primary HA
  • Secondary HA
  • AAA SPI: AAA Security Parameter Index.
  • HA SPI: HA Security Parameter Index.

SIM/APN/Auth Settings

SIM PIN: PIN number for a GSM modem with a locked SIM.

Authentication Protocol: Set this only if your service provider requires a specific protocol and the Auto option chooses the wrong one. Choose from Auto, PAP, and CHAP and then input your username and password.

Access Point Configuration: Some wireless carriers provide multiple Access Point configurations that a modem can connect to. Some APN examples are ‘isp.cingular” and “vpn.com”.

  • Default: Let the router choose an APN automatically.
  • Default Override: Enter an APN by hand.
  • Select: This opens a table with 16 slots for APNs, each of which can be set as IP, IPV4V6, or IPV6. The default APN is marked with an asterisk (*). You can change the APN names, select a different APN, etc. For Verizon modems, only the third slot is editable. Changes made here are written to the modem, so a factory reset of the router will not impact these settings.

Update/Activate a Modem

Some 3G/4G modems can be updated and activated while plugged into the router. Updates and activation methods vary by modem model and service provider. Possible methods are: PRL Update, Activation, and FUMO. All supported methods will be displayed when you select your modem and click “Control” to open the “Update/Activate” window. If no methods are displayed for your device then you will need to update and activate your device externally.

To update or activate a modem, select the modem in the WAN Interfaces table and click “Control”.

The modem does not support Update/Activate methods: A message will state that there is no support for PRL Update, Activation, or FUMO.

The modem supports Update/Activate methods: A message will display showing options for each supported method:

  • Modem Activation / Update: Activate, Reactivate, or Upgrade Configuration.
  • Preferred Roaming List (PRL) Update
  • Firmware Update Management Object (FUMO)

Click the appropriate icon to start the process.

If the modem is connected when you start an operation the router will automatically disconnect it. The router may start another modem as a failover measure. When the operation is done the modem will go back to an idle state, at which point the router may restart it depending on failover and failback settings.

NOTE: Only one operation is supported at a time. If you try to start the same operation on the same modem twice the UI will not report failure and the request will finish normally when the original request is done. However if you try to start a different operation or use a different modem, this second request will fail without interfering with the pending operation.

Process Timeout: If the process fails an error message will display.

Activation has a 3-minute timeout, PRL update has a 4-minute timeout, and FUMO has a 10-minute timeout.

Update Modem Firmware

Click on the Firmware button to open the Modem Firmware Upgrade window. This will show whether there is new modem firmware available.

If you select Automatic (Internet) the firmware will be updated automatically. Use Manual Firmware Upgrade to instead manually upload firmware from a local computer or device.

Reset the Modem

Click on the Reset button to power cycle the modem. This will have the same effect as unplugging the modem.

Configuration Rules (Advanced)

This section allows you to create general rules that apply to the Internet connections of a particular type. These can be general or very specific. For example, you could create a rule that applies to all 3G/4G modems, or a rule that only applies to an Internet source with a particular MAC address.

The Configuration Rules list shows all rules that you have created, as well as all of the default rules. These are listed in the order they will be applied. The most general rules are listed at the top, and the most specific rules are at the bottom. The router goes down the list and applies all rules that fit for attached Internet sources. Configuration settings farther down the list will override previous settings.

Select any of these rules and click “Edit” to change the settings for a rule. To create a new rule, click “Add.”

WAN Configuration Rule Editor

After clicking “Add” or “Edit,” you will see a popup with the following tabs:

  • Filter Criteria
  • General Settings
  • IP Overrides
  • IPv6 Settings
  • Ethernet Settings
  • Modem Settings
  • WiMAX Settings
  • CDMA Settings
  • SIM/APN/Auth Settings

Filter Criteria

If you are creating a new rule, begin by setting the Filter Criteria . Create a name for your rule and the condition for which the rule applies:

  • Rule Name: Create a name meaningful to you. This name is optional.

Make a selection for “When,” “Condition,” and “Value” to create a condition for your rule. The condition will be in the form of these examples:

When Condition Value
Port is USB Port 1
Type is not WiMAX
  • When:
    • Port – Select by the physical port on the router that you are plugging the modem into (e.g., “USB Port 2”).
    • Manufacturer – Select by the modem manufacturer, such as Sierra Wireless.
    • Model – Set your rule according to the specific model of modem.
    • Type – Select by type of Internet source (Ethernet, LTE, Modem, Wireless as WAN, WiMAX).
    • Serial Number – Select 3G or LTE modem by the serial number.
    • MAC Address – Select WiMAX modem by MAC Address.
    • Unique ID – Select by ID. This is generated by the router and displayed when the device is connected to the router.
  • Condition: Select “is,” “is not,” “starts with,” “contains,” or “ends with” to create your condition’s statement.
  • Value: If the correct values are available, select from the dropdown list. You may need to manually input the value.

Once you have established the condition for your configuration rule, choose from the other tabs to set the desired configuration. All of the tabs have the same configuration options shown above in the WAN Configuration section (i.e., the options for Configuration Rules are the same as they are for individual devices).

Permalink


Cradlepoint Series 3 (102)

View category →

If you are unsure of CradlePoint Series or Model number, please click here.

Overview:

All computers/devices that connect to a network get an IP Address (an IP Address is a number used to identify the specific device. Think “street address”).  Computers can acquire this IP address one of two ways:

  1. They assign one to themselves.
  2. They can choose to get one from the router itself.

Every time a computer disconnects/reconnects to the router, or turned off/on a new IP address is assigned to it by the router.  Any port forwarding/remote access rule in the router is based on the computer’s IP address.  Using port forwarding/remote access rules the computer in question is required to be assigned the same IP address assigned from the router.  DCHP Reservations provide this functionality.

Things to do before setting this up:

  1. Make sure the router firmware is up to date.(How to Verify Firmware Version)
  2. Make sure the device you want to set up the reservation for is turned on and connected to the router via Wi-Fi or Ethernet.
  3. You will need to know the CURRENT IP Address of the device you want to set up a reservation for at this time.

How to set Up DHCP Reservation:

  1. Log into the routers administration page (login instructions).
  2. If you see a button in the top left that says Basic Mode, click on it. It should now say Advanced Mode (Depending on the firmware version and the router, you may not see this button)User-added image
  3. Click the Network Settings tab then select DCHP Server.               User-added image
  4. Locate the Active Leases section then find the IP Address of the device in question select it then click Reserve.            User-added image

What if this Doesn’t Work?

  1. Try doing a hardware reset of the router. This will return all router settings to factory default, so then follow the instructions to set up the reservation again. (Hard Reset instructions)
  2. Try clearing your browser’s cache. Most browsers (IE, Firefox, and chrome) allow you to do this by pressing “CTRL” + “F5” on your keyboard. (Clear Browser Cache)

Permalink

0 Comments - Leave a Comment

If you are not sure what model CradlePoint router you have, please click here.

This article was written based upon firmware version 5.0.0.

 

Description:

Many Internet service providers provide publicly routable dynamically assigned addresses to their customers.  Because the Internet IP address provided from the ISP may change daily, it may be helpful to use a Dynamic DNS service to ensure that a user on the internet can always connect to the CradlePoint, even if they don’t know the current IP address.
For example, when connecting a Comcast cable modem to a CradlePoint MBR1400, Comcast provides you a public routable IP address (for example, 71.213.152.203).  If remote web administration is enabled on port 8080 on the CradlePoint, a remote internet user would be able to access the CradlePoint’s administrative console by surfing to http://71.213.152.203:8080.  Because this address may change without notice from Comcast, a remote user would not be able to log back in until they know the IP address.

Dynamic DNS services allow you to reserve a domain name or subdomain with a Dynamic DNS provider.  Once the account with the Dynamic DNS provider has been set up, you can enter its settings inside the CradlePoint.  Once the CradlePoint has the Dynamic DNS settings entered, then any time the address changes it will send an update request to the DNS server.

For example, you went to a Dynamic DNS provider like http://www.dyndns.org and created a username & password and reserved the subdomain “cradlepoint.dyndns.org”.  Once you’ve entered these settings into the CradlePoint (as described below), a remote user on the internet would always be able to access the remote administrative console by surfing tohttp://cradlepoint.dyndns.org:8080 rather than having to know the current IP address.

Directions:

Before entering any settings into the CradlePoint, it is necessary to create an account with a Dynamic DNS service provider.  These companies provide free and/or paid Dynamic DNS services depending on your needs:


The CradlePoint also supports other custom servers that use the same settings as the above services.

After creating your account, you will need to know your host name, user name, and password.  For our example, let’s assume that you are using these settings:

  1. Host name:           cradlepoint.dyndns.org
  2. User name:           cpusername
  3. Password:             **********

To enter these settings into your Series 3 CradlePoint, follow these directions:

  1. Log into the CradlePoint’s administrative console, the default location is http://192.168.0.1.  Click here if you are unsure of how to access the administration pages.
  2. Select “Network Settings” from the top menu, then click “DNS”.                            User-added image
  3. Under “Dynamic DNS Configuration”, place a checkmark next to “Enable Dynamic DNS”. User-added image
  4. Set the “Server Type” to the dynamic DNS service provider you are using
  5. Set the “Host name” to your host name (in this example we are using “cradlepoint.dyndns.org”), User name, password, and verify your password.                               User-added image
  6. Click “Apply” to save your changes.


After making this change, any user trying to connect to “cradlepoint.dyndns.org” will be redirected to whichever WAN IP address that the CradlePoint is currently using.  If the CradlePoint changes its WAN IP address, as soon as it gets a new address it will automatically let the Dynamic DNS provider know the new IP address.

Note:

If your CradlePoint’s WAN IP address begins with a 10 (for example 10.34.121.12), then your Internet service provider is having you connect from behind Network Address Translation (NAT) instead of providing you a routable IP address.
If you have this type of account and need to be able to access the CradlePoint’s network from the Internet, contact your mobile provider to see if they can provide you a routable IP address instead.

Permalink


If you are unsure of CradlePoint Series or Model number, please click here.

This article was written based on firmware version 5.0


SUMMARY:

This document describes how to disable internet bounce pages on a Series 3 CradlePoint router.  This is necessary when you are trying to use the router for an INTRANET only, or if you do not want to see the bounce pages when the internet is not working.

First you need to log into the router, if you are unsure how click here.

  1. Click on System Settings then on Administration.                                              internet bounce
  2. Click on the Local Management Tab.
  3. Uncheck Internet Bounce Pages.
  4. Apply your settings.                                                                                                internet bounce

Permalink


If you are unsure of CradlePoint Series or Model number, please click here.

This article was written based on firmware version 5.0.0

Overview:

All current CradlePoint routers that support IP Pass-Through are the: CBA750B, CBR400, CBR450, IBR600, IBR650, and MBR1400.

Creating a custom gateway/subnet is a preventative measure to use when you have a block of consecutive static IP address from your provider.

Instructions:

  1. Click on Network Settings.
  2. Click on WiFi/ Local Networks.                                                                  User-added image
  3. Click on the Primary LAN check box.
  4. Click Edit                                                                                                        User-added image
  5. Click on the IPv4 Settings tab.
  6. Make sure your Routing mode is in fact IP Pass-Through.
  7. Set the Subnet Selection Mode to Custom Settings.
  8. Input your settings.                                                                                       User-added image

From here, you can create your own Gateway and Subnet; However, we recommend making your Gateway the same as your Static IP, except making the last octet a .1, and for subnet, a class C be fine.  For the device behind the CradlePoint, you will want to statically set its WAN port, to match the setting that were applied in the CradlePoint.  Your IP on the port should be the Static IP that you get from your provider, the Gateway will be the custom gateway that was just created (static ip of provider but last octet .1) and the class C subnet.

Example:  Cisco router behind a CradlePoint in pass through with a Verizon provided static ip 166.244.233.232.  In the CradlePoint, you would set the Gateway to 166.244.233.1 with a 255.255.255.0 subnet.  Now in the Cisco you would need to set its Eth0 or whatever port you have connected to the CradlePoint as such, IP: 166.244.233.232 GW: 166.244.233.1 S/N: 255.255.255.0

Permalink


CradlePoint routers that currently support IP Pass-Through are the: CBA750B, CBR400, CBR450, IBR600, IBR650, and MBR1400

If you are unsure of CradlePoint Series or Model number, please click here.

This article was written based on firmware version 5.0.0

Things to know before getting started:

  • These instructions are based on firmware version 4.0.3 for Series 3 Routers that support the IP Pass-through feature.  If the router’s firmware is not up to date, update before proceeding, How to update Firmware.
  • When IP Pass-through is enabled, the first device connected to the router receives the modems public IP address.  This means that any OTHER devices connected to the router will not be able to access the internet.

Configuring IP-Pass-through

There are two ways to configure IP Passthrough.

The first is to use the IP Passthrough Setup wizard available under the Getting Started tab.  This wizard will automatically apply the settings for IP passthrough.

User-added image

The second is to configure in manually by following the below steps.

  1. Connect a computer to the router via Ethernet (you will be disabling the WiFi on the Primary LAN) then log into the routers administration page (login instructions).
  2. Click  the Network Settings tab then select Wi-Fi/Local Networks.                                         User-added image
  3. Locate Primary LAN, put a check mark next to it then click Edit.
  4. (This step only necessary on the MBR1400, IBR600, and CBR400) In the new window click on the Interfaces tab.  In the Selected box, click on the WiFi network and click the minus button.User-added image
  5. Then click the IPv4 Settings tab and change the Routing Mode to IP Pass-through.                                                                                                     User-added image
  6. Click Submit.
  7. Verify that the Internet is still available on the connected computer.
  8. Verify that the IP address is same as the modems IP.

Trouble Shooting IP Pass-Through:

  1. If the settings saved correctly and the connected computer is works properly but after connecting the router to a different device it does not work as expected, consider the following:
    • Often, IP Pass-Through requires a MAC address bound to it in order to work properly.  To do this, return to the screen presented on step 4 then re-perform step 5.  In the Pass-through, reservation field type the IP address of the device that you want to configure IP Pass-through for.
    • Then click Submit.
  2. If IP-pass-through works (device behind router receives the modems IP address), but you are unable to open ports, consider the following:
    • Many 4g networks assign private, double-NAT’d private IP addresses  Often these IP addresses start with 10.x.x.x.   If you have this type of IP address, no port forwarding or remote access will be possible due to the cellular carrier’s network configuration.  This is not a limitation imposed by the CradlePoint router.
    • In Pass-Through mode, the router is not performing any routing, so it is very likely that the cellular carrier is blocking ports.
    • If the CradlePoint router is unable to  acquire a connection through the modem it will automatically issue your device a DHCP IP address.  This can also occur if the router detects the computer connected BEFORE it connects to the modem.  Performing an IP refresh/renew on your device will typically resolve this error.

Permalink


Cradlepoint Series 2 (49)

View category →

If you are unsure of CradlePoint Series or Model number, please click here.

This article was written based on firmware version 2.0.0.

Symptom:

Restrict or allow devices to connect to a Series 2 router based on the specific device MAC address.

Cause:

Enhanced Wi-Fi security.

Resolution:

  1. Log in to the administration pages of the CradlePoint router (how to log into Series 2 routers).
  2. Click on the Advanced tab.                                                                                                                 User-added image
  3. Click on MAC ADDRESS FILTER in the gray sub-menu on the left.
  4. In the MAC FILTERING SETUP section click the drop down to see the different MAC Filtering options.  User-added image
  5. Select your desired option from the Configure MAC Filtering Below drop down menu.
    • ALLOW:  allow those computers listed to connect to the network.
    • DENY:  not allow devices listed to connect to the Cradlepoint.
  6. This example selects ALLOW.  Configuring the DENY option is the same.
  7. If you would like the MAC Filtering to apply to wired and wireless clients, place a check in the Filter Wired Clients check box.
    User-added image
  8. In the Add MAC Filtering Rule, ensure the Enable check box is checked.                               User-added image
  9. Enter the MAC address of the device you would like to Allow access, begin with the device you are using to configure the CradlePoint router.
    User-added image
  10. In the Computer Name field enter a unique name for the device for later recognition of the device.
  11. Click the Save button to save this newly created rule.
  12. The rule should now populate in the MAC Filtering Rules section.                                          User-added image
  13. Repeat steps 8 through 12 for each device that you wish to Allow access to.  Devices not listed will not connect to the routers network.

Permalink


If you are unsure of CradlePoint Series or Model number, please click here.

This article was written based on firmware version 2.0.0


Symptom: 

Limited wireless range, WiMAX modem connection issues, Wi-Fi connection drops on a Series 2 CradlePoint router.


Cause:

Possible radio interference on the Wi-Fi channel that CradlePoint router is broadcasting on.


Resolution:

  1. Log in to the administration pages of the CradlePoint router (how to log into Series 2 routers)
  2. Once you are logged in click on the BASIC tab.                                                           User-added image
  3. Click WIRELESS (WIFI) in the sub-menu on the left.                                                  User-added image
  4. In the box labeled Wireless (WIFI) Network Settings, un-check the box next to Enable Auto Channel Scan.     User-added image
  5. The Wireless Channel drop down will now allow you to select with channel you want the wireless radio to broadcast on. User-added image
  6. Scroll to the top of the page and click Save Settings.                                                 User-added image
  7. You will receive a warning from the CradlePoint router, click Ok.  This will cause your router to reboot.

You have successfully changed the Wireless Channel on the CradlePoint router.  Test your wireless network for possible improved performance.  If performance is not improved repeat these steps choosing a different Wi-Fi channel.

NOTE:  If changing the Wi-Fi channel to improve WiMAX 4G connection characteristics use channel 1 for best results.

Permalink


If you are unsure of CradlePoint Series or Model number, please click here.

This article was written based on firmware version 2.0.0.

Symptom:

A mobile device(s) and/or gaming systems such as; Kindle, PlayStation, Xbox, Wii, iPhone, tablets, etc., cannot connect to the WiFi network of a CradlePoint router or a device is requesting a password for the network that is different from the Wi-Fi password. Any either of these scenarios, you may need to disable ‘Require User Login’.

Resolution:

  1. Log into the router’s setup page (login instructions).
  2. Click the TOOLS tab then select USER LOGIN in the gray sub-menu on the left.
  3. Locate the USER LOGIN SETTINGS section then uncheck the Require User Login and Allow Remember Me check boxes.                                                                                                    
  4. Click Save Settings at the top of the page.
  5. Click Reboot Now when prompted.User-added image

Permalink

0 Comments - Leave a Comment

If you are unsure of your CradlePoint Series or Model number, please click here.

This article was written based on firmware version 2.0.0.

Cause

Often Cable, DSL, or Satellite modems use the same IP Address as the default IP address on the CradlePoint router.  This causes an IP conflict and requires that the IP address on the CradlePoint router be changed.  Changing the IP Address of the CradlePoint router eliminates the IP address conflict.  Another issue that can occur on the CTR500 is an incorrect Ethernet port mode setting on the router’s single Ethernet port.

Resolution

  1. Log in to the administration pages of the CradlePoint router, if you are unsure how to do this click here.
  2. Click the  BASIC tab, then click on NETWORK in the gray sub-menu on the left.
  3. Change the Router IP Address to 192.168.5.1      User-added image
  4. Click Save Settings at the top of the page, then click Reboot Now when prompted.
  5. Reconnect to the router using the new IP Address (http://192.168.5.1) after the reboot.
  6. Log back into the router, click the BASIC tab, then click WAN in the gray sub-menu on the left..
  7. Locate the Ethernet Port Mode section then change the mode from LAN to WAN.
  8. Locate the WIRED WAN SETTINGS section, then in the Dynamic IP (DHCP) Internet Connection Type sub-section, click Clone Your PC’s MAC Address.                                            User-added image
  9. At the top of the page, click Save Settings and then click Reboot Now when prompted.
  10. Unplug the power cord from the modem and CradlePoint router.  NOTE:  Some modem have a battery, if so remove nd replace the battery while the power cord is unplugged.  Plug the power cord back into the modem then wait approximately 30 seconds then reconnect the power cord to the CradlePoint router.
  11. Establish a connection between the computer and CradlePoint router then open a web browser, the browsers default page should load.

Permalink


Overview:

This article explains what you need to do to get your MC100W Business Grade Modem to work in your CBA750.

Directions:

  1. Prior to activation, you will want to ensure that the CBA750’s Firmware and WiMax modem driver are up to date. Please review the following article for information on updating the firmware and WiMax modem driver located here.
  2. Once the firmware and WiMax driver are up to date you are ready to proceed with activation of the modem. Please review the following article for information on registering and activating your MC100W modem.
    Using Sprint Service please consult this Link.
    Using Clearwire (Clear) Service consult this Link.

Permalink


Sierra Wireless Products (43)

View category →

Four LEDs are visible from the front and top of the AirLink GX400. Labeled (from left to right) Network, Signal, Activity, and Power, each LED can display one of three colors: green, yellow, or red.

  • LED Operation:
  • Off – No activity
  • Green – Full function
  • Yellow – Limited Function
  • Red – Not functional
  • Blinking – Where needed, blinking is used to indicate altered functionality
  • Network LED:
  • Green – On the network
  • Flashing Green – Roaming
  • Yellow – Found service, attempting to connect
  • Flashing Yellow – Link down
  • Red – No data connection available
  • Signal LED – Light shows the strength of the signal and may be nearly solid
    (strong signal) or flashing (weaker signal). A slow flash indicates a very weak
    signal
  • Green – Good signal
  • Yellow – Marginal signal
  • Red – Bad signal
  • Flashing Red – No signal
  • ActivityLED – Pulse green on packet transmit/receive on radio link.
    Otherwise, LED is off
  • Power LED:
  • Off – No power (or above 36V or below 7.5V)
  • Red – System not operational
  • Green – Normal operation
  • Green, Occasional Yellow – GPS Lock
  • Yellow – Low power mode or system booting

Caution: If you need to reset the device configuration using the Reset button, hold the button depressed until the LEDs start cycling yellow, and then release the button.

Light Patterns

The LEDs on the front of the device respond with different light patterns to indicate device states.

    Normal – Each LED is lit as applicable

  • Start up and Device Reboot – All LEDS simultaneously cycle red, yellow, and green at the start. Various light patterns continue until the Power LED turns yellow, and then a solid green, to indicate an active device
  • Radio Passthrough (H/W) – Network LED is a solid red
  • Factory Reset – All LEDs cycle yellow back and forth when the Reset pin is briefly depressed and released. Returns the device’s software to the factory default state
  • Data Retry, Failed Auth, and Retrying – The Network LED blinks red every 3 seconds

Learn More about the Sierra Wireless Gx440

 

Permalink


The only GX400 device that requires a SIM card is the Sierra Wireless GX400 for HSPA+ (AT&T/T-Mobile). The AT&T SIM card can be procured & activated by USAT the time of purchase.

Through the procurement of USAT’s DevProv+ suite the device and SIM can be activated on the AT&T network. Additionally, USAT’s DevProv+ suite allows for network authentication, special template loads and device management prior to shipment.

Permalink


The GX440 supports the following frequencies:

  • Verizon: Band 13 – UL 777-787Mhz, DL 746-756Mhz
  • AT&T: Band 17 – UL 704-716Mhz, DL 734-746Mhz (also Band 1 and Band 4 used outside the US)

Note: The Sierra Wireless GX440 does NOT support public safety Band 14 (D block) – UL 788-798Mhz, DL 758-768Mhz

 

Learn More about the Sierra Wireless Gx440

 

Permalink


IP (Ingress Protection) rating measures the rates and the degrees of protection provided against the intrusion of solid objects (including body parts like hands and fingers), dust, accidental contact, and water in mechanical casings and with electric enclosures. The first number of an IP rating represents the level of protection against “solid particle”, while the second number represents the level of protection against “liquid ingress”.
An IP rating of 64 indicates that the GX400/440:

  • 6 for solid particles – “No ingress of dust; complete protection against contact.” 6 is the highest rating for solid particle protection.
  • 4 for liquid ingress – Splashing Water; “Water splashing against the enclosure from any direction shall have no harmful effect.”

Learn More about the Sierra Wireless Gx440

 

Permalink


The Sierra Wireless GX400 on Verizon and Sprint is tailored for their EVDO networks and does NOT require a SIM card. Device activation can be performed by working with your USAT Sales Manager.

Permalink


Digi Products (3)

View category →

Firewall concerns:
Firewalls (and the IT security people that maintain them) are generally concerned with protecting a location’s Local Area Network from unauthorized use – both from traffic coming at the network from the outside world, and traffic from within the local area network going outward.  A Remote Management-capable Digi product falls into the latter category, because the Digi device creates an outbound TCP socket connection to the Device Cloud or Remote Manager server.  This  EDP (easy device protocol) socket connection is tunnel through which data gets pushed from your Gateway to to the Device Cloud, so that data can be accessed from anywhere in the world.

The following article describes:

  • The IP socket connections used when a Digi RF Gateway,TransPort Router, or edp-capable device (using Digi Cloud Connector) makes a Remote Management connection to Device Cloud or Remote Manager
  • How to determine the IP address in use for a given Device Cloud or Remote Manager DNS name

Locations where it is likely that Firewall Rules will be needed:

Those who are trying to connect to Device Cloud or Remote Manager from a location which has strict outbound firewall rules will especially need the guidance found within this article.  Some likely examples for this type of network security environment include:  Government offices/buildings and institutions, Schools, Universities, and some Businesses (especially ones that do government contract work).

 

What network port(s) does a Gateway or Connect-capable device use to connect to Device Cloud?

By default, the TCP and/or UDP port(s) your Device Cloud-capable Gateway or device uses to connect with Device Cloud will depend in part on the age/default configuration of your Gateway, the device’s configuration, as well as the particular model.

TCP Port 3197:  The outbound EDP/non-SSL (non-secure) socket connection from NDS-based products like the ConnectPort X2 / X4 / X5 / X8 Gateways, and ERT/Ethernet Gateway (especially if the product hasolder firmware), which may still be configured to create an un-encrypted Device Cloud socket connection.

Note:  If possible, the firmware of older products should be updated so that the Device Cloud configuration settings can changed to use of SSL socket connections into the Device Cloud instead (see next entry below).

TCP Port 3199:   The outbound EDP/SSL (secure) socket connection from NDS-based products like the ConnectPort X2 / X4 / X5 / X8 Gateways, and ERT/Ethernet Gateway with newer firmware which are configured to create a secure SSL socket connection into Device Cloud.  Required on ALL Linux-based Gateways, examples:  XBee Gateway ZB andConnectPort X2e for Smart Energy.  Can also be required if the Device Cloud account is configured to accept SSL connections only (new Device Cloud option as of version 2.16)

UDP Port 53:  Outbound DNS (Domain Name Service) name recognition service, i.e. translates the my.devicecloud.com name for Device Cloud connectivity.

Note:  DNS service is not a requirement.  If access to DNS service is not allowed or possible from your network, the device’s remote connectivity address would need to use the IP address of my.devicecloud.com (52.73.23.137), rather than the DNS name itself (see below under What IP address is needed for outbound Firewall rule(s)? for more details).

UDP Port 123:  The outbound socket connection to an NTP (time) server is required for ALL Linux-based Gateways such as the XBee Gateway and ConnectPort X2e, as well as  gateways and devices configured for NTP time management.

Important Note for all XBee and ConnectPort X2e Gateways (and Gateways configured for NTP Time Management)

The XBee Gateway and ConnectPort X2e are Linux-based gateways which require outbound access to UDP port 123 (NTP), in order to generate the secure (SSL) TCP socket connection into Device Cloud.  Any Gateways which are configured for NTP time management will have this requirement as well, since the Gateway connects to an NTP server in order to to keep an accurate date/time.

If your XBee (or CP-X2e) Gateway is added to your Device Cloud account but never shows up in a Connected state, check to ensure that outbound NTP access is available for the Gateway through your local network Firewall.  ConnectPort X2 and X4 gateways would still connect to Device Cloud (assuming TCP port 3199 isn’t blocked), but the Gateway might show an epoch 1970-based date/time if no other Time Sources are configured.
What IP address is needed for outbound Firewall rule(s)?

The best way to determine that is to do an nslookup of the DNS name for the Remote Management server you want your device(s) to connect to.  As of the date of this article (6/16/2015), here is how this looked from my Windows 7 commandline (Start – Run – CMD) prompt when doing nslookup of our various Remote Management and NTP ring servers:

Digi Device Cloud and Remote Manager device connectivity address:

C:\>nslookup my.devicecloud.com

Name:    my.devicecloud.com
Address:  52.73.23.137

Past Device Cloud connectivity addresses which may still be in use on devices (all device configurations should be updated to use of the my.devicecloud.com address, then re-connected to the server at the new address):

devicecloud.digi.com
login.etherios.com
my.idigi.com
app.idigi.com

devicecloud-uk.digi.com
login.etherios.co.uk
my.idigi.co.uk

Digi Primary NTP Time Server Ring addresses:

C:\>nslookup time.devicecloud.com

Name:     time.devicecloud.com
Addresses:  52.25.29.129, 52.2.40.158

Secondary/Tertiary NTP Time Server addresses for pool usage:

C:\>nslookup 0.time.devicecloud.com

Name:     0.time.devicecloud.com
Addresses:  52.2.40.158

C:\>nslookup 1.time.devicecloud.com

Name:     1.time.devicecloud.com
Addresses:  52.25.29.129

Deprecated NTP/Time server addresses which may still be in use on devices (all devices should be updated to use time.devicecloud.com within their configuration):

time.digi.com
time.etherios.com

time.etherios.co.uk
0.idigi.pool.ntp.org
1.idigi.pool.ntp.org
2.idigi.pool.ntp.org

Making the Firewall Rules:

If the IP address of the DNS name ever changes (before this article is updated to reflect it), a Windows CLI command can be used to determine the IP address of our server:

nslookup <DNS name of server>

The Name and Address fields will be the DNS name and IP address for the Remote Management or Time server listed.  Your firewall rule will need to allow access for the appropriate network port used based on your Gateway’s Device Management configuration, as well as UDP port 123 if NTP Time Management is in use.

Important Note regarding deprecated DNS names:

If your Gateway is configured to use an idigi.* or etherios.* DNS name, it should be re-configured to use the my.devicecloud.com url at your earliest convenience. You will need to create firewall rules for all IP addresses/ports used, for all Remote Management and Time (NTP) DNS server names used within your device.

Permalink


Cloud services can be used for applications built around Software as a Service (SaaS), Platform as a Service (PaaS), or Infrastructure as a Service (IaaS).

Digi International has a platform called iDigi. iDigi is a cloud platform for both device network management and for data management. The iDigi Device Cloud is designed using a high-availability architecture, with redundancy and failover characteristics. It is a highly scalable system that can host single units to tens of thousands of Digi devices. It also has web services APIs for secure application integration and data messaging. iDigi device clouds are located in Chicago and in London and you can select to which cloud your data is subscribed.

Device management also include the ability to send commands to remote devices. Standard web service calls are available to manage traditional device settings. An optional Server Command Interface / Remote Command Interface (SCI/RCI) mechanism is available for any custom device or application commands that may be required.

iDigi Manager Pro is a pay-as-you-go model, starting at $1.59 per registered device, per month. Sending data to and from the iDigi Device Cloud is billed on a transactional basis and are available at different usage levels. Data is managed through iDigi, which means that iDigi provides a collection point of data. iDigi is not a (long-term) data storage solution–Digi Dia data is stored for 1 day, and iDigi files are stored for 7 days.

Permalink


Unlike the ConnectPort WAN, the serial ports on the standard builds of the Digi Transport line are DTE not DCE serial, this means that a null modem cable should be used instead of a cross-over cable.

Null modem is a communication method to connect two DTEs (computer, terminal, printer etc.) directly using an RS-232 serial cable. The name stems from the historical use of the RS-232 cable to connect two teleprinter devices to modems in order to communicate with one another; null modem communication was possible by instead using RS-232 to connect the teleprinters directly to one another.

Permalink


Digi Transport (18)

View category →

The debug.txt file is useful for troubleshooting a variety of issues with Digi TransPort and Sarian branded routers.  There are a several methods available for extracting the debug.txt file, below are some common examples.

FTP Client

Using an FTP client, such as, Filezilla make an FTP connection to the router and “drag” the debug.txt file to
the PC.

FTP Using Firefox

Using Firefox, make an FTP connection to the router by typing the IP address of the router prefixed with: ftp://

For example: ftp://10.1.208.1

Enter the login details for the router and click “OK


Right click the “debug.txt” file then “Save Link AS”

FTP Using Internet Explorer

From Internet Explorer, make an FTP connection to the router by typing the IP address of the router prefixed with: ftp://

For example: ftp://10.1.208.1

Enter the login details for the router and click “OK”

Right click the debug.txt file then “Save target As”

HTTP (Web Browser) Method

Browse to the router’s IP address, login using an administrative username and password.
Then navigate to:

Administration – File Management > FLASH Directory

Right click on “debug.txt” and click “Save Target As”

NOTE: In other browsers the menu may be slightly different, for example with Firefox uses
“Save Link As”

Using “Execute A Command” Method

Browse to the router’s IP address, login using an administrative username and password.
Then navigate to:

Administration – Execute a command


And enter the following command:

type debug.txt

Click “Execute”

Using Microsoft Windows Telnet

NOTE: The debug.txt file is quite large so it may be necessary to increase the scroll back buffer in
telnet to make it large enough to capture the full file.

Click on the C:\ icon and select “Properties”.  Next click “Layout” and set the Screen Buffer Size Height to its maximum.  Click “OK”

Next, Telnet to the router’s IP address:

Enter the username and password when prompted.  Once connected issue the command:  “type debug.txt

There will be a large amount of output scrolling on the screen which may take several seconds.  The command is complete once [ENDCFG] is seen.

To copy the file, right-click on the page and select “Mark” from the drop-down menu:

Select the contents by right-clicking on the page and selecting “Select All” from the drop-down menu:

Copy the contents, by right-clicking and selecting “Copy”:

Open up “Notepad” and select “Paste” and save the contents.

Permalink


This Knowledge Article will describe how to configure a Digi TransPort router to failover between 2 IPsec tunnels and recover automatically.

Configure IPsec Tunnel 0

Open the web interface of the device and navigate to Configuration – Network > Virtual Private Networking (VPN) > IPsec > IPsec Tunnels > IPsec 0

Configure the primary IPsec tunnel Phase 2 like desired. For example  :

Note : for more information on how to build an IPsec tunnel between two Digi TransPort routers, please see at the end of this article for a link to an Application Note

ipsec 0 phase 2

Makes sure that the tunnel is set to “Whenever a route to the destination is available” and if the tunnel is down and a packet is ready to be sent to “bring the tunnel up

tunnel up config

Repeat these steps for the second IPsec tunnel.

Configure IPsec Tunnel 0 out of service

Navigate to Configuration – Network > Virtual Private Networking (VPN) > IPsec > IPsec Tunnels > IPsec 0 > Advanced

Check the box “Go out of service if automatic establishment fails

out of service

Click Apply and Save Configuration.

Configure IPsec Tunnel 1 inhibit

Navigate to Configuration – Network > Virtual Private Networking (VPN) > IPsec > IPsec Tunnels > IPsec 1 > Advanced

Under “Inhibit this IPsec tunnel when IPsec tunnels” enter 0

tunnel 1 inhibit

This option will prevent IPsec Tunnel 1 to be built if IPsec Tunnel 0 is established.

Verify failover

You can verify that the failover is happening and the second is started as soon as the first IPsec tunnel is set out of service in the eventlog :

08:55:08, 31 Oct 2014,Eroute 1 VPN up peer: responder
08:55:08, 31 Oct 2014,New IPSec SA created by responder
08:55:08, 31 Oct 2014,(1778) IKE Notification: Initial Contact,RX
08:55:08, 31 Oct 2014,(1779) IKE Notification: Responder Lifetime,RX
08:55:08, 31 Oct 2014,(1778) New Phase 2 IKE Session  37.83.216.184,Initiator
08:55:08, 31 Oct 2014,(1776) IKE Keys Negotiated. Peer: responder
08:55:07, 31 Oct 2014,(1760) IKE SA Removed. Peer: responder,Dead Peer Detected
08:55:07, 31 Oct 2014,(1776) New Phase 1 IKE Session 37.83.216.184,Initiator
08:55:07, 31 Oct 2014,IKE Request Received From Eroute 1
08:55:07, 31 Oct 2014,(1775) New Phase 1 IKE Session  90.121.123.244,Initiator
08:55:07, 31 Oct 2014,IKE Request Received From Eroute 0
08:55:07, 31 Oct 2014,Eroute 0 Out Of Service,No SAs
08:55:07, 31 Oct 2014,Eroute 0 VPN down peer: responder
08:55:07, 31 Oct 2014,IPSec SA Deleted ID responder,Dead Peer Detected

The device will however keep trying to build the IPsec tunnel 0 in the background until the remote peer comes back online/is available. At which point, the IPsec tunnel 1 will be dropped down due to the inhibit configuration.

08:59:07, 31 Oct 2014,(1789) IKE SA Removed. Peer: responder,Successful Negotiation
08:58:38, 31 Oct 2014,Eroute 1 VPN down peer: responder
08:58:38, 31 Oct 2014,IPSec SA Deleted ID responder,Eroute inhibited
08:58:38, 31 Oct 2014,Eroute 0 Available,No SAs
08:58:38, 31 Oct 2014,Eroute 0 VPN up peer: responder
08:58:38, 31 Oct 2014,New IPSec SA created by responder
08:58:38, 31 Oct 2014,(1789) IKE Notification: Initial Contact,RX
08:58:38, 31 Oct 2014,(1790) IKE Notification: Responder Lifetime,RX
08:58:38, 31 Oct 2014,(1789) New Phase 2 IKE Session 90.121.123.244,Initiator
08:58:38, 31 Oct 2014,(1788) IKE Keys Negotiated. Peer: responder
08:58:37, 31 Oct 2014,(1788) New Phase 1 IKE Session 90.121.123.244,Initiator
08:58:37, 31 Oct 2014,IKE Request Received From Eroute 0
08:58:37, 31 Oct 2014,(1787) IKE SA Removed. Peer: ,Negotiation Failure
08:58:37, 31 Oct 2014,(1787) IKE Negotiation Failed. Peer: ,Retries Exceeded
08:58:27, 31 Oct 2014,IKE Request Received From Eroute 0
08:58:17, 31 Oct 2014,IKE Request Received From Eroute 0

You can find a more in depth Application Note on how to build an IPsec tunnel between two Digi TransPort routers using Pre-Shared key like in our example at the following link :

http://ftp1.digi.com/support/documentation/AN_010_IPSec_Over_Cellular_using_Digi_Transport_Routers.pdf

Permalink


There are five main methods by which new firmware can be loaded onto Digi TransPort or Sarian routers: Digi Device Cloud (DC), Web interface, FlashWriter, S/FTP and USB flash drive.

Note that, because of changes in the firmware, the procedure for loading firmware has changed for the S/FTP and USB flash drive procedures beginning at firmware version 5.2.9.13.  Please note the different procedures when using these methods.

1. Digi Device Cloud / Remote Manager 2.0

After setting up your account on DC and configuring your TransPort to connect to DC, log into your DC account and add the TransPort if it is not already added. You will need to download the correct firmware to your PC. The “FTP” version of the firmware file is needed. (See the Web interface method in #2.) Right-click on the TransPort and select Firmware, then Update Firmware. Select Browse and navigate to the firmware file. Select the Update Firmware button. Wait while the process is completed.
Scheduled firmware updates using DC. In DC go to Schedules. Click on New Schedule. On the Device tab there is the option for Gateway Firmware Update. Click on it. Now a window will pop up with a ‘Browse’ to button. Click on it and browse to where you have the file saved on your desktop. You’ll also need to give a ‘Description’ to the operation before you can proceed. The Description field is at the top of the New Schedule window in yellow.

Then hit the Schedule button in the lower right hand corner. A new window will pop up showing you all the devices in your account. Pick which ones you want the firmware to be loaded too and on the left hand side pick the Future option and then the time/date you want it to happen.

That’s it. You can monitor the progress of the operation in the Operations window right next to the Schedules window. You have to keep hitting the refresh button to update though. If you’ve chosen multiple units to upload then double click on the operation and you’ll see which units completed and which ones, if any, failed.

2. Web interface method

The Web interface method of upgrading firmware can be used locally or remotely. It is available only in Digi TransPort firmware versions 5.149 and later. The method involves clicking the “Update Firmware” option in the Web interface, browsing to a local or remote zip file containing the firmware, then clicking the “Update” button to start the automated update process. Only individual firmware files are replaced during the upgrade, so when a unit is upgraded via the Web interface method its current saved configuration will be retained.
How to upgrade the firmware on a Digi TransPort router using the Web interface

3. FlashWriter method

The FlashWriter method of upgrading firmware can be used only locally, i.e. a serial and/or Ethernet connection between your PC and the router to be upgraded is required. With the FlashWriter method the entire system flash will be overwritten, which means that any configuration will be lost.
How to upgrade the firmware on a Digi TransPort router using Flashwriter – Serial Procedure
How to upgrade the firmware on a Digi TransPort router using Flashwriter – Ethernet Method

4. S/FTP method

The SFTP or FTP method of upgrading firmware can be used locally or remotely. A little more background knowledge is required in order to use the S/FTP method. It is assumed that the user is familiar with the operation of S/FTP client software and Telnet or SSH client software. Only individual firmware files are replaced during the upgrade, so when a unit is upgraded via S/FTP its current saved configuration will be retained.
How to upgrade the firmware on a Digi TransPort router using FTP to a firmware version earlier than 5.2.9.13
How to upgrade the firmware on a Digi TransPort router using FTP to firmware version 5.2.9.13 or later

5. USB flash drive method

The USB flash drive method of upgrading firmware can be used only locally. The USB flash drive method is especially useful for upgrading routers during a site visit. Once the USB drive is configured the update process involves simply inserting the USB drive into the front of the router, waiting for a few minutes for a flashing LED sequence to indicate that the upgrade is complete, removing the USB drive then rebooting the router (for example by power-cycling it). There are two methods of upgrading firmware with a USB flash drive:

Method A) Loading a complete flash memory image onto the router, in the form of a ‘.all file’ – this is similar to the FlashWriter method, in that the entire system flash will be overwritten and any existing configuration will be lost.

Method B) Upgrading individual firmware files – this is similar to the FTP or Web interface methods, in that since only individual firmware files are updated, any current saved configuration will be retained.
How to upgrade the firmware on a Digi TransPort router using a USB flash drive to a firmware version earlier than 5.2.9.13
How to upgrade the firmware on a Digi TransPort router using a USB flash drive to firmware version 5.2.9.13 or later

Permalink


When using a Digi TransPort Router with a Public SIM card, the issue of reaching this device by it’s IP address happens as most/all providers will dynamically assign IP addresses that will change at every connection / reconnection.

To overcome this problem, it is possible to use a Dynamic DNS host configured in the router. The Router will update the service provider with it’s current IP Address and / or any IP Address changes. This will allow the device to be reached without knowing it’s currently assigned IP Address

Digi TransPort Routers currently supports 3 service providers type :
– DynDNS.org
– No-IP.org
– Other

In this example, No-IP.org will be used as they allow registration of free Dynamic DNS hosts.

Before you can successfully register the IP address of your router with a service provider, you must create an account on their web site. In this example, no-ip will be used.

1- Sign-UP for a Free Account on No-IP

Go to https://www.noip.com/sign-up and sign-up for a free DDNS Account. When registering, the “hostname” will be the name used to reach your device, for example: “digitesteu.ddns.net

User-added image

2- Configure Digi TransPort DDNS settings

Open a web browser to the IP Address of the Digi TransPort Routers and navigate to Configuration – Network > Dynamic DNS

– Select the Service Provider, in this example: No-IP
– Enter the Host and Domain Name previously chosen during registration at the service provider, in this example: digitesteu.ddns.net
– Destination port can be left to 0. This will by default use HTTP port 80.
– DynDNS User Name is the username chosen during registration.
– DynDNS Password and Confirm Password is the password chosen during registration
– When is which interface to use to send DDNS updates. By default, use default route.

Click Apply and Save Configuration

User-added image

3- Verify DDNS update

3.1 – On Digi TransPort Router

Navigate to Management > Event Log. A line should show the DynDNS update success :

12:47:01, 10 Mar 2015,DynDNS 0 host 0 updated: good 90.121.121.151

3.2 – On No-IP.org website

Navigate to https://www.noip.com/members/dns/ and login with the previously created account credentials.

Under Manage Hosts, the domain name should be displayed with the current Digi TransPort’s Routers IP.

User-added image

4- Test Connection

Now that the DDNS update is done, open a web browser to the selected domain name (in this example : digitesteu.ddns.net). The Web interface of the Digi TransPort Router should be displayed

User-added image

Permalink


Gobi 2000/3000 Sprint Provisioning
Overview
This document is intended for Gobi Transport units over the Sprint network.  The purpose is to quickly walk you through running the Gobi Carrier Wizard, how to provision the device for Sprint networks.  It also highlights items to look at and how to test the unit.

Assumptions
This guide assumes that you have a PC that is able to reach the TransPort through the Ethernet interface to gain access to the WebUI for configuration purposes.

Information You Might Need
If possible, please try to gather the following information from Sprint as it might be necessary for possible issues:
MSL – Master Subsidiary Lock is required to allow the PTN and the MSID to be programmed
PTN – The phone number, which should contain 10 digits
MSID – The Mobile Station Identity or MIN, again 10 digits

Running the Gobi Carrier Wizard
The first thing that will need to do be done is run the Gobi Carrier Wizard to enable the device for Sprint. The following steps will guide you through this process:

1) Log into the WebUI through the Ethernet interface. (Default IP address is 192.168.1.1)

2) Once in the WebUI, click on Wizards on the upper-left hand side, as shown in the screenshot below:
User-added image

3) Click on the GOBI Carrier Wizard, and then click Next, as shown in the screenshot below:
User-added image
4) Choose Sprint, and click Next, as shown below:
User-added image

5) On the next page, you will see a line that says “Save configuration changes here”, with the “here” being blue in color and underlined. Click the ‘here’ link and then click Save on the next screen. Reboot the device after saving.

6) After the device reboots, log back into the WebUI.

7) Navigate to Configuration > Network > Interfaces > Mobile > CDMA Provisioning.

8) Under the section titled Automatic Provisioning, click the Start button. DO NOT fill in any of the 3 parameters unless told to by Digi.  DO NOT fill out anything under Manual Provisioning.
User-added image

9) This process will take ~2 minutes to complete. Once the process completes, a message at the top of the page will indicate if it has either been successful or failed to provision. If successful, click the Reboot link and reboot the device.  If failed, try provisioning again.  Please email Digi Technical Support with the debug.txt file (please see “When contacting Digi Technical Support” below) if the failure continues.

Once the unit is provisioned, it could take another minute or so before it establishes an IP address.

Indicators, WebUI

LED Displays

For the WR41 & WR44
W-WAN NET
Will illuminate steady if the unit is able to log on to the Sprint mobile network.

W-WAN SIM
This LED should not light up since you do not a SIM for a Sprint account.

W-WAN DAT
Represents data passing to and from the network.

Signal Strength
Here is a guide for the signal strength:

  • -113 dBm or less (0 LED) -> effectively no signal
  • -112 dBm to –87 dBm (1 LED) -> weak signal
  • -86 dBm to –71 dBm (2 LEDs) -> medium strength signal
  • -70 dBm or greater (3 LEDs) -> strong signal

The minimum recommended strength indication is 2 LEDs. If you have no or 1 LEDs lit, it is recommended that you fit an external antenna to the unit.

For the WR21
Service
Illuminates steady when there is a network connection to the WWAN interface and flashes when data is transmitted or received.

WWAN
Flashes to show which network mode the unit is operating in:
Off – no service
1 blink – GPRS mode
2 blinks – EDGE mode
3 blinks – UMTS mode
4 blinks – HSDPA mode
5 blinks – HSUPA mode
On steady – CDMA mode

Strength
Here is a guide for the signal strength:

  • -113 dBm or less (0 LED) -> effectively no signal
  • -112 dBm to –87 dBm (1 LED) -> weak signal
  • -86 dBm to –71 dBm (2 LEDs) -> medium strength signal
  • -70 dBm or greater (3 LEDs) -> strong signal

The minimum recommended strength indication is 2 LEDs. If you have no or 1 LEDs lit, it is recommended that you fit an external antenna to the unit.

WebUI

Locating the Mobile IP Address
On the Home page, you should see the Mobile IP address under PPP1 (W-WAN (CDMA)).

NOTE: If you get an IP address of 120.x.x.x, this is a false mobile IP address.  Please see the Troubleshooting section of this document.
User-added image

Under Management > Network Status > Interfaces > Mobile
User-added image

NOTE:  Use the above screenshot as a reference for the below information.

Mobile Connection  

Registration Status
This is the registration status of the mobile module with respect to the cellular network.
Ideally, it will show up as registered.

Signal Strength
The signal strength in dBm being received by the mobile module.
Here is a guide for the signal strength:

  • -113 dBm or less (0 LED) -> effectively no signal
  • -112 dBm to –87 dBm (1 LED) -> weak signal
  • -86 dBm to –71 dBm (2 LEDs) -> medium strength signal
  • -70 dBm or greater (3 LEDs) -> strong signal

The minimum recommended strength indication is 2 LEDs. If you have no or 1 LEDs lit, it is recommended that you fit a high-gain external antenna to the unit.

Mobile Statistics
IP Address
The IP address of the mobile interface.

Primary DNS Address / Secondary DNS Address
The primary and secondary DNS addresses used by the mobile interface

Data Received
The number of data bytes that have been received on the mobile interface whilst it has been connected.

Data Sent
The number of data bytes that have been sent on the mobile interface whilst it has been connected.

Mobile Information  
Current system ID
The current system ID reported by the mobile module.

Current network ID
The current network ID reported by the mobile module.

Network
The current network reported by the mobile module.

Signal strength 1xRTT
The signal strength in dBm being received by the mobile module from 1xRTT networks.

Signal strength EVDO
The signal strength in dBm being received by the mobile module from EVDO networks.

Manufacturer
The manufacturer of the mobile module.  For a Gobi module, you should see either Huawei Incorporated or Qualcomm Incorporated.

Model
The model of the mobile module.  Examples for the Gobi would be Huawei EM680, Qualcomm Gobi 2000, Qualcomm Gobi 3000.

MDN
The Mobile Directory Number (MDN) of the mobile module.

MIN
The Mobile Identification Number (MIN) of the mobile module.

ESN
The Electronic Serial Number (ESN) of the mobile module.

MEID
The Mobile Equipment Identifier (MEID) of the mobile module.

Firmware
The firmware running on mobile module.

Bootcode
The bootcode firmware running on the mobile module.

Hardware version
The hardware version of the mobile module.

Registration State
See Registration Status.

Roaming status
The current roaming status of the mobile module.

Service capabilities
EVDO, CDMA 1x, or both

Radio band
1900 MHz for Sprint.

Channel
The transmission channel in use.  25 for Sprint.

Preferred system
Specifies what you configured it for: CDMA, EVDO, or Auto.  You can set this under Configuration > Network > Interfaces > Mobile > Advanced.

PRL version
The version of the Preferred Roaming List (PRL) loaded on the mobile module.

Activation status
The activation state of the mobile module. It can be of the following:

  • 0 – Not activated
  • 1 – Activated

Raising and Lowering the Cellular Link
Under Management > Connections > PPP Connections > PPP 1 – W-WAN, you should see the Mobile IP Address, the Primary and Secondary DNS Address, as well as buttons to Drop or Raise the link.
NOTE: If you get an IP address of 120.x.x.x, this is a false mobile IP address.  Please see the Troubleshooting section of this document.
User-added image

Locating the Event Log

Under Management > Event Log
This page displays the current contents of the event log on the router.  This log records events throughout the Digi device’s system including cellular information.  Some of this cellular information you might see would be status codes, error codes, signal strengths, tower locations, & service available.
Note: The newest information is on top of this file.

Testing
Once you have set up the mobile settings on your unit and you see a mobile IP address, there are a couple of quick tests you can do to ensure your device is working.

Ping test

Unfortunately, you cannot do a ping test on the Sprint Network.  Sprint blocks this port (please see Sprint EVDO Blocked Ports under Troubleshooting, below).

Accessing the Internet

If you have a laptop or computer directly connected to your Transport, you can try opening a browser and accessing the Internet (for example ‘http://www.digi.com’).

NOTE: In order for this step to be a valid test, you must ensure you do not have another source to the Internet, such as being connected to your company’s network either via Ethernet or over Wi-Fi.

If this fails, please email Digi Technical Support with the debug.txt file (please see “When contacting Digi Technical Support” below).

Access the Transport Remotely

With Sprint as a cellular provider, they block certain ports.  A complete list of these blocked ports may be found in the Troubleshooting section below.  One of those ports is port 80, which is HTTP, which is the protocol normally used to access the Internet. With Sprint blocking this port, a user will no longer be able to remote into the Transport by simply entering the address (i.e. http://x.x.x.x where the x’s are representing the mobile IP address of the Transport).  Locally, the user will still have access to it using the local IP address.

In order to resolve the issue of getting into the Transport using the mobile IP address, there are two methods.

  1. With the Transport, there are two services for entering the Web GUI, HTTP or HTTPS.  Sprint blocks port 80, which is HTTP, but they do not block port 443, which is HTTPS.  To change to HTTPS, go to Configuration > Network > Network Services, then click the “Enable Secure Web Server” button.  You will then click the Apply button and then the Save.  Then click the Save All button.  Note that you will lose your connection.  At this point, in order to access either remotely or locally, you will need to specify “https” (i.e. https://x.x.x.x where the x’s are representing your local or remote address of the Transport).
  2. The HTTP service, in the Transport, besides the normal port 80, also accepts port 8080.  This means that you can keep the default settings and then enter the unit remotely specifying port 8080 (i.e. http://x.x.x.x:8080 where the x’s are representing the mobile IP address of the transport).  Note that locally you may still enter the WebUI of the Transport as you normally would (http://x.x.x.x where the x’s are representing the local IP address of the Transport).  To change to HTTP (which is the default setting), go to Configuration > Network > Network Services, then click the “Enable Web Server” button.  You will then click the Apply button and then the Save.  Then click the Save All button.

If you have a mobile terminated account, you should be able to access the Transport remotely.  Find a laptop or PC that has Internet access (outside of the Transport), open a browser, and specify, using https, the mobile IP address of the Transport (i.e. https://166.55.x.x).

If this fails, please verify that you have Web Server enabled (Configuration > Network > Network Services).  Having IP Forwarding (Configuration > Network > IP Routing/Forwarding > IP Port Forwarding/Static NAT Mapping) or IP Passthrough (Configuration > Network > IP Passthrough) enabled could affect these results as well.  Otherwise, if you cannot access your Transport remotely, the issue could be that you have a mobile originated account or a private account.  You should check this with your provider.

Mobile Originated vs. Mobile Terminated

Mobile Origination – Allows for outbound data to pass through the Digi and receive responses from the data request, but it does not allow for data originating from the Internet to pass through the Digi or to devices beyond it.

Mobile Termination – Allows for 2-way communication of data, where data from the Internet can reach the Digi and beyond, and data from the Digi can go to the Internet.

Troubleshooting
Ensure you are on the latest firmware
Updating your firmware may resolve your issue as well as enhancements to both your Transport and traces for troubleshooting.

  1. To check your firmware, go to Administration > System Information and note your Firmware Version
  2. Compare the firmware version to our latest release by going to www.digi.com > Support > Firmware Updates.
  3. Enter your Transport Model (i.e. WR21) in the field and then click on your particular model.
  4. It should bring you to a page for your product.  Choose the fimrware for the type of upgrade you will performing, either via FTP (WebUI) or FlashWriter, from the options on the page and save the file to your PC.
  5. Please follow “TransPort Firmware Upgrade Instructions” that is available under the General Firmware page listed above.

False Mobile IP Address Sprint units
120.x.x.x – If you see an IP address in the 120.x.x.x network for your mobile IP address, you should note that this is a false IP address.  Please attempt to re-provision your Transport.  If you still receive a false IP address, please provide the debug.txt file to Tech Support (please see “When contacting Digi Technical Support” below).  You may also need to contact Sprint, as well.

Sprint EVDO Blocked Ports
80/tcp filtered http
113/tcp filtered auth
135/tcp filtered msrpc
137/tcp filtered netbios-ns
138/tcp filtered netbios-dgm
139/tcp filtered netbios-ssn
445/tcp filtered microsoft-ds
559/tcp filtered teedtap
901/tcp filtered samba-swat
1022/tcp filtered unknown
1023/tcp filtered netvenuechat
1025/tcp filtered NFS-or-IIS
1433/tcp filtered ms-sql-s
3128/tcp filtered squid-http
3306/tcp filtered mysql
4000/tcp filtered remoteanything
4899/tcp filtered radmin
5000/tcp filtered UPnP
17300/tcp filtered kuang2
27374/tcp filtered subseven

Permalink


Digi Remote Manager (5)

View category →

Remote Manager uses tags to categorize devices.  You may want to edit the tags associated with a device if the purpose of a device changes or if you use tags to create a new sub-category of devices. Device tags are stored in Remote manager and not on the device.

To add a tag to a device:

  1. Click Device Management > Devices.
  2. Select the device you want to update.
  3. Click More > Edit Tags. The Edit Tags dialog appears.
  4. Enter the name of a tag in the text box and click Add Tag.
  5. Click Save. The new tag is associated with the device.

To edit tags for a device:

  1. Click Device Management > Devices.
  2. Select the device you want to update.
  3. Click More > Edit Tags. The Edit Tags dialog appears.
  4. Click the tag name you want to edit. The tag name appears in the text box.
  5. Edit the tag name as needed and click Change Tag.
  6. Click Save. The new tag is associated with the device.

To remove a tag from a device:

  1. Click Device Management > Devices.
  2. Select the device you want to update.
  3. Click More > Edit Tags. The Edit Tags dialog appears.
  4. Click the red X under action to delete the corresponding tag underStream Name.
  5. Click Save. The new tag is associated with the device.

Permalink


The groups feature allows you to add or create a group and assign a list of devices to that group. You can create a hierarchical structure of device groups to help organize your device inventory.

To create a group

  1. Click Device Management > Devices.
  2. Click the Groups button and select Add Group. The Add Group dialog appears.
  3. Type a group name.
  4. Choose the folder where you want to place the new group. The default is the root level.
  5. Click the Add Group button. The group name appears in the folder structure under the root directory in the left pane.

To add a device to a group
You can add one or more devices to a device group, and can add up to 500 devices to a group at one time.

  1. Click Device Management > Devices.
  2. Select the device(s) you want to add to a group:
  • Click any device list item to select that device.
  • Use Control-click or Shift-click to select multiple devices or a range of devices.
  1. Click More in the Devices toolbar and select Assign to Groupfrom the Organize category. The Add to Group dialog appears.
  2. Choose a group from the drop-down list.
  3. Click Assign to Group. The devices are added to the selected device group.

To move/remove a device from a group

  1. Click Device Management > Devices.
  2. Click a group name in your list of device groups you wish to remove the device from.
  3. Select the device(s) you want to remove from a group:
  • Click any device list item to select that device.
  • Use Control-click or Shift-click to select multiple devices or a range of devices.
  1. Click More in the Devices toolbar and select Assign to Groupfrom the Organize category. The Add to Group dialog appears.
  2. Choose a group from the drop-down list.  You may also select the “/” to move it to the root directory.
  3. Click Assign to Group. The devices are added to the selected device group or root.

To edit device group properties
You can edit device group properties, including the group name and its parent in the groups hierarchy.

  1. Click Device Management > Devices.
  2. Click a group name in your list of device groups.
  3. Click Groups and select Edit Group from the drop-down.
  4. Make changes to the group name and location as needed.
  5. Click Edit Group to confirm your changes.

To Remove a device group
Removing a device group removes the group itself and moves all devices in that group to the parent level in your device list.

  1. Click Device Management > Devices.
  2. Click to select the device group you want to remove from the device hierarchy in the left panel under Groups.
  3. Click Groups and select Remove Group from the drop-down. A confirmation dialog appears asking you to confirm that you want to remove that group.
  4. Click Yes to confirm. The group is deleted and any devices in that group move to the parent level in your device hierarchy.

To show or hide device groups
This feature will allow you to toggle the Groups display to hidden or visible.

  1. Click Device Management > Devices.
  2. Click the Show/Hide Groups button on the far left side of theDevices toolbar.

Permalink


This article describes how to configure Digi Device Cloud or Digi Remote Manager to send an E-Mail notification when a device goes offline.

Note: This article assumes that you have already created a Digi Device Cloud account or a Digi Remote Manager account, that your device is configured to connect to the cloud and added to your account.

Guidelines for NDS devices (Digi Connect WAN 3G, ConnectPort X etc..) can be found here : Configure a Digi Connect WAN or ConnectPort Gateway for Device Cloud connection

Guidelines for Digi TransPort can be found here : Configuring a Digi TransPort for Remote Manager connectivity

Guidelines for adding a Digi device to the Digi Device Cloud or Remote Manager platform can be found here : Adding a Digi Device to the Digi Device Cloud or Remote Manager Platform and here Add a Digi TransPort to your Remote Manager account

Create an Alarm

1. Log into your Digi Device Cloud or Digi Remote Manager account.
2. Click on the Device Management tab.
3. Click on the Alarms tab.
4. Click on the Add button

User-added image

The Add Alarm window will open.

1. Select Device Offline in the Alarm Type drop down menu.
2. Chose a name for the Alarm. (default is Device Offline)
3. Chose a description for the Alarm. (default is Detects when a device disconnects from Device Cloud and fails to reconnect within the specified time)
4. Chose for how long the cloud should wait before firing an alarm (defaul is 5 minutes. This is recomended in case of cellular devices that can sometimes lose network connectivity due to bad reception and allow it to reconnect)
5. Resets when device reconnects will allow the alarm status to be reset as soon as the device reconnects to the cloud.
6. Chose the Scope of the alarm. It can be per group or per device. Per Group allows to select the root directory (in this case the alarm will be applied to all devices on this account) or a single group.
7. Click Create to create the Alarm.

User-added image

Create an E-Mail Notification

1. Navigate to Admin Account Settings > Notifications
2. Click on the Add button.

User-added image

1. Chose a name for the Notification
2. Chose a Description for the notification. This will be shown in the “Subject” field of the E-Mail
3. Chose an E-Mail address to send the notification to.
4. Select if you wish to receive a daily summary of your alarms and at which time.
5. Check this box to receive an E-Mail notification each time an alarm triggers (Each time a device goes offline this will trigger an alarm which in result will trigger an E-Mail)

User-added image

6. Select “Send notification for the following alarms” and in the box, type the name of previously created alarm, by default “Device Offline” and press enter.
7. In the list, chose the previously created alarm and click on the “+” icon

User-added image

8. Click Save

User-added image

Testing

To test that the Alarms and notification are working, simply disconnect/turn off one of your devices which are monitored by this alarm. After the selected delay triggers, the alarm should fire and you should receive an E-Mail similar to this one :

User-added image

Permalink


Introduction:

This article will discuss how to configure your Digi TransPort router for use with Remote Manager by utilizing the built-in Web User Interface (WebUI) of the Digi TransPort itself.

Changing the Remote Manager connection settings from the WebUI

The Digi TransPort WebUI can be accessed locally via the local IP address (LAN or WAN), or the Cllular Mobile IP address (provided your cellular account is one which supports Mobile Termination, and that you left a pinhole for HTTP or HTTPS through which to get to the WebUI if configured for IP Passthrough).

If you know the Mobile IP address and have met the conditions above, you should be able to open the TransPort’s WebUI by opening a browser to the Mobile IP of your TransPort at this time, but keep in mind that accessing the TransPort WebUI via the Local IP is preferred if available, since it doesn’t affect your cellular bill, is faster, and generally less prone to connection loss.

If you can get to the Local IP of the TransPort (this is an Ethernet or Wi-Fi connected TransPort and you’re at that location), you should access the TransPort’s WebUI using the Local IP address instead. The Digi Device Discovery Tool for Windows can be used to discover the Local IP address of the TransPort, if unknown. If you run the Device Discovery Tool and see a “No devices found?” message, and you’ve verified your TransPort is both powered on and has a solid Link LED present, you may want to check this article for Digi Device Discovery Troubleshooting Tips.

Assuming you can access either the Mobile (WAN) or Local (LAN) IP address and are now looking at the Web User Interface of your Digi TransPort:

1. Open Configuration -> Remote Management -> Remote Manager on the WebUI, then click the check box for “Enable Remote Management and Configuration using Remote Manager”. It should look similar to this:

2. On the page above, from the drop down menu, select the desired Device Cloud server :remotemanager.digi.com for the US Cloud or remotemanager-uk.digi.com for the EU Cloud.

3. Ensure the “Automatically reconnect to the server after being disconnected” box is checked as shown in the example, and configured with the 10 second value listed (or a reasonable alternative), as this is the box that tells your router to re-connect to the Remote Management server, should the connection get broken for some reason

4. Apply any changes by clicking the Apply button, when configuration is complete.

5. Click the blue “here” link to save the configuration, as shown below:

6. Click the “Save All” button from the ensuing page and you should get a message saying “The configuration has been saved successfully!”, then click the OK button.

7. After a minute or so, you should see that your Transport has established (i.e. state = ESTAB) a Remote Management connection to the Remote Manager server by viewing the Management -> Connections -> IP Connections page under the “General Purpose Sockets” listing towards the bottom:

In Closure: If all went well, your Digi TransPort should now be “Connected” on the Remote Manager server you selected in step 1 above.

Permalink


Adding your Digi TransPort to Remote Manager

  1. Log into your Digi Remote Manager account.
  2. Click on the Device Management tab.
  3. Click on the Add Devices button on the tool bar

  4. Add the Digi TransPort by either discovering it locally, or manually adding the Device ID, using either of the the two methods described below:

Discovery method:

  1. After hitting Add Devices (step 3 above), click the Discover >> button.

  2. Click the Discover button on the 2nd Add Devices screen.

  3. Select the Digi TransPort to be added, and click OK.

Manual method:

  1. After hitting Add Devices (step 3 above), click the dropdown which defaults to MAC Address, and select Device ID instead.

  2. Populate the entry field to the right of Device ID with the Device ID of your Digi TransPort.  This can be obtained from the Digi TransPort WebUI Home page if needed.

  3. Click the Add button, then click OK.

Your Digi TransPort should now be added to Remote Manager:

After your device is added, it should show up in the list of devices as disconnected (a Red icon beside the device means Disconnected, see below).

After a minute or so, refresh the device list by clicking the Refresh button, and verify a Connected state as seen below.  A Blue icon indicate the device is connected to Remote Manager.

 

Conclusion:

If you see the Blue/Connected icon next to your TransPort, it means that your device was properly configured, and you can now manage your TransPort on Remote Manager.  If still not connected after a a few minutes, you’ll want to re-check your TransPort Remote Management and Network configurations, as well as make sure you aren’t running into any Firewall issues between the TransPort and Remote Manager.

Permalink


Digi Device Cloud (5)

View category →

HOW TO: Change the Device Cloud Name on Gateways Using Device Manager from the Device Cloud
To change the server name for the Device Cloud connection from your Device Cloud account, you will navigate to the Device Management tab, right click on the desired Digi device and select Properties.

From the Properties screen, navigate to Advanced Configuration > Remote management connection > Remote management connection 1.  Type in the server name (en://my.devicecloud.com) in the Server address field:

User-added image

Click Save to save the changes.  Your device may disconnect from the Device Cloud and reconnect using the new name.

Permalink


The following example shows how to create a task on Digi’s Device Cloud to change the Remote Management Server Address in a TransPort.
Log into Device Cloud
Click on Device Management > Schedules and then click New Schedule
User-added image

Click Start Walkthrough
Type in the description at the top of the screen for the task
On the left menu, select Command Line Interface
For the first command, enter cloud 0 server my.devicecloud.com
On the left menu, select Command Line Interface, again
For the second command, enter config 0 saveall
Then click Schedule at the bottom right hand corner
User-added image

Either select Immediate or Future to schedule when you wish to apply this change
If you choose Future, you will need to use the drop down buttons to specify the date and time and then you will see the scheduled job on the next screen.
If you choose Immediate, it will simply complete the job.
You will need to select the devices you wish to apply these changes to.  If selecting more than one, use the “Ctrl” button to select these.
Select Run Now at the bottom of the screen if you choose Immediate or Schedule if you choose Future.
User-added image

Here are the results for a scheduled job.
User-added image

After the scheduled event, you can check to see if it performed by going to Device Management  >  Operations.  You should be able to see if it successfully completed or not.  You may also click on Operation Details for each individual device.
User-added image
You can also see the changes in each individual device by going to Device Management > Devices, selecting a particular device by double clicking on it, click on Configuration, Remote Management, Remote Manager, Remote Manager Config, then check the Connect to Device Cloud server.  At first you will see the previous server name, but if you click Refresh at the bottom of the page, it will update.
User-added image

Permalink


This article describes how to configure Digi Device Cloud or Digi Remote Manager to send an E-Mail notification when a device goes offline.

Note: This article assumes that you have already created a Digi Device Cloud account or a Digi Remote Manager account, that your device is configured to connect to the cloud and added to your account.

Guidelines for NDS devices (Digi Connect WAN 3G, ConnectPort X etc..) can be found here : Configure a Digi Connect WAN or ConnectPort Gateway for Device Cloud connection

Guidelines for Digi TransPort can be found here : Configuring a Digi TransPort for Remote Manager connectivity

Guidelines for adding a Digi device to the Digi Device Cloud or Remote Manager platform can be found here : Adding a Digi Device to the Digi Device Cloud or Remote Manager Platform and here Add a Digi TransPort to your Remote Manager account

Create an Alarm

1. Log into your Digi Device Cloud or Digi Remote Manager account.
2. Click on the Device Management tab.
3. Click on the Alarms tab.
4. Click on the Add button

User-added image

The Add Alarm window will open.

1. Select Device Offline in the Alarm Type drop down menu.
2. Chose a name for the Alarm. (default is Device Offline)
3. Chose a description for the Alarm. (default is Detects when a device disconnects from Device Cloud and fails to reconnect within the specified time)
4. Chose for how long the cloud should wait before firing an alarm (defaul is 5 minutes. This is recomended in case of cellular devices that can sometimes lose network connectivity due to bad reception and allow it to reconnect)
5. Resets when device reconnects will allow the alarm status to be reset as soon as the device reconnects to the cloud.
6. Chose the Scope of the alarm. It can be per group or per device. Per Group allows to select the root directory (in this case the alarm will be applied to all devices on this account) or a single group.
7. Click Create to create the Alarm.

User-added image

Create an E-Mail Notification

1. Navigate to Admin Account Settings > Notifications
2. Click on the Add button.

User-added image

1. Chose a name for the Notification
2. Chose a Description for the notification. This will be shown in the “Subject” field of the E-Mail
3. Chose an E-Mail address to send the notification to.
4. Select if you wish to receive a daily summary of your alarms and at which time.
5. Check this box to receive an E-Mail notification each time an alarm triggers (Each time a device goes offline this will trigger an alarm which in result will trigger an E-Mail)

User-added image

6. Select “Send notification for the following alarms” and in the box, type the name of previously created alarm, by default “Device Offline” and press enter.
7. In the list, chose the previously created alarm and click on the “+” icon

User-added image

8. Click Save

User-added image

Testing

To test that the Alarms and notification are working, simply disconnect/turn off one of your devices which are monitored by this alarm. After the selected delay triggers, the alarm should fire and you should receive an E-Mail similar to this one :

User-added image

Permalink


The following example shows how to create a task on Digi’s Device Cloud to change the Remote Management Server Address in a TransPort.
Log into Device Cloud
Click on Device Management > Schedules and then click New Schedule
User-added image

Click Start Walkthrough
Type in the description at the top of the screen for the task
On the left menu, select Command Line Interface
For the first command, enter cloud 0 server my.devicecloud.com
On the left menu, select Command Line Interface, again
For the second command, enter config 0 saveall
Then click Schedule at the bottom right hand corner
User-added image

Either select Immediate or Future to schedule when you wish to apply this change
If you choose Future, you will need to use the drop down buttons to specify the date and time and then you will see the scheduled job on the next screen.
If you choose Immediate, it will simply complete the job.
You will need to select the devices you wish to apply these changes to.  If selecting more than one, use the “Ctrl” button to select these.
Select Run Now at the bottom of the screen if you choose Immediate or Schedule if you choose Future.
User-added image

Here are the results for a scheduled job.
User-added image

After the scheduled event, you can check to see if it performed by going to Device Management  >  Operations.  You should be able to see if it successfully completed or not.  You may also click on Operation Details for each individual device.
User-added image
You can also see the changes in each individual device by going to Device Management > Devices, selecting a particular device by double clicking on it, click on Configuration, Remote Management, Remote Manager, Remote Manager Config, then check the Connect to Device Cloud server.  At first you will see the previous server name, but if you click Refresh at the bottom of the page, it will update.
User-added image

Permalink


One very useful aspect of Device Management on the Digi Device Cloud is the ability to view the Connection History of a device.  This of course refers to the connection history of that device as viewed from Device Cloud, and is a record of a device’s connections and disconnections with the server, for whatever reason.

Device Cloud Connection History (from the device UI):

Getting the Connection History from the Data Streams API:

As seen above, the Connection History of a device is something which Device Cloud keeps track of.  A screen like the one above may be useful when wanting to know the current state of a device or what’s been going on with it, but short of taking a screenshot or copying/pasting that information into a text file, the information isn’t very portable.  The good news is, the Connection History is something which is also tracked as a Data Stream, and each of the Connect/Disconnect events is a separate Data Point within that Stream.

To query the Data Stream Connection History if the same device, we must query for the Data Points which make up that Stream as follows:

/ws/DataPoint/{deviceId}/management/connections/

Example Request:  /ws/DataPoint/00000000-00000000-00409DFF-FF5DF1CB/management/connections/

Response (for a single Data Point of the Stream):

<?xml version=”1.0″ encoding=”ISO-8859-1″?>
<result>
<resultSize>206</resultSize>
<requestedSize>1000</requestedSize>
<pageCursor>27f2d9aa-beab-11e5-92dc-fa163ea15feb</pageCursor>
<requestedStartTime>-1</requestedStartTime>
<requestedEndTime>-1</requestedEndTime>
<DataPoint>
<id>f5e6756c-75c8-11e5-8dc1-fa163ee3abab</id>
<cstId>70</cstId>
<streamId>00000000-00000000-00409DFF-FF5DF1CB/management/connections</streamId>
<timestamp>1445194168409</timestamp>
<timestampISO>2015-10-18T18:49:28.409Z</timestampISO>
<serverTimestamp>1445194168412</serverTimestamp>
<serverTimestampISO>2015-10-18T18:49:28.412Z</serverTimestampISO>
<data>{“connectTime”:”2015-10-18T03:14:07.442Z”,”disconnectTime”:”2015-10-18T18:49:28.409Z”,”type”:”Wi-Fi”,”remoteIp”:”213.35.189.122″,”localIp”:”192.168.82.204″,”bytesSent”:70412,”bytesReceived”:69588,”session”:”6b861b2f-bd52-4455-b9fc-dc92693460db”}</data>
<description/>
<quality>0</quality>
</DataPoint>…
</result>

As can be seen in the <resultSize> field, there were 206 Data Points in the response to the query, so I’ve only listed one Data Point as an example of the type of data retrieved from the Connection History Data Stream.

Permalink


NetCloud Engine (81)

View category →

Summary

This article describes the functions of the NameStation App and how the app would be used.


Configuration

The NameStation App allows for Alternate Naming with NetCloud Engine DNS (available on select plans):

So, if you had a Resource with the name of SVR_X43.ax4g32.pertino.net — it can be changed in a couple of ways:

  • In the app you can choose a custom subdomain for your network instead of ax4g32. Such as “acmecorp” (Release 270)
  • You can create up to 3 alternate names for the hostname portion, SVR_X43. Such as “corpfiles”or “corpdata” (Release 280)
  • With those applied, this Resource can be reached via NetCloud Engine DNS with the following lookups:
 **corpfiles.acmecorp.pertino.net** or **corpdata.acmecorp.pertino.net**

Permalink


Summary

How to resolve connectivity issues with NetCloud Engine Linux Gateway:

With NetCloud Engine Linux Gateway installed, and a registered web server as an “external device” associated with that Gateway.


Configuration

Configuration Difficulty: Intermediate

This scenario is for NetCloud Engine Linux Gateway on CentOS “minimal server”, running on an ESX VM. The CentOS server was a default installation, with no additional software besides the NetCloud Engine Linux Gateway.

The ESX box, in this example, is in a data center behind an L3 switch. L3 switch connected to the site router/firewall, which connects to the Internet. A web server is also connected to the L3 switch.

A static rule is applied to the site router/firewall for traffic destined to 172.86.160.x: the next hop would be the L3 switch. On the L3 switch, another static rule sends traffic for 172.86.160.x to the NetCloud Engine Linux Gateway on the ESX VM.

HTTP connectivity to the web server is okay using the internal network addresses (ex. 192.168.0.x) but there is no connectivity using NetCloud Engine Linux Gateway FQDN or 172.86.160.x address for that external device.

Solution:

The CentOS “minimal server” includes a firewall that’s enabled by default. In effect, the customer had installed a firewall in front of the NetCloud Engine Linux Gateway that was blocking L4 traffic. We simply disabled the firewall, as root on the CentOS server:

# systemctl stop firewalld

# systemctl disable firewalld

Permalink


Summary

This article provides a workaround to the issue of host name resolution not functioning correctly.


Issue

You try to access a remote computer listed in the NetCloud Engine Connect workgroup and get the error message “Windows cannot access \Computer Name”. However, you can ping the remote computer’s IPv6 address successfully.

In this situation, it is possible LLMNR (IPv6 name resolution) is not able to respond because DNS is responding first, or LLMNR is turned off or being blocked.


Workaround

To workaround this issue you can edit the hosts file by adding the IPv6 address and hostname of the remote machine.

  • Check what IPv6 address is assigned to the host:
    • In windows command prompt type ipconfig and look for the IPv6 address under the Ethernet adapter NetCloud Engine Connection.
  • From Notepad (Run As Administrator), select File and then Open.
  • Navigate to the C:\Windows\System32\drivers\etc\hosts file.
    • Make sure to select All Files (.) to show the file called hosts.
  • Add the IPv6 address then the name of the machine at the bottom of the page. Select File, then Save.

Permalink


Summary

When using ADConnect, NetCloud Engine configures the virtual interface with the defined DNS server(s). Since NetCloud Engine is usually the last interface installed, it gets put on the top of the list in the interface binding order. In Microsoft, this tends to be the first interface it looks at when determining which DNS server it will use for DNS look ups. This is normally OK but if you have a split DNS for a host that would resolve both publicly and privately (For example MS Exchange/Outlook Anywhere), this would cause problems resolving it properly.

In the case of Outlook Anywhere for remote users, using MS Outlook to connect to MS Exchange via the internet, the name of the server needs to resolve to public IP. If it were resolved internally it would get a private IP. When using ADConnect, the DNS query would go through the NetCloud Engine tunnel and directly to the internal DNS server. This is a problem if NetCloud Engine was not running on MS Exchange as it would not be able to connect to the server. (You could decide to install NetCloud Engine on MS Exchange but then there wouldn’t be a reason to use Outlook Anywhere).

The easiest way to resolve this problem is to change the binding order on the remote computer by moving the NetCloud Engine interface lower than the active LAN interface. This way it will be able to resolve the public IP using the LAN configured DNS.

To get to the screen below, go to the adapter settings and then select the Organize then layout and the menu bar. The menu bar will show Advance and then Advance Settings. Make sure in the Connections section that NetCloud Engine is lower and then select OK.

User-added image

Permalink


Configuration

Configuration Difficulty: Intermediate

To share a folder on a Mac in your NetCloud Engine network, make sure File Sharing is enabled and SMB is selected as a protocol to use. First, select the Launchpad from the Dock and click on System Preferences. In the Internet & Wireless section select Sharing. Make sure “File Sharing” is checked and then select Options… Verify “Share files and folders using SMB (Windows)” is checked. From here you can specify the folder you would like to share. In the Shared Folders section, select the + to add the folder you want to be shared and then select Add. Next, add or remove users as well as provide the proper permission to the folder (Read or Read & Write).

You can also share a folder by right clicking the actual folder and select “Get Info”. Check the Shared folder option and then under “Sharing & Permissions:” select the + option to add a user or group as well the permissions to access this folder.

To access the new shared folder from your NetCloud Engine Network:

Mac – From Finder, select Go and then Network and Shared. Double-click the name of the Mac and provide the username and password to access the share.

Windows – From the Windows File Browser, select Network and on the right pane window double-click the name of the Mac and provide the username and password to access the share.

Permalink