Skip to main content
adGmail
New Member
September 2, 2020
Question

5.x VIP for PAT not valid on 6.x

  • September 2, 2020
  • 2 replies
  • 2881 views

I used the following VIP config to perform a PAT (without NAT) on 5.x;

edit "vip-10.1.2.1-tcp2022" set src-filter "172.17.2.1" "172.18.1.14" set extip 10.1.2.1 set extintf "any" set arp-reply disable set portforward enable set mappedip "10.1.2.1" set extport 22 set mappedport 2022

 

However on 6.0.10 creating this object fails with "

Static NAT's extip should be different from mappedip. object check operator error, -8, discard the setting Command fail. Return code 1"

 

How can I achieve this on v6?

 

Thanks

    2 replies

    lobstercreed
    New Member
    September 3, 2020

    I'm surprised that would have ever worked.  It sounds like a bug, because port-forwarding is redundant without NAT being involved.  Just tell whoever is connecting on port 22 to connect on port 2022, or change the application so that is listens on port 22.  Either way, port translation in this scenario seems like a hack around the real issue.

    adGmail
    adGmailAuthor
    New Member
    September 6, 2020

    FYI, the fix is to add 'set type load-balance' to the VIP config. Not exactly intuitive.

    Thought Leadership Security Summit. Outpace New Threats with AI - enhanced defense. Tuesday, Septmeber 15, 8:30 AM - 2:30 PM PT. The Golf Club at Newcastle, WA.
    Fortinet Flag the Hack. Wednesday, August 26, 9:00 AM - 5:00 PM ET, COSM, Atlanta, GA.
    Virtual event | September 2026. SASE summit. The age of autonomous trust. Register here!