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. Server IP (Source address translated) configuration advice

Server IP (Source address translated) configuration advice

Scheduled Pinned Locked Moved Support
2 Posts 2 Posters 17.1k 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.
  • S
    S
    sodalist
    wrote on last edited by
    #1

    What would be advised way to handle server to agent connection in case that server address
    is source ip network address translated and translated IP is chosen dynamically from pool of
    ip addresses. (static translation is not possible, not technical reason)

    Practically:
    SERVER (ip a.a.a.a/24) <-> SNAT (pool b.b.b.b/26) <- VPN -> agent (ip c.c.c.c/24)

    Server translated address at time of connection could be b.b.b.1-b.b.b.127.

    Solutions  (parameters Servers =, ControlServers =, MasterServers 😃
    * define all possible ip address in Servers = ...
    * create dns A record with all possible ip addressees and use dns name as parameter value
    * create feature request for parameters to accept CIDR notation

    Possible solution:
    * create feature request to add logic to client:
      if none of  Servers =, ControlServers =, MasterServers =  are defined
      and required authentication+encryption is configured
      allow configuration value 0.0.0.0
      as Servers =, ControlServers =, MasterServers = parameter value.
     
    thank you,

    Ales

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

      Hi!

      Currently the only working solution is to list all possible server's IP addresses in MasterServers. Using DNS name will not work because agent do name resolution only once at startup. I'll add feature request for supporting subnets in form xxx.xxx.xxx.xxx/nn in *Servers parameters.

      Best regards,
      Victor

      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