IntroductionPlease note that Infiot Edge devices are no longer sold in the SkySwitch Store. This guide serves to help those who have already purchased the product.This user guide will help you understand and configure the Infiot iXEdge-100 SD-WAN solution. This guide includes an overview of the Infiot Edge functionality, authority hierarchy and terminology, standard network topologies, the processes of creating all necessary configuration components within the web interface, and a hardware guide to help set up and troubleshoot the device.Infiot provides a secure, compliant, cloud-hosted service held to the strict audit standards of PCI Level 1 Service Provider and HIPAA. Hosted services are distributed in tier-1 datacenters, with certifications such as SAS70 Type II, SSAE16, and ISO 27001. Infiot HIPAA certified Intelligent Access solution with thin, wireless edges unlocks the power of LTE and 5G, local application processing, and zero trust security. A HIPAA Security Validation of Compliance Letter can be viewed below.Download Link: Infiot HIPAA Security Attestation of Compliance Letter (PDF)Infiot Edge - How it worksThree components make up the Infiot SD-WAN solution, including web-based Central Management, a Cloud-Hosted Controller, and an Extensible Edge.Cloud-Hosted ManagementInfiot Cloud-Hosted Management is a tool that offers complete configuration and visibility into edge and application health while enabling automated and secure software updates to one edge or multiple edges at the same time.Cloud-Hosted ControllerThe Infiot Cloud-Hosted Controller provides separation of control plane and data plane functionality. This separation offers scale and ensures data-plane continuity in case the control plane goes down. The Controller leverages a standard-based BGP route reflector for interoperability. The Infiot Controller transparently distributes the routing information and simplifies key management using unique keys with PKI automation.Extensible EdgeInfiot Edge provides transport-agonistic connectivity with zero trust security, using LTE, Ethernet, or WiFi to applications in any location, including private data centers and public clouds.Hierarchy and TerminologyWithin the Infiot Web Interface, each user is assigned a level of authority that dictates how much information the user can access. The hierarchy consists of Top Level → MSP → Organization. As a Top Level authority, SkySwitch can see endpoints and offer Support and troubleshooting for Resellers (the MSP).User accounts can exist on both the MSP and the Organization levels. The MSP level has access to all organizations under their MSP account. The Organization level only has access to devices within the organization. Throughout this guide, there are several frequently used terms, and those terms are identified below. Edge refers to the Edge of the Network, the device itself. Customer edges are referred to as Spokes that connect to the hub.Edge Policies refer to a set of rules applied to the Edge device concerning QoS and traffic shaping. Hub refers to the datacenter host which can egress data over a secure connection. Spoke refers to an edge device that is connected to a hub.MSP refers to the Reseller top-level authority that houses organization(s). Organization refers to a site where devices are installed. Organizations can have their own users, allowing them to provide access to their end customers; if they have an IT staff.NAT refers to Network area translation, which typically needs to be set on the WAN interface.Proxy ARP refers to a technique where the edge device answers ARP requests intended for another host. If a user wants to put a firewall behind the Edge device, they would need multiple static IP addresses from the ISP. The Edge can then send ARP requests on behalf of the Firewall and pass traffic through to the Firewall.Typical Network TopologiesThis section details a few standard network topologies to be used with the Infiot Edge. These details include a brief description of the configuration and a visual topology diagram showing which port(s) are being utilized.Spoke ConfigurationThe example topology below shows the Infiot iXEdge-100 with the WAN port connected to an Internet link. The LAN port is connected to an L2-switch port.Proxy ARPProxy ARP is a technique where the edge device answers ARP requests intended for another host. In the example below, an Infiot iXEdge-100 is deployed to provide Application prioritization and optimization for the voice traffic without making any changes to the existing topology with the firewall appliance.With this configuration, the Infiot Edge responds to the ARP requests intended for the firewall appliance so that traffic from the firewall passes through Infiot Edge. This enables the Infiot Edge to prioritize voice traffic and control oversubscription of bandwidth by data traffic from the client's connected behind the firewall. The WAN interface and firewall IP should be on the same subnet for Proxy ARP to work correctly.Web Interface GuideThis chapter details how to use the Infiot web interface and what options are available with this tool. The Infiot web interface allows users to view and create organizations, other users, edge devices, edge policies, and more.User MenuWhen a user first logs in to the Infiot web interface, they will notice the User Menu Bar on the page's left side, shown below. This menu allows users to create and manage edge devices, view a log of events, create and configure Edge policies, and more. EdgesThe Edges button allows users to create and configure new Edge devices and modify existing Edge devices. If any Edge devices are already configured, they are listed here. Selecting the "..." button to the right of any Edge device provides the options to Configure, Upgrade, Monitor, Events, Console, Clone, Restart, Activate, or Delete. EventsThe Events button allows users to view a log of events regarding Edge device changes. This section enables users to see user login information, edge status, configuration changes, and more. This information includes date and time stamps.Edge PoliciesThe Edge Policies button allows users to select or create a set of policies that can be applied to Edge device(s). If an Edge Policy has already been created, it can be viewed here. If a user selects the "..." button to the right of an existing policy, they have access to Edit, Events, Clone, Disable, and Delete option.AdminIf available, the Admin button allows authorized users to see all users that have access to the Edge Interface, including their "Role" or Authority level. If a user selects the "..." button to the right of a user, they have access to View, Events, Disable, and Delete options. Note: Users will only be able to log into their URL or sublevel URLs. An identical login email address can exist on an MSP level and an Organization Level. The MSP level login can access the Organization, but the Organization will only be able to access its Organization. Usernames and passwords are bound to the URL subdomain.SettingsThe Settings button allows users to change the appearance, notification, and authentication settings of the web interface. Online HelpThe Online Help button allows users to access several guides related to device activation, global events, content filtering, and more. Once selected, the selected guide appears in the same window.Create an OrganizationAfter logging into your MSP Portal, please complete the following to create your organization:Under Tenants, create an organization by clicking the "+" button.Enter the organization Name, Description, and Domain Name. Under Domain Name, enter a name that Infiot will use to generate an FQDN for your Org, for example: if you enter 'ssmlv', the organization will be accessed at https://ssmlv.infiot.netEnter Tenant Type as "Organization."Click "Create."Create UserBefore others can access the Infiot web interface, they must be created as a user.Create a User by selecting the newly created MSP. Click the"Admin" button on the left.Click the "+ New User" button on this page.Enter the name of the user (This name must be in lower-case).Enter the email of the user (An invitation email is sent to this email address).Enter the Role (Admin, Operator, or Monitor).Click "Create."User Sign-inEach time a new user is created, they must follow a unique process to access the web interface in the following order:The email recipient user receives a welcome email from support@infiot.com. The recipient must click the "Login" button in this email to proceed.The recipient can utilize SSO (Single Sign-On) if they have a Google or Microsoft Email Account; or otherwise, select 'Sign up'.The user is signed in and taken to the Edges home page.Create EdgeAfter an organization is created, users can create and configure their Edge device(s). Multiple edges can be created for a single organization.  From the "Tenants" menu, select the Organization to be taken to its web interface.On the "Edges" menu, click the green "+" button to create an Edge device.Note: The Edge menu has a process flow sub-menu that must be followed for changes to be saved. It is vital to click "Finish" and then "Save" for all changes to take effect.Enter the Device Information.Edge NameAddress Fields (Some users may need to turn off "GeoIP Location" and enter the address manually)Description (Name)Serial NumberSoftware Version (leave as suggested)Model (enter the router model as it appears on the package sticker)Under the "Interfaces" menu, select "WAN"Ensure the configuration is set to "Routed" at the top of the page.It is recommended that the addressing configuration is set to "DHCP Client" initially. However, if the user needs this to be configured as a static address, this can be changed again after the edge is activated.At least one interface should be set to "DHCP Client" for the initial edge activation to ensure the device automatically comes online and downloads the configuration (The device will need to obtain an IP from a different router). Suppose the network configuration only includes a single WAN link and it is static. In that case, the user should configure the OPT interface as a DHCP Client for the initial activation (OPT will need to obtain an IP address from a different router temporarily).If using a static configuration, enter the IP Address, Mask, and Gateway address. This is not applicable if using "DHCP Client" configuration.Click "Overlay" and toggle "Overlay" On.Click "Advanced" and make sure NAT is toggled On.Click Apply, and the user is taken back to the interfaces menu.Under the "Interfaces" menu, select "LAN" and configure.Ensure the configuration is set to "Routed" at the top of the page.If a user wishes to change this configuration to "Switched," they are required to create VLAN settings that can be selected from the "Native VLAN" option that appears on this page. VLAN setup is detailed in the next section of this chapter.Ensure the addressing configuration is set to "DHCP Server."Under "Addressing," enter the IP address and Mask.Ensure "Advertise Subnet" is turned On.Under "IP Address Pool," enter the start address and the end address.Under "DHCP Options," click "Add DHCP Options" and enter "66" into the Code field, and enter "https://sipcfg.io/cfg" into the Value field. Click Apply and the user is taken back to the Interfaces menu.Under the "Interfaces" menu, select "+Add VLAN" and configure (This step may be skipped if VLAN is not applicable).Enter a name and ID (Default is vlan1 and 0).Click the "Addressing" section to expand and ensure the addressing configuration is set to "DHCP Server."Under "Interface IP," enter the IP Address and Mask.Click "Add IP Address Pool," enter the start address and the end address.Click "Apply," and the user is taken back to the "Interfaces" menu.Click "Finish" and then click "Create."On the "Edges" menu, find the MSP that was just created and click the vertical "..." button to the right and select "Activate."Once selected, a message appears regarding activation directions. Click "Yes" to proceed.The user is prompted to enter an activation email. The entered email address is sent a device activation invite.Note: If an activation email is generated more than once, only the most recent activation email is considered valid. All previous activation email(s) expire once a new one is generated.Edge User ActivationAfter completing the steps above regarding Edge creation and activation, the invited user receives an activation email advising the following instructions:Connect the Infiot Edge to power and connect the Internet/WAN links.Find and connect to WiFi network infiotedge and use password infiot123.Click the Activate button (inside the email).The user is taken to the Edges menu to see the device's status as "Online" after a few minutes.Create Edge PoliciesOnce the user has configured their Edge device(s), they are able to create Edge policies that allow traffic shaping. This chapter details the process to locate data center IP addresses, a general guide to creating edge policies, and how to apply these rules to an edge once created. Standard edge policy configuration parameters are detailed at the end of this chapter.Note: Once an Edge Policy has been created, it will not take effect until it is manually applied to a selected edge device. This process is detailed in this chapter under the section titled "Apply Rules To Edge".Data Center IP Address LookupBefore creating these policies, users may need to locate the data center IP addresses used to configure each rule.To locate the data center IP addresses, run the following computer command, and replace "Your Reseller ID" with the organization's numeric Reseller ID: nslookup -type=SRV _sip._udp.Your Reseller ID.hpbx.outboundproxy.com Once complete, users can see the information below.The order of these data centers is determined by weight. This number is listed after "service =," and the lowest weight indicates which data center is the highest priority.The first service listed as "g1-sw01.nms.outboundproxy.com" is the Dallas data center, with a weight of 20. The second service listed, "g1-se01.nms.outboundproxy.com" is the Atlanta data center, with a weight of 30. Once the user has confirmed the services' name, they can use the ping command for "g1-sw01.nms.outboundproxy.com" to obtain the IP address for the Dallas center, as seen below.Repeat this same process for the other location, "g1-se01.nms.outboundproxy.com", to obtain the IP address for the Atlanta center, as seen below.General Edge Policy CreationThis section details the entire process to create and configure an Edge Policy. As a reminder, standard edge policy configuration parameters are detailed at the end of this chapter. To create a new Edge Policy:Click "Edge Policies" on the left side menu bar.Click the green "+ Add Policy" button to begin creating a policy.Note: The Policy menu has a process flow sub-menu that must be followed for changes to be saved. As such, it is vital to click "Save" at the bottom of the page for all changes to take effect. If a user cannot see a "Save" button, click "General Settings" and click the button on this page to save any changes.Under the "Overview" page, create a name for the policy, such as "SIP."Click "Topology" at the top of the page and click "Add destination," where a user can select the hub(s) they wish to add. Once a hub is added, a user can add another by clicking "Add destination" again. Once all hubs have been added, click "Save."The user is taken to the "Configure Policies" page where they can add rules by clicking the "..." configure button on the right and selecting "Edit."Select "QoS" at the top of the page. Once displayed, click the "+Add Rule" button and click the default "new-rule" that appears so it can be modified.Under "Match Criteria," enter the following:NameDestination Address Type Options: Internet, IPv4, or Port (range)IPv4 Address (Enter address entire subnet)Under "Priority," enter the following:Priority Options: High, Medium, Low, Drop, or AutoTraffic Class Options: Auto, Voice, Video, Transac, or BulkUnder "Path," enter the following:Under "Active" to the left, click "Add Path." Active Path Options: Direct-Internet or OverlayActive WAN Label Options: Wired, Wireless, Private, and MeteredUnder "Backup" to the right, check the box to the right of "Backup" and click "Add Path."Backup Path Options: Direct-Internet or Overlay Backup WAN Label Options: Wired, Wireless, Private, and MeteredUnder "Destination," enter the following:Destination Options: Auto, Direct, or Hubs that have been previously added.Under "Finish," click "Apply."Once applied, the user is taken back to the QoS tab showing the created new policy.Important Step: Once all rules are created, be sure to select "Save" at the bottom right of the QoS page or any other page that shows a "Save" button at the bottom right.Apply Rules to EdgePlease note that rules are not automatically applied to the edge device(s). After policy rules have been created and saved, they must be manually applied to the selected edge before they can take effect.To apply Policy Rules to an edge:Locate the edge via the "Edges" button in the Infiot menu bar on the left side of the page.To the right of the selected edge, click the "..." button and select "Configure."At the top of this page, click "Virtual Networks" and then select "GLOBAL."On the following page, click the "Policy" drop-down menu to select an existing policy. Once selected, click "Apply" at the bottom right.Once applied, click "Finish" at the top of the page and select "Save" to ensure the rules are applied.Standard Rule Configuration SettingsThis section provides the configuration settings for four standard rules in the order that they should be prioritized. These rules include a primary data center, a failover data center, a second failover data center, and other traffic/local breakout rules. It is important to note the 4th rule listed as "OtherTraffic" is used for both Other Traffic and Local Breakout functions. Before these configuration settings can be applied, a user must first complete steps 1-6 in the section titled "General Edge Policy Creation."LTE Failover Note: If you plan to use the LTE Failover functionality, please be sure to review the next section that includes two special QoS rules designed to reduce LTE usage inefficiencies. These two rules should be used in addition to the QoS rules detailed in this section.Each rule is detailed by the configuration settings entered in the Match Criteria → Priority → Path → Destination → Finish process flow seen below.Note: Once a rule has been created, the user can easily change the order by dragging and dropping the rule higher or lower in the list as seen below. Rule 1 Configuration - Primary Data CenterMatch CriteriaName: IP1-SRV(DAL)Destination Address Type: IPv4IPv4 Address: 75.98.50.0/24PriorityPriority: HighTraffic Class: VoicePathTo the left, click "Add Path." Active Path: OverlayActive WAN Label: WiredTo the right, check the "SLA Mode" box and click "Add Path."Backup Path: OverlayBackup WAN Label: WirelessDestinationSelect the Hub "MT-Hub-Dallas"FinishClick "Apply," and the rule configurations are saved.Rule 2 Configuration - Failover Data CenterMatch CriteriaName: IP1-SRV(DAL)BCKPDestination Address Type: IPv4IPv4 Address: 75.98.50.0/24PriorityPriority: HighTraffic Class: VoicePathTo the left, click "Add Path." Active Path: OverlayActive WAN Label: WiredTo the right, check the "SLA Mode" box and click "Add Path."Backup Path: OverlayBackup WAN Label: WirelessDestinationSelect the Hub "MT-Hub-Atlanta"FinishClick "Apply," and the rule configurations are saved.Rule 3 Configuration - Secondary Failover Data CenterMatch CriteriaName: IP2-SRV(ATL)Destination Address Type: IPv4IPv4 Address: 207.254.80.0/24PriorityPriority: HighTraffic Class: VoicePathTo the left, click "Add Path." Active Path: OverlayActive WAN Label: WiredTo the right, check the "SLA Mode" box and click "Add Path."Backup Path: OverlayBackup WAN Label: WirelessDestinationSelect the Hub "MT-Hub-Atlanta"Finish Click "Apply," and the rule configurations are saved.Rule 4 Configuration - Other Traffic/Local Breakout Match CriteriaName: OtherTrafficDestination Address Type:IPV4: 0.0.0.0/0PriorityPriority: AutoTraffic Class: AutoPathTo the left, click "Add Path." Active Path: Direct-InternetActive WAN Label: WiredDestinationSelect "Direct"FinishClick "Apply," and the rule configurations are saved.Note: As a reminder, once the rules have been created, please be sure to click "General Settings" and click "Save" at the bottom right.LTE Failover Rule Configuration SettingsImportant Note: If you plan to use LTE Failover, please implement the additional QoS rules detailed below in addition to the rules mentioned in the previous section. This section provides the configuration settings for two additional rules that should be implemented if you plan to use LTE Failover functionality. LTE is still functional while using the standard four QoS rules detailed in the previous section, however, these rules modify the sensitivity of the failover event so it is only active when a substantial loss is detected. For example, if you use the LTE Failover function without implementing these two additional QoS rules, there is a risk of the Device failing over as soon as a minimal loss is detected on the main WAN, resulting in a higher than needed LTE usage. As in the previous QoS Rule section, each rule is detailed by the configuration settings entered in the Match Criteria → Priority → Path → Destination → Finish process flow seen below. These two rules should be placed at the highest priority in the QoS Rule list. LTE Failover Rule 1 Configuration - Primary Data CenterMatch CriteriaName: DAL (SIP)Destination Address Type: IPv4IPv4 Address: 75.98.50.0/24PriorityPriority: HighTraffic Class: TransactionalPathTo the right, check the "SLA Mode" box.DestinationSelect the Hub "MT-DAL-HUB02"FinishClick "Apply," and the rule configurations are saved.LTE Failover Rule 2 Configuration - Failover Data CenterMatch CriteriaName: ATL (SIP)Destination Address Type: IPv4IPv4 Address: 207.254.80.0/24PriorityPriority: HighTraffic Class: TransactionalPathTo the right, check the "SLA Mode" box.DestinationSelect the Hub "MT-HUB-ATL02"FinishClick "Apply," and the rule configurations are saved.Once the Standard and LTE Failover QoS Rules have been created, they should be ordered as seen below:SIP (DAL)SIP (ATL)IP1-SRV (DAL)IP1-SRV (DAL) BCKPIP2-SRV(ATL)Other Traffic/Local BreakoutClone an OrganizationTo begin cloning an organization: Login to the MSP Portal and navigate to Tenants. Then, locate the Organization to be cloned and click the 'Three Dots' icon to the right of the organization and select 'Clone.'In the dialog box that appears, enter the following:Name: Enter the new organization’s name.Domain Name: Choose a domain name.Include Edges: Check the cloned edge name only (do not include the hubs).Include Policies: Select the cloned organization's policy. Once complete, the new organization will be created and will be displayed in the current list of organizations.Click on the name of the new organization to access the new cloned organization portal and verify that it is properly cloned and the edge policy is included.Edit the new organization's edge by navigating to Edges → Old Edge Name → 'Three dots' button to the right and update the below items with the new organization’s information:Edge name & address The Serial number of the router to be installed for the new organization.Once this information is entered, be sure to save the changes.Once the above is complete, go to the Partner Hub and attach hubs to the new organization.Hardware GuideThis section details the initial setup of the Infiot iXEdge-100 device as well as any information or process relating to the physical device.Infiot iXEdge-100 Device OverviewThe following is included in the Infiot Edge packaging:iXEdge-100 Unit x1Power Adaptor x1The iXEdge-100 device ports, lights, and other device information is detailed below. Please note, an earlier chapter of this guide titled "Typical Network Topologies" includes a few standard topology configurations to aid in the initial setup of the device.The front side of the iXEdge-100 device includes a USB, WAN, LAN, OPT, and USB 3.0 port. Each of these ports can be configured via the Edges → Configure → Interfaces menu from within the Infiot web interface. The backside of the iXEdge-100 device includes the power adapter port to be used with the power adapter that is included with the device. The backside also includes two WiFi antennas that can be adjusted and removed.The top side of the iXEdge-100 includes three LED lights. These lights may show solid illumination, blinking light, or they may not be illuminated at all, depending on the connection's status.Note: The USB Wireless feature is currently unavailable, and this feature is expected to be added in a future firmware update.Connection LED (Left)Off: There is no connection present.Blinking Light: A network connection is being established.Solid Light: A network connection is established and active.USB Wireless LED (Middle)Off: There is no USB Wireless connection present.Blinking Light: A USB Wireless connection is being established.Solid Light: A USB Wireless Connection is established and active.Power LED (Right)Off: The device is not receiving power. Solid Light: The device is receiving power.The bottom side of the iXEdge-100 includes the MAC address of the device and the Serial Number of the device.Note: The device serial number is required to configure the device in the Infiot web interface initially.Factory Reset ProcessThe iXEdge-100 device factory reset process must be completed on the physical device as it requires the power adapter to be removed multiple times. After this process is complete, the user will receive an email to confirm the activation of the device. To begin the Factory Reset process:Power Cycle the device three times.This process consists of disconnecting the power adapter from the back of the device until all LED lights on the device are off and then reconnecting the power adapter.With each power cycle, be sure to wait for the Connection LED on the left side of the device to begin blinking before disconnecting power.Once complete, the user receives an email. Click the Activate button in this email.When prompted, click the Activate button one more time to begin the activation process.Once complete, the status shows "Online" from within the Infiot Web Interface, as seen below.USB Interface Failover (USB Dongle & Tethering) GuideIf your primary ISP experiences an outage, you can seamlessly failover to a backup cellular connection. When this occurs, any active VoIP calls during the outage will stay connected and roam over to the cellular line. You can plug in a ZTE Dongle with a SIM card or use USB tethering from your cell phone.This section details how to enable USB Interface Failover from the Infiot Web Interface, how to enable USB Tethering from your wireless interface device, and how to verify if USB Interface Failover is working correctly.Enabling the USB Interface on your Infiot Edge deviceTo enable the USB Interface:From the Infiot Web Interface, select "Edges."Locate the device you wish to modify. Once found, click the vertical "..." button to the right and select "Configure."From this page, select "Interfaces." To the right of the Interface "USB0," toggle the switch to enable this interface. Once enabled, click the USB0 interface to be taken to the Interface Configuration menu.From the Interface Configuration menu, click and enable "Overlay."Underneath Overlay, locate "WAN Label" and change this to any option except "Wired."The primary interface should already be configured as wired, and as this feature enables a failover option, wireless, private, and metered are the only suitable options for this interface.Click "Advanced" and enable NAT.Click the "Apply" button at the bottom.Select "Finish" at the top of the page.Click the "Save" button to apply the changes.Important Note: If you have not already, you will want to make sure your Infiot Edge is configured for failover from a Wired connection to a Wireless connection. This failover configuration can be viewed and modified from the Infiot Web Interface by going to Edge Policies → [Your Policy Name] → QoS → [Your First Rule] → Path. Please be sure "SLA Mode" is enabled and configured as seen below.Enabling USB Tethering on your Wireless Interface DeviceEnabling USB Tethering on a wireless interface device is typically a simple process. However, please review the Android device steps below if there are any issues. If you do not find the solution below, please reference the wireless device's manufacturer guidelines to understand how to enable this feature for your device.As a reminder, USB Tethering is not available for iPhone at this time, and the steps below are for a typical Android device/phone. Connect the Infiot Device and Wireless Interface Device via a USB cable. It is strongly recommended to use the same USB cable that came with the wireless device.Either one of the two USB ports on the Infiot device can be used for USB Tethering. From an Android Wireless Device, go to "Settings."Find and select "Connections."Find and select "Mobile Hotspot and Tethering."From this menu, enable Mobile Hotspot" and "USB Tethering."The option for "USB Tethering" may not become available until the device is connected via USB.You can check the status of this interface from the Infiot Web Interface by going to Edges → [Your Edge Device]. Please allow 2-5 minutes before this feature will show active (blue ring), as seen below.USB Interface Failover VerificationOnce the USB Interface Failover settings have been enabled on both the Infiot Device and the Wireless Interface Device, there are a couple of ways to check that this feature is working correctly. To begin, you will need to simulate a failover environment by disconnecting the WAN in the middle of an active phone call by completing the steps below. While connected to the primary interface, place an outbound call.While the call is still connected, disconnect the ethernet cable that is plugged into the WAN port of the Infiot Device.Once disconnected, the call should remain active, meaning the wireless interface device is now being used to stay connected.Once this process is complete, you can go into the Infiot Web Interface to verify further by completing the following steps:Go to "Edges" and select your Infiot Device.From here, select "Devices" and locate the phone used to make the initial outbound call.You can locate the device by name or the WiFi MAC Address.You can expand the list to see more devices by utilizing the "Items per page" option at the bottom of the page. Under the "FLOWS #" column, click the number displayed to the far right of the device name.Once selected, scroll to the bottom of the page to see all flows for this device. You should see at least one entry that shows "LAN to USB0," as seen below.This information confirms the connection flow was originally LAN to WAN, and when the WAN becomes unavailable, the flow changes to "LAN to USB0," the Wireless Interface Device.