2.3.1 Top Banner

The top banner area, which is consistently displayed on every navigation page, will show the current Network mode and cellular signal strength information towards the top right area.

Figure 18: Mission Control – top banner shows Network Mode and Signal Strength.

• Network Mode: NAT (default) or Passthrough.
• Signal Strength: The number of cellular signal strength bars, which should match up with the bars on the device LCD Display screen.

2.3.2 Navigation Pane

The navigation pane on the left consists of a two-level menu system:

Figure 19: Mission Control Navigation Pane – Overview menu structure.

a: In the main Overview page, the Top-level menu section consists of four on-page topics: Device, Networking, System Settings, and Logout.

b: If any, the second-level sub-menu contains on-page quick links. For example, Figure 19 shows the top-level Networking menu item with its second-level submenu items of DHCP Leases and Interfaces. Clicking on any of those options will take you to that area of the current Top-level selection.

c: Selecting the 'Logout' option will log you out of Mission Control. When the user navigates into Expert Configuration mode by clicking on the 'Expert Configuration' button, located in the System Settings under Admin Tools, the navigation pane on the left exposes different selectable options and lands the user inside the 'General' page (Second-level page) under 'Status' (Top-level menu).

Figure 20: Mission Control Navigation Pane – Expert Configuration mode menu structure.

d: There is a link back to the main Overview page at the top. Click on it to go back to the main Overview page.

e: The Top-level menu section consists of four new topics with links to different pages under each: Status, System, Network, and Logout.

f: If any, the second-level sub-menu in this area contains a variable number of page links. For example, Figure 20 shows the top-level Status menu item with its second-level sub page links to General, Routing, Firewall, System Log, Processes, Channel Analysis, etc. Clicking on any of those page link options will take you to that page of the current Top-level selection.

g: Selecting the 'Logout' option will log you out of Mission Control.

2.4.1 Save Options

Within Mission Control, all changes and saves must be applied manually; there are no automatic save or apply options. Typically, there are three save options: Save, Save & Apply, and Apply Unchecked; plus, non-save options such as Reset, Dismiss, Revert, etc.

Figure 21: Mission Control – Save options buttons are displayed.

The action buttons you see will depend on where you are in the system and what changes you have made. We will look at these in more detail below, starting with Save.

Figure 22: Mission Control – Save options buttons are displayed again.

2.4.2 Save

Though the Overview page presents most of the basic admin functionality in a single scrolling page, you may need to navigate between, and make changes to, multiple pages within Mission Control itself. The 'Save' button allows you to save your changes as you go. In contrast, without this save option, if you navigated away from a page without saving your changes, these would then be discarded and lost, and current applied settings and values would remain unchanged. However, it is important to note that saving changes does not apply/commit them to the system (i.e., no updates occur as a result of saving changes). Instead, saving any changes adds them as pending to the 'Unapplied Changes' list as shown below.

Figure 23: Navigation pane showing pending 'Unapplied Changes' count.

Once saved as Unapplied Changes, you can then:

• Carry out additional work on the current page or navigate away to a different page and continue your tasks until you are ready to apply all changes.
• Manage your unapplied changes.
• Save and apply your unapplied changes.

2.4.3 Managing Unapplied Changes

To view or manage your unapplied changes:

1. Click on the 'Unapplied Changes' button and the 'Configuration/Changes' dialog will show, listing all queued changes. Also, the status of each item is indicated by its color, per the legend.
2. From here, you have several buttons: Close, Save & Apply (Apply unchecked is in the dropdown menu), and Revert or Reset.

   Figure 24: Configuration/Changes dialog showing button options: Close, Save & Apply, Revert/Reset.

• Close: Will close this dialog window.
• Save & Apply: Will apply the changes, clear the Configuration/Changes list, close the dialog window, and you will then see the 'Apply configuration changes' countdown popup.

  Unlike performing a Save & Apply from the main dashboard, because these items have already been saved once (the initial save added them to the unapplied changes queue), no second click is required to initiate these changes. A single click on the Save & Apply button will commit all changes and the countdown will commence.

• Revert/Reset: Will cancel all unapplied changes, clear the list of any pending changes, and displays the 'changes have been reverted' message as a popup, and then takes you back to the Mission Control dashboard where all settings remain unchanged.

2.4.4 Save & Apply

When you are ready to apply your unapplied changes, click on 'Save & Apply'. This will then apply all unapplied changes to the system and update your current configuration.

IMPORTANT: Please allow adequate time for changes to update and ensure continuous power is supplied to the MegaFi 2 during any updates.

2.4.5 Apply Unchecked

When updating certain attributes, such as the LAN IP address or other configurations, there is often a time delay between events (e.g., a change in the LAN IP that uses DHCP) so there may be a delay between connecting to the new IP and subsequent assignment of new DHCP addresses. In such cases, the system will attempt to check that both communication and function are maintained. However, if, during this check, the system determines that either would be lost because of the change, it will trigger the 'Configuration has been rolled back!' alert. 'Apply unchecked' allows us to avert this by applying pending changes without performing communication and function checks.

1. Click on the 'Save & Apply' button arrow and the popup will open.
2. Click on 'Apply unchecked' and the dropdown will close, the button label will change to 'Apply unchecked', and the button color will change to red.

   Figure 25: Configuration/Changes dialog showing the 'Apply unchecked' option selected.

3. A second click, on the now 'Apply unchecked' button, will apply the changes and the 'Applying configuration changes' countdown will initiate.

2.4.6 Reset or Revert

Clicking on 'Reset' or 'Revert' will cancel all unapplied changes, clear this list, return on-page settings to their current values, and leave the current settings and configuration in their present state.

2.4.7 Overview Page

As previously pointed out above, the top-level menu, the user can see direct links to Device, Networking, System Settings all listed in the left-hand pane and detailed information and statistics for each of these pages within the main window. The 'Logout' button function is also listed at the bottom.

Figure 26: Mission Control – Overview page showing navigation and main content areas.

The user may need to scroll down the main window to see all that is presented under Overview. Each of these areas are detailed below.

3.1 Changing APN (Access Point Name)

By default, the APN (Access Point Name) will automatically detect and configure itself when a firstnet-broadband or an Enterprise (broadband) SIM is installed. If the user has a custom APN SIM card, do the following to manually change the APN in Mission Control:

1. Navigate to Overview > System Settings under Admin Tools.
2. Click the drop-down menu next to 'Override APN' and select 'On'.
3. Click on the 'Save & Apply' button at the bottom to confirm the change.

   Figure 32: System Settings – 'Override APN' setting is enabled.

4. Now click the drop-down menu next to 'APN (Access Point Name)' and click inside the custom field.
5. Correctly type in the APN name associated to the SIM card into the custom field and hit Enter. Otherwise, it will revert back to its default setting, or pre-configured APN.
6. Click on the 'Save & Apply' button at the bottom to confirm the change.

   Figure 33: System Settings – APN (Access Point Name) field is updated with a custom APN.

7. Give the device a few minutes to successfully regain network connectivity.
8. After the device becomes available, issue a Reboot so the device receives the correct IP address and any other provisioned network settings. See Section 3.9 for Reboot procedure.
9. To validate the custom IP address associated to your custom APN, navigate to Overview > Networking and verify the WWAN IPv4 address under Interfaces and make sure it is correct.

   Figure 34: Networking – WWAN IPv4 Address is displayed, showing the assigned IP for the custom APN.

3.2 Changing LAN IP Address

By default, the LAN IP address is set to 192.168.113.1. If the user needs to configure this setting to fit their network environment, do the following to make the change in Mission Control:

In this environment, the system automatically sets a /24 or Class C network and will provide IP addresses to devices within this range.

1. Navigate to Overview > System Settings under Admin Tools.
2. In the 'LAN IP' field, click on the drop-down arrow and click inside the custom field.

   Figure 35: System Settings – Changing LAN IP Address field is shown.

3. Enter the new IP address in the field and hit Enter. Otherwise, it will revert back to its default setting, or pre-configured IP address.
4. After clicking on Enter above, a popup window will warn the user that the system will be temporarily unreachable and that a manual reconfiguration of the URL address in the web browser address bar will be required to regain access to the device as soon as the change is committed.

   Figure 36: LAN IP address warning popup indicates temporary unreachability.

5. Click on 'Save & Apply' to confirm change.
6. A 'Connectivity change' popup message will appear, warning the user that current access to the device will be interrupted if the user proceeds. The user is given options to either Cancel, Apply with revert after connectivity loss, or Apply and keep settings.
• Cancel: Will not proceed with committing the change but will keep unapplied changes pending and take the user back to step 5.
• Apply with revert after connectivity loss: Will begin to commit the change but the user will have 90 seconds to regain access to the device using the new IP address. Otherwise, the setting will automatically revert to the previous setting. Another popup window ('Configuration changes have been rolled back!') will ask the user to select Dismiss, Revert changes, or Apply unchecked.
  • Dismiss: will dismiss this popup window and take the user back to step 5.
  • Revert changes: will revert changes and take the user back to step 2.
  • Apply unchecked: will commit the change. Skip to step 7.

    Figure 38: 'Configuration changes have rolled back!' popup message with options.

• Apply and keep settings: Will commit the change.
7. Give the device a few minutes to successfully regain network connectivity and before attempting to reconnect to MegaFi 2 via Mission Control or SSH.

   After proceeding with the LAN IP change, the user will need to retype the new IP address in the web browser address bar to regain access to the device.

3.3 Flash/Update Firmware

The user can either use Mission Control or MegaPortal (Nextivity's Cloud portal for MegaFi 2), to update MegaFi 2's firmware.

Firmware updates for MegaFi 2 are primarily only supported via MegaPortal. By default, the device is set to automatically update its firmware whenever there is a new version available in the cloud. This feature does not necessarily auto-update the device, but it acknowledges a new update is available and requires some user intervention to carry out the update. To update the device using MegaPortal, please refer to the MegaPortal User Guide.

For special needs or requirements, and only with the assistance of Nextivity Support, a user may update the firmware via Mission Control. To manually update the firmware for MegaFi 2 via Mission Control, the firmware version-specific BIN file needs to be obtained from Nextivity Support.

If the user requires an immediate update, do the following to update the device in Mission Control.

Assumption: The user has obtained the appropriate firmware (BIN file) from Nextivity Support, it is loaded on a computer workstation or laptop, and it is directly connected to a LAN port on MegaFi 2 or via its Wi-Fi connection.

Uploading an incorrect file can render your device inoperable and may void warranty.

1. Navigate to Overview > System Settings under Admin Tools.
2. Click on the 'Upload Firmware' or 'Flash image' button next to 'Update Firmware'.

   Figure 39: Firmware update – 'Upload Firmware' button is highlighted.

3. On the pop-up 'Uploading file...' window, click on 'Browse' to locate the firmware file.

   Figure 40: Uploading file... – 'Browse' button to select the firmware file.

4. The firmware file should be the BIN type file, and, depending on the firmware version, around 40 MB.

   Figure 41: Firmware update – Example of selecting the upgrade file.

5. Select the firmware file. The 'Uploading file...' window now shows the selected file.

   Figure 42: Firmware update – Uploading the selected upgrade file is shown.

6. Click on 'Upload', and the file will begin to upload.

   Figure 43: Firmware update – Status of upgrade file upload progress.

7. A new pop-up window 'Flash image?' will ask the user to manually verify the checksum SHA256 value displayed here, with the checksum SHA256 value displayed next to the firmware file from where it was downloaded. Only continue if the values match.

   The SHA256 value is unique to each version. In this example, this is the SHA256 value for firmware version 3.1.6.8.

   Figure 44: Flash image window – prompts to compare checksum and file size with the original.

WARNING: If you accidentally try to upload the wrong file to the MegaFi 2 device, a warning screen will be displayed. If this happens, STOP - DO NOT PROCEED. Select 'Cancel' to back out of this operation and avoid "bricking" your device.

Figure 45: Flash image window – 'Image format check failure' warning example.

8. Click on 'Continue' on 'Flash image?' only after the SHA256 values have been verified to match.
9. The 'Flashing...' window will display.

   Do not power off the unit until the image flashing is complete.

   The update will take 3-5 minutes.

   Figure 46: Flashing window – message indicating progress of the system flashing process.

10. When the image flash is complete, you will be taken back to the login page.
11. Log in to continue.
• Current status may initially display 'No Internet' and no signal strength bars. It will correct itself once the device properly boots up from the upgrade process.
• Refresh the browser if the device has not gone back to the home screen after 10 minutes and re-login again.
12. Verify that the intended firmware upgrade successfully loaded by looking at the bottom right of any Mission Control page. Once verified, the firmware update is complete.

    Figure 47: Mission Control page showing Firmware Version information.

3.4 Backup Existing Configuration

If the user wants to back up an existing configuration, do the following in Mission Control:

1. Navigate to Overview > System Settings under Admin Tools.
2. Click on the 'Save to File' button next to 'Backup Existing Configuration'.

   Figure 48: System Settings – 'Save to File' button for backup.

3. A tar.gz (tarball) file is created and stored in Downloads. Take note of the date of the file for future reference if needed.

   Figure 49: Downloads folder showing a downloaded tar.gz file, representing the configuration backup.

3.5 Load Configuration from File

If the user wants to load a backup/saved configuration (i.e., duplicate a configuration file onto other MegaFi 2 devices or restore a previous configuration file), do the following in Mission Control:

The backup configuration file will bring over the previous password, its Wi-Fi settings, and all other configuration settings from that MegaFi 2 device it was created from. Make sure to have a copy of the password and Wi-Fi settings including SSID names and keys if needed.

1. Navigate to Overview > System Settings under Admin Tools.
2. Click on the 'Load File' button, sometimes referred to as 'Upload archive...', next to 'Load Configuration from File'.

   Figure 50: System Settings – 'Load File' button for restoring configuration.

3. The 'Uploading file...' window pops up, select 'Browse' to locate the appropriate tarball file and click 'Open'.

   Figure 51: Uploading file – 'Browse' button to locate the configuration file.

   Figure 52: Uploading file and Browse to and select the tarball file interface.

4. The 'Uploading file...' pop-up window shows the file chosen to load. Verify it is the intended file before selecting 'Upload' to continue with loading the file.

   Figure 53: Load Configuration from File – Uploading selected file confirmation.

5. In the 'Apply backup?' pop up window, press 'Continue' at the bottom to proceed with restoring the backup file and reboot. Otherwise, click 'Cancel' to abort the operation.

   Figure 54: Apply backup – Confirmation dialog to continue with restoring the backup.

6. Give the backup operation 3-5 minutes to finish as it reboots.

   Do not power off the device during this time.

3.6 Change Password

If the user requires to change the current password, do the following in Mission Control.

1. Navigate to Overview > System Settings under Admin Tools.
2. Click on the 'Change Password' button next to 'Change Password'.

   Figure 55: System Settings – 'Change Password' button.

3. The user is automatically put into Expert Configuration Mode and taken to the System > Router Password page.

   Figure 56: Router Password page – Expert Configuration Mode, showing password fields.

4. Enter a new password in the 'Password' field and re-type it in the 'Confirmation' field as well.

   The device will not accept weak passwords. Password must meet the following requirements: a minimum length of 10 characters and a randomized complexity of lowercase letters, uppercase letters, and numbers.

   Figure 57: Router Password page – Enter new password and confirmation fields.

5. Click on the 'Save' button.
6. Once the change is confirmed by the device, the user will be put back in the Overview page.

3.7 Factory Defaults via Mission Control

If the user wants to return to factory default settings, the user can perform a factory reset to the MegaFi 2 device in Mission Control as follows:

After a factory reset, the MegaFi 2's UUID may need to be reassigned for Cloud support. If cloud access breaks after a factory reset, contact the support team at support@nextivityinc.com for further assistance.

1. Navigate to Overview > System Settings under Admin Tools.
2. Click on the 'Factory Defaults' button next to 'Factory Defaults'.

   Figure 58: System Settings – 'Factory Defaults' button.

3. A window will pop up and ask the user to confirm the operation. Click 'OK' to continue.

   Figure 59: Confirmation dialog to return settings back to factory defaults.

4. Give the device 3-5 minutes to complete the operation.
5. Once the device recovers, the user will be asked to log in to Mission Control again, using the default password located on the device's label or from the LCD display screen.
6. The user will then be asked to accept the EULA agreement and change the default password.

To factory default the MegaFi 2 using the DISPLAY button (in case of a forgotten password), press and hold the DISPLAY button for 20 seconds and release. The device will take a few minutes to recover, and all settings will now be set to factory default.

3.8 Vehicle Shutdown Delay

If the MegaFi 2 device is installed in a vehicle, the user can increase the 'Vehicle Shutdown Delay' setting up to 2 hours. The default setting is 30 seconds. This ensures that the MegaFi 2 device will stay powered on after the vehicle is shut off and it will continue to provide services until the timer expires. To change this setting, do the following in Mission Control:

1. Navigate to Overview > System Settings under Admin Tools.
2. Click the drop-down arrow to expose the other pre-defined settings and select from 15 minutes, 1 Hour, or 2 Hours.

   Figure 60: System Settings – 'Vehicle Shutdown Delay' options are displayed.

3. Click on 'Save & Apply' to confirm the new setting.

3.9 Reboot

If the user would like to reboot the MegaFi 2, do the following in Mission Control.

1. Navigate to Overview > System Settings under Admin Tools.
2. Click on the 'Reboot' button.

   Figure 61: System Settings – 'Reboot' button.

3. A pop-up window asks the user to confirm the operation. Click on 'OK' to continue.

   Figure 62: Confirmation message to reboot the device.

4. Wait for the device to reboot before continuing. The process will take 1 - 5 minutes.

   Figure 63: Message indicating the device is being rebooted.

5. The user will be asked to log in again into Mission Control after the device reboots. Click on the 'To login...' button to do so.

   Figure 64: Prompt to log in after the device reboots.

3.10 Wi-Fi Settings

To verify or change current Wi-Fi settings, do the following in Mission Control:

3.11 NAT vs. Passthrough Mode

The MegaFi 2 device can be set to either NAT (default setting) or Passthrough Mode. In NAT Mode, the device acts as an intermediary between a local network and the internet, translating private IP addresses into a single public IP address. This helps enhance security by hiding internal devices from external networks and allows multiple devices to share a single public IP. Passthrough Mode disables NAT, meaning the device does not modify IP addresses. It simply forwards traffic as-is, allowing a connected device (such as a firewall or router) to handle public IP assignments. Passthrough is often used when another device downstream is managing the network. Also, in Passthrough Mode, the carrier assigned IP address will be shared with the device directly connected behind the MegaFi 2 on the LAN 1 port. In some cases, computers with specific software will require this IP and can be the recipient of the passed through IP address.

Prior to implementing Passthrough Mode, the user needs to take the following steps:

• Connection to MegaFi 2 Device: The user will need to connect a computer workstation or laptop with an Ethernet cable to LAN port 1. The user will also need to make sure the computer is NOT connected to Wi-Fi.

  Only LAN port 1 is usable and all other LAN ports are disabled in Passthrough Mode.

• Implement Custom APN/Static IP first: Though not always the case, if the user is using a custom APN, the user will need to input the custom APN (Section 3.1) first prior to implementing Passthrough Mode. If the correct IP address does not appear on the device, please review SIM provisioning with the carrier. If the correct IP address does appear, then the user may proceed with implementing Passthrough Mode as instructed below.
• Manually refresh the connected computer IP address: Once in Passthrough Mode, the Mission Control software management interface will briefly be unreachable at https://192.168.113.1 or whatever LAN IP address it has been configured to until the IP address is manually refreshed. If this occurs, go to Step 11 below for options to try to regain connection to Mission Control.

To change between NAT and Passthrough modes, do the following in Mission Control:

1. Navigate to Overview > System Settings under Admin Tools.
2. Click on the 'Expert Configuration' button to enter Expert Configuration mode.

   Figure 72: System Settings – Entering Expert Configuration mode.

3. A pop-up window asks the user to confirm going into Expert Configuration mode. Click 'OK' to continue.

   Figure 73: Confirmation message to enter Expert Configuration mode.

4. The left-pane menu exposes pages only available in Expert Configuration mode. Navigate to System > Configuration.

   Figure 74: Navigation pane showing options available in Expert mode – 'Configuration' under 'System'.

5. Under the 'Networking' area, click on the drop-down arrow and select the desired mode: 'NAT Mode' (default), or 'Passthrough Mode' from the 'Passthrough vs NAT (changing causes reboot)' option.

   Figure 75: MegaFi 2 Configuration – Change modes (NAT or Passthrough) option.

6. A pop-up window will warn the user that temporary access to Mission Control will be lost after committing to the mode change. After committing to the mode change, the user will have the option to restore the default configuration by holding the Reset button for 30 seconds if they don't wish to continue with the mode change. Click 'OK' to continue with the mode change.

   Figure 76: MegaFi 2 Configuration – Change modes (NAT or Passthrough) confirmation warning.

7. Click on 'Save & Apply' to confirm the change.

   Internet access, wireless connectivity and/or access to the MegaFi 2 will become disrupted or unavailable after committing the mode change. Please allow 1-3 minutes for the configuration to apply.

8. Once Mission Control access is re-established, login again to Mission Control.
9. It is highly recommended to issue a Reboot (Section 3.9) to make sure the new setting takes hold. Please proceed with a Reboot at this time.
10. If the MegaFi 2 is set to Passthrough Mode, and the desired device, such as a firewall or router or a different computer with special software is to be connected to LAN port 1 on MegaFi 2 other than the computer used to implement the mode change, follow these added steps:
• Power down both the MegaFi 2 and the device that will interconnect with each other.
• Using an Ethernet patch cable, interconnect the MegaFi 2 LAN port 1 interface and the device's WAN port. If the device is another computer, connect to its Ethernet port.
• Power up both devices.
• Ensure that the connected device receives the appropriate IP address. Follow instructions from the device manufacturer to validate the IP address.
11. If connectivity becomes an issue to Mission Control, try one of the following actions to regain access to MegaFi 2:
• Refresh the web browser to Mission Control.
• Connect an Ethernet cable to an enabled LAN port (LAN port 1 if in Passthrough mode) on the MegaFi 2 and re-access Mission Control as usual through a web browser.
• Manually refresh connected computer IP address by opening a Windows PowerShell, or Command Prompt window on a PC with local access to MegaFi 2 and enter the following commands at the prompt:
• ipconfig /release <enter> – this will release the existing IP addresses

  Figure 77: Windows PowerShell window – 'ipconfig /release' command.

• ipconfig /renew <enter> – this will refresh the IP addresses on the connected computer.

  Figure 78: Windows PowerShell window – 'ipconfig /renew' command.

12. When changes have been completed, and to prevent any more setting changes, click on the 'Logout' button to exit out of Mission Control and be taken back to the Log In page.

3.12 Band Lock

In certain situations, the user may need to Band Lock to band 14. To do so, do the following in Mission Control:

Before committing to this change, please make sure to validate that band 14 is available in your area as not all areas are equipped for band 14.

1. Navigate to Overview > System Settings under Admin Tools.
2. Click on the 'Expert Configuration' button to enter Expert Configuration mode.

   Figure 79: System Settings – 'Expert Configuration' button.

3. A pop-up window asks the user to confirm going into Expert Configuration mode. Click 'OK' to continue.

   Figure 80: Confirmation to Enter Expert Configuration mode.

4. The left-pane menu exposes pages only available in Expert Configuration mode. Navigate to System > Configuration.

   Figure 81: Navigation pane showing options available in Expert mode – 'Configuration' under 'System'.

5. Under the 'Other' area, use the drop-down arrow next to 'Band Lock' to select 'LTE B14 Only'. Choose the 'Default Band Configuration' option to set back to default setting in which the device relies on the Network to choose the appropriate band.

   Figure 82: Band Lock Setting dropdown menu.

6. Click on 'Save & Apply' to confirm the change.
7. When changes have been completed, and to prevent any more setting changes, click on the 'Logout' button to exit out of Mission Control and be taken back to the Log In page.

3.13 SSH Access

The user-enabled SSH instance (Dropbear) offers SSH network shell access and an integrated SCP server. Access to SSH on the MegaFi 2 is turned off by default. To enable command line SSH Access to the device, do the following in Mission Control.

1. Navigate to Overview > System Settings under Admin Tools.
2. Click on the 'Expert Configuration' button to enter Expert Configuration mode.

   Figure 83: System Settings – 'Expert Configuration' button.

3. A pop-up window asks the user to confirm going into Expert Mode. Click 'OK' to continue.

   Figure 84: Confirmation to Enter Expert Configuration mode.

4. The left-pane menu exposes pages only available in Expert Mode. Navigate to System > Router Password > SSH Access.

   Figure 85: SSH Access page – 'Add instance' button.

5. Click on the 'Add instance' button.
6. The 'Interface' field will be pre-populated with the LAN interface by default and is the only option when needing local access to the device. The other options in the dropdown menu are wan, wan6, and wwan when remote SSH Access is required.
7. In the 'Port' field, change the port number from the default 2022 to 22 (well-known SSH port for local access) or another port of your choosing that is not being used and hard for hackers to guess (typical for SSH wan access).
8. 'Idle Timeout' is set to 300 seconds by default. Adjust for more or less time in seconds as needed.
9. All other settings are not required and are optional.
10. Click on 'Save & Apply' to confirm changes.

    Figure 86: SSH Access – Change port number from 2022 to 22 example.

11. Use your preferred SSH client to access MegaFi 2 on port 22 or whatever port configured and use 'root' as the username along with the current router password.

    The SSH password will be the same as the Router Password.

12. Optional: If remote SSH Access to the device is required and the device has a custom static/public IP address, do the following to open the appropriate wan interface:
• Within the SSH Access page, click on 'Add instance'.
• Choose the appropriate wan interface from the 'Interface' drop-down menu.
  • wwan – most typical choice to access SSH from the cellular network
  • wan – only select if the device has internet connection through wan port
  • wan6 – currently not widely used
• Choose a port such as 46556 or something similar that is not the typical SSH port 22.
• It is recommended to leave the 'Idle Timeout' set to 300 or less for wan access for security reasons.
• All other settings are not required and are optional.
• Click on 'Save & Apply' to confirm changes.

3.14 GPS Output Configuration

This is where the user can configure GPS settings on MegaFi 2 for a GPS Server, GPS Internal Reporting, and GPS Output in Mission Control.

• GPS Server: This option provides GPS data to applications or clients that request it using a predefined server port.
• GPS Internal Reporting: This is how the MegaFi 2 will process GPS data and display it on-device only. The user can choose the format and the optional NMEA station code or TAIP ID and Rate. The default format setting is NMEA.
• GPS Output: This most widely used option transmits or shares GPS data to other systems using a host's IP address, a port number, a defined format (NMEA or TAIP), and a TCP/IP connection method using UDP as the protocol of choice. NMEA station code or TAIP ID and Rate are other options available in this area.

Figure 87: GPS Output Configuration page overview.

3.15 WAN/LAN Port Mode

The MegaFi 2 has two physical Ethernet ports. By default, the left port labeled WAN/LAN2 is set to WAN mode. It can be set to function as a second LAN port if desired. To change the port mode on this port, do the following in Mission Control.

1. Navigate to Overview > System Settings under Admin Tools.
2. Click on the drop-down menu next to 'WAN/LAN Port Mode' and select 'LAN'.

   Figure 100: WAN/LAN Port Mode options dropdown.

3. Click on 'Save & Apply' to confirm the WAN/LAN Port Mode setting.

The MegaFi 2 is capable of receiving PoE (Power over Ethernet) through the WAN/LAN2 port. Check the MegaFi 2 User Guide for specifications.

3.16 LCD Configuration

The MegaFi 2 LCD display screen can be configured for the following settings:

Table 2: LCD Screen Settings.

To make any changes to the LCD Display screen, do the following in Mission Control.

1. Navigate to Overview > System Settings under Admin Tools.
2. Click on the 'Expert Configuration' button to enter Expert Configuration mode.

   Figure 104: System Settings – 'Expert Configuration' button.

3. A pop-up window asks the user to confirm going into Expert Configuration mode. Click 'OK' to continue.

   Figure 105: Confirmation to Enter Expert Configuration mode.

4. The left-pane menu exposes pages only available in Expert Configuration mode. Navigate to System > Configuration > LCD Configuration.

   Figure 106: LCD Configuration – default settings interface.

5. For settings with a drop-down menu arrow, click the arrow and choose the preferred setting.
• Screen Orientation: select from Portrait (default) or Landscape
• Detail Level: select from Full (default) or Minimal
• Turn off screen after (seconds): select from 600 (default), Always off, Always on, or enter a custom value in seconds between -1 and 3600.
6. To modify 'Switch screen information (seconds)', remove or delete the previous setting (default is set to 15) and enter a new setting between 1 and 60 in this field, and hit Enter. Otherwise, it will revert back to its default setting, or pre-configured setting.
7. Click on 'Save & Apply' to confirm the change(s).