Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. TCP Proxy to service on same network as node

TCP Proxy to service on same network as node

Scheduled Pinned Locked Moved Support
4 Posts 3 Posters 30.5k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D
    D
    djex81
    wrote on last edited by
    #1

    So I've been playing around with the new TCP Proxy feature and it seems I am only able to access local ports on a particular node. Is it possible to proxy to a service located on another device on the same network as the node?

    For example I would like to access a Synology web admin panel through another node on the same network. The local network address for the admin panel would be something like http://192.168.1.10:5000 . When configuring the Local Command in Object Tools the TCP Tunnel check box only allows to specify a port number. There seems to be no where to supply an address. Is it possible to configure the current TCP proxy to do this or is it only possible to proxy local ports on a node?

    I've used remote access software in the past that allowed me to do this. Not sure if I'm missing something here.

    1 Reply Last reply
    0
    • V
      V
      Victor Kirhenshtein
      wrote on last edited by
      #2

      It works as following. First of all, you have to enable TCP proxy on a proxy agent. By default it will be agent running on NetXMS server, or if zoning is enabled, agent running on zone proxy. When you run object tool with TCP proxy option, client will open random local port for listening, then establish tunnel to proxy agent, and when you open TCP connection to this random local port, proxy agent will establish TCP connection to target node on port set in object tool configuration.

      So, for example, let's say you have Synology device reachable at 192.168.1.10 by the server. You will do the following steps:

      1. You Synology device to NetXMS as a node, and specify 192.168.1.10 as primary IP address.
      2. Enable TCP proxy on server's agent.
      3. Enable TCP port forwarding option in object tool, and use URL http://${local-address}:${local-port}

      When running on Synology node, this tool should open browser on local host which will be forwarded to Synology device.

      Best regards,
      Victor

      1 Reply Last reply
      0
      • D
        D
        djex81
        wrote on last edited by
        #3

        Thanks for the reply. There are two issues I have:

        1. First the Synology device is not on the same network as the netxms server. I am using another workstation on the network of the Synology NAS as an SNMP proxy to monitor the Synology NAS.
        2. I can not install the netxms agent on the Synology NAS because it is running a custom linux distro that is not supported by netxms agent (I tried)

        And so I need some way to TCP proxy from the workstation that is on the same network as the Synology NAS to the Synology's web admin panel on port 5000.

        I can enable TCP proxy on the workstation agent however there seems to be no way in object tools to configure the tool to access a specific IP along with the port.

        I have used this feature in other remote access software which would allow specifying both the Remote Host IP and Remote Host Port to proxy. Not sure if this is possible with the TCP proxy feature or if there are any workarounds.

        1 Reply Last reply
        0
        • F
          F
          Filipp Sudanov
          wrote on last edited by
          #4

          In this case You'd need to create a Zone and set this worksation, which is on the same network as Synology NAS as proxy for that zone.

          1 Reply Last reply
          0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          Powered by NodeBB Contributors
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • Users
          • Groups