https://community.cisco.com/t5/wireless/cisco-wireless-controller/m-p/3089926#M147123 <P>hello team,</P> <P></P> <P>Reasons for configuring the virtual ip address in the controller for the guest authentication?</P> <P></P> <P>Currently the users were not getting web authentication page.</P> <P>Regards,</P> <P>R</P> <P></P> Mon, 05 Jul 2021 14:22:08 GMT Thushara 2021-07-05T14:22:08Z https://community.cisco.com/t5/wireless/cisco-wireless-controller/m-p/3089926#M147123 <P>hello team,</P> <P></P> <P>Reasons for configuring the virtual ip address in the controller for the guest authentication?</P> <P></P> <P>Currently the users were not getting web authentication page.</P> <P>Regards,</P> <P>R</P> <P></P> Mon, 05 Jul 2021 14:22:08 GMT https://community.cisco.com/t5/wireless/cisco-wireless-controller/m-p/3089926#M147123 Thushara 2021-07-05T14:22:08Z https://community.cisco.com/t5/wireless/cisco-wireless-controller/m-p/3089927#M147124 <P>Hi,</P> <P>Virtual interface is used for certain client management functions such as DHCP request and mobility/roaming functions (every controller in the same mobility group should be configured with identical virtual address).</P> <P>in other words....</P> <P>Virtual Interface – This interface handles any mobility management, VPN Termination, Web authentication, and is also a DHCP relay for WLAN clients. You really want to give this interface a bogus type address (Like 1.1.1.1 or something) since it’s only accessed and used by the WLC, the APs and WLAN clients will not interact with this interface. (Other then it’s purpose as the DHCP relay, but it’s all in done within the controller unknown to the AP’s or clients).</P> <P></P> <P>Regards</P> <P>Dont forget to rate helpful posts</P> Thu, 20 Jul 2017 05:15:32 GMT https://community.cisco.com/t5/wireless/cisco-wireless-controller/m-p/3089927#M147124 Sandeep Choudhary 2017-07-20T05:15:32Z