Show VPN Tunnels

[Danny]

👉 Available as CLI script

SmartConsole Extension to show all VPN Site-to-Site tunnels on gateways. SMB appliances use the CLI script.

Extension URL: https://dannyjung.de/vpntu.json

[Norbert_Bohusch]

Hi Danny,

nice extension and it's working perfectly in my tests.

Unfortunately because of the lack of support for run-script with Virtual Systems it's currently working only for customers with standard gateways.

Thanks

Norbert

[Danny]

@Norbert_Bohusch : I added support for Virtual Systems that are within the same domain as the VSX host.

[Norbert_Bohusch]

@Danny nice, but in my tests it didn't work (mgmt and vsx cluster both R82).

It fails in the task with:

Connection failed for <IP of VS>
Make sure that the machine is up and running, and that SIC has been established

I then checked logs and so the DMS trying to communicate with the VS over CPD port 18191, which I then allowed. But still not working.

Any idea what the problem could be?

[Henrik_Noerr1]

We have a SR 6-0004538755 running as all "run-script" api commands to our DMS fails after the autoupdater updated the api above t11 on gateways we have.

[Expert@testgw:0]# autoupdatercli s ender_gaia_api

product-name: gaia_api

component-name: ender_gaia_api
component-branch: gaia_api_AutoUpdate
GA-Version: 0
download-scheduler-active: true
install-scheduler-active: true
download-action: idle
install-revert-action: idle

installation-date: 2025-08-18_12:43:59
package-branch-name: gaia_api_AutoUpdate
package-version: 9
package-name: Check_Point_GAIA_API_AUTOUPDATE_Bundle_T9_FULL.tgz
package-installed: false
package-installable: true
package-previously-installed: true

installation-date: 2026-03-04_12:29:34
package-branch-name: gaia_api_AutoUpdate
package-version: 11
package-name: Check_Point_GAIA_API_AUTOUPDATE_Bundle_T11_FULL.tgz
package-installed: true
package-installable: true
package-previously-installed: false

[Expert@testgw:0]#

issue is solved when reverting to T9 (API version 1.8)

[Danny]

@Norbert_Bohusch: The reason is that your VSX host is in a different domain than your VS system. SmartConsole therefore can't identify your VSX to connect to it and run vsenv in order to change to the selected VS. My extension currently only supports VSX, when it's within the same domain as the VS.