Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Network Interfaces for kLWC

kLWC is deployed with three network interfaces: internal, external, and management. Each interface serves a distinct purpose to ensure secure data collection, communication, and system access.

Table 1: Network Interface for kLWC
Interface Interface Name Description
Internal int Internal network used to access the Junos devices being monitored by JSI.

This interface must have connectivity to internal Junos devices and must not have Internet access.
External ext External network interface with HTTP/HTTPS and DNS Internet connectivity.

This interface is used to connect to Juniper Cloud, either directly or through an active proxy server.

Management cap

Management network used to access the kLWC system through the JSI shell or the Captive Portal web page for configuration and troubleshooting.

Port requirements:

  • Port 443/HTTPS for the Captive Portal webpage

  • Port 22/SSH for the JSI shell

Note:
  • Proper network segmentation is recommended to maintain security between internal, external, and management traffic.
  • Ensure firewall rules allow required communication across each of the interfaces.