Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 2 subscribers
  • Views 3675 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to specifically route to SSL VPN clients?

Flancer
Is there a way I can specifically get the ASG to route traffic to SSL VPN clients via Routing Policies?


This thread was automatically locked due to age.
Parents
  • 0
    Local/WAN traffic, or traffic from the internet?

    Local/WAN should work with the standard VPN routing or Policy Routing.

    Incoming Traffic from the internet would be complicated if you're doing masquerading. Otherwise policy routing might work.

    Barry
Reply
  • 0
    Local/WAN traffic, or traffic from the internet?

    Local/WAN should work with the standard VPN routing or Policy Routing.

    Incoming Traffic from the internet would be complicated if you're doing masquerading. Otherwise policy routing might work.

    Barry
Children
  • 0 in reply to BarryG
    Hi Barry,

    The scenario that I'm trying to achieve is this;

    I have 2 X WAN interfaces and more than 1 LAN segments.

    one of the LAN segment's (LAN #2) Internet traffic is routed through WAN #2.

    SSL VPN connections are made through WAN #1,  but can't access LAN #2 because Astaro tries to route all replies from LAN #2 out through WAN #2.

    How can I fix this? It seems Astaro does not automatically knows how to route traffic through its internal services and it does not list the OpenVPN TUN interface on its list of interfaces.
  • 0 in reply to Flancer
    I'm guessing you have policy routes which are overriding the VPN routing.
    Perhaps you can add more policy routes to fix it.

    Barry
  • 0 in reply to BarryG
    What policies can be added?

    It seems in a dual WAN situation, the users will need to specific policy routes to route traffic through the correct gateways and at times needs to even create routes specificallyto  route traffic within the internal networks.

    It seems that using the Routing Policy to manage Multi-WAN scenarios is actually a bad thing when you have multiple internal networks to take care of.