Controllerless Networks

last person joined: yesterday 

Instant Mode - the controllerless Wi-Fi solution that's easy to set up, is loaded with security and smarts, and won't break your budget
Back to discussions
Expand all | Collapse all

Client IP Assignment Virtual Controller Assigned NAT clarification

This thread has been viewed 0 times

  • 1.  Client IP Assignment Virtual Controller Assigned NAT clarification

    Posted Sep 12, 2019 03:38 PM

    Could someone verify something for me?

    We are trying to setup a guest network and I am trying to "air gap" the guest network off the access point management subnet / IP.

     

    From my reading, video demos, and other posts on airheads I was under the belief that when the Virtual Cluster had an IP address configured to it and the guest SSID had Client IP Assignment set to Virtual Controller Assigned the source NAT was that of the Virtual Controller not the physical AP management IP address.  What I am seeing is all traffic is NATed to the management IP address of the physical master AP.  I ran this past support and they told me that where the documentation says Virtual Controller it not referring to the software "Virtual Controller" it is referring to the cluster master device that is functioning as the Virtual Controller at that time. 

    Since there are several howtos that seem to contradict that I was wondering if anyone could verify the expected behavior. 

    Also could someone explain to me the purpose/value of NATing to the physical controller versus each AP NATing itself since the source IP address would change any time the master AP changes you would have to configure your infrastructure to accommodate every access point anyway?.

     

    Thanks!