Announcement

Collapse
No announcement yet.

OpenVPN exported networks

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • OpenVPN exported networks

    I want to allow an AWS load balancer to be exported and allowed on my network. Something like example.us-east-1.rds.amazonaws.com. The problem is that Untangle currently only supports CIDR networks and the load balancer constantly changes IPs. Is there any way of adding to the exported networks an FQDN or URL that changes IPs?
    Right now I am exporting entire ranges of IPs which kinda defeats the point of exporting networks.

  • #2
    Unfortunately not; that field will only take IP addresses.
    Græme Ravenscroft • Technical Marketing Engineer
    ('gram', like the unit of measurement)
    he/him
    How can we make Arista ETM products better?

    Comment


    • #3
      This just isn't ever going to work. The Linux kernel routes based on IP address, you cannot ever route based on a name. You can try to lookup the name and cache the IP address, but how frequently do you update that? This is just a can of worms... Not to mention if you did this guess what... you're exporting ranges of IP addresses. This fixed what exactly?

      The only sane way out is API integration so that Amazon can push updated information at the point of change to all platforms. NGFW cannot do this, nor can Sonicwall or anything else.

      So I'm back to asking what your use case is, because it's time to get creative.
      Last edited by sky-knight; 01-14-2023, 07:01 AM.
      Rob Sandling, BS:SWE, MCP, Microsoft Certified: Azure Administrator Associate
      NexgenAppliances.com
      Phone: 866-794-8879 x201
      Email: [email protected]

      Comment

      Working...
      X
      😀
      🥰
      🤢
      😎
      😡
      👍
      👎