Cato Networks Knowledge Base

Remotely Pinging the Socket WAN Interface

You can configure specific sites or the entire account to allow admins to ping the Socket WAN interfaces from any remote location. To enable this feature on your account, please contact Cato Support.

 

Note: This feature is only supported on Cato Sockets version 7.1 and higher.

Contacting Support to Configure Remote Ping

For EA, the remote ping feature is controlled by a back-end configuration. You must give the IP addresses or IP ranges for the ACL to allow those remote locations to ping the WAN interfaces.

To configure this feature, contact Cato Support and give them the following information:

  • For the entire account, IP addresses or IP ranges (CIDR format) for the remote ping ACL
  • For specific sites, for each site:
    • Name of the site
    • IP addresses or IP ranges (CIDR format) for the remote ping site ACL

If both a site and the account are configured for remote ping, then the settings for the site override the settings for the account.

Showing the WAN IP Address

Use the Socket WebUI to show the IP address for each WAN interface. You can then ping the interface using this IP address. You need the gateway IP address of the site to connect to the Socket WebUI.

To show the Socket IP address for a WAN interface:

  1. Show the IP address for the Native Range Gateway to connect to the Socket WebUI:
    1. From the Cato Management Application, click Configuration > Sites and select the Socket site.
    2. Expand the Networks section, and locate the row for the Native Range.
    3. In the Characteristics column, the Gateway setting shows the IP address for the Socket WebUI.

  2. Log in to the Socket WebUI - from an Internet browser, enter this URL: https://[Cato Socket IP address]. For example, https://192.0.2.2
  3. Enter the login credentials for the Socket WebUI.
  4. Click the Network Settings tab.

    The window shows the public IP address for each interface.

Pinging the WAN Interface - Public or Private IP Address

When you ping the WAN interface, the options are different depending on whether it has a public or private IP address. You can ping an interface with a public IP address from any remote location over the Internet.

For interfaces with a private IP address, you can ping the interface from another private IP address on the same subnet. You can also configure the router for that site to allow ping requests from remote locations.

Pinging an Interface with a Public IP Address

WAN interfaces on a Socket with a public IP address allow ping requests over the Internet. Use the Socket WebUI (see above, Showing the WAN IP Address) to identify the public IP address for each WAN interface.

Pinging an Interface with a Private IP Address

By default, WAN interfaces on a Socket with a private IP address only allow ping requests from an IP address on the same subnet. You can't ping the interfaces from remote locations.

For Sockets that are behind a NAT device, some routers support adding the ICMP forwarding rule to allow ping requests to the private IP address for the interface.

Use the Socket WebUI (see above, Showing the WAN IP Address) to identify the private IP address for each WAN interface.

Was this article helpful?

2 out of 2 found this helpful

Comments

0 comments

Please sign in to leave a comment.