Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Configure Network Settings through JSI Shell

This section provides information on the JSI Shell.

JSI Shell Overview

The JSI Shell is an SSH menu system for the kLWC. It allows you to view the current network settings and network status through an SSH login. You can use the JSI Shell as an alternate option to configure network settings. You can interact with the JSI Shell menu system through the keyboard. See Table 1.

Table 1: Keyboard Navigation
Key Action
Up and Down arrow keys, or number press Navigate to an option.
Enter key Select the option.
Esc key Go back to the previous menu or exit the shell depending on what menu you are currently in.

Login to JSI Shell

To access the JSI Shell, SSH to the configured IP address of the management (cap) interface.

On successful login, the kLWC Main Menu screen in JSI Shell appears.

Change JSI Shell Login Password

You can change the login password for jsiuser from the JSI Shell Main Menu screen. To change the password, select Change password for jsiuser from the kLWC Main Menu screen (using the arrow key or pressing 6 on the keyboard), press Enter, and follow the prompts to specify the new password.

Configure Network Settings

You can configure the following network settings from the JSI Shell:

  • Interfaces—Internal (int), External (ext), Management (cap)

    Note:

    While configuring the internal, external, and management interfaces, you must ensure that the subnet of the IP address assigned to the internal network port, external network port, and captive portal are different from each other.
    Note:

    You must connect to the captive portal from a local IP address. Connection to the captive portal from the browser will fail if the connection request originates from a non-local network.

  • Active proxy

Follow the steps below to configure the network settings:

  1. Login to the kLWC Main Menu (JSI Shell). See Login to JSI Shell.
  2. Select Edit Network Settings (using the arrow key or pressing 3 on the keyboard) from the kLWC Main Menu screen.
    The kLWC Edit Network Settings Menu screen appears.
  3. To change the various interface settings:
    1. Select the interface you want to edit (options one to three) from the kLWC Edit Network Settings Menu screen.
    2. Select the appropriate options from the series of menus presented after which a kLWC Edit interface Settings Menu screen appears for the interface you selected.
      The upper half of the display lists the current network settings.
    3. Use the options displayed in the bottom half of the display to modify the network settings. You can select an appropriate option and configure the new value when the prompt appears.
      The updated values will appear in the upper half of the display.
    4. Once you have made all the changes, select Apply pending changes and return to network settings to apply your changes.
      Note:

      You can exit the settings from one interface and work on another interface without losing your changes. You can then apply all changes at the same time.

  4. To change the active proxy settings:
    1. Select Change active proxy (using the arrow key or pressing 4 on the keyboard) from the kLWC Edit Network Settings Menu screen.
      The kLWC Edit Active Proxy Settings Menu screen appears. The upper half of the display lists the current active proxy settings.
    2. You can enable or disable the active proxy (option 1), or configure the active proxy settings from the kLWC Edit Active Proxy Settings Menu screen.
    Note:

    The kLWC's external interface must be able to reach the URL, or IP address and port used for the active proxy.
    Note:

    If you choose to use an active proxy, ensure that it forwards all the traffic from the kLWC to the AWS cloud proxy (see Outbound Connectivity Requirements for information on the AWS cloud proxy URL and ports). Juniper cloud services blocks all the inbound traffic coming through any path other than the AWS cloud proxy.
Note:

After applying changes, if the network does not work as intended, reboot the kLWC.