Skip to main content
icankil
New Member
April 27, 2016
Solved

VDOMS with SSL VPN.

  • April 27, 2016
  • 1 reply
  • 6436 views

Hi,

 

Good day,

 

Anyone experience doing multiple VDOMS with multiple SSL VPN portals, but using only 1 public address.

 

The ISP is connected to the root VDOM so i made a routing and policy and made a inter VDOM link to VDOM2.

I have no problem on accessing SSL VPN Portal for root VDOM since the ISP is connected

EX PublicIP:8080 >> portal for root vdom.

 

Now i set up the SSL VPN Portal for VDOM2, and listening to a private IP with unique corresponding port

(its InterVDOM link interface) 172.16.1.1:8081

 

Now since the internet is connected to the root VDOM, I created a VIP to translate cause I am using only one public ip.

Ex. PublicIP:8081 >>> 172.16.1.1:8081

 

No luck. its not translating.

I sure my policy and routing is okay i can ping an ip from each vdom. and policies are ANY ALL to ANY ALL

 

Is other work around for this? what i might  missed out?

 

 

 

 

    Best answer by emnoc

    The diag debug flow is your friend,  but yes your on the right approach with a DNAT to the  internal SSLVPN portal in the vdom 1 2 3 4 so-on...

     

    I would look at the following

     

    1:  fwpolicies are correct

     

    2: dport ( 11443 443 etc...)

     

    3: that you have no other internal mis-configuration in the inside  vdoms

     

    4: DNAT VIP mappaing is correct to the target vpn ipv4 address

     

     

     

    1 reply

    emnoc
    emnocAnswer
    New Member
    April 27, 2016

    The diag debug flow is your friend,  but yes your on the right approach with a DNAT to the  internal SSLVPN portal in the vdom 1 2 3 4 so-on...

     

    I would look at the following

     

    1:  fwpolicies are correct

     

    2: dport ( 11443 443 etc...)

     

    3: that you have no other internal mis-configuration in the inside  vdoms

     

    4: DNAT VIP mappaing is correct to the target vpn ipv4 address