<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Hi Scott in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/flex-connect-web-authentication/m-p/2773720#M140017</link>
    <description>&lt;P&gt;Hi Scott&lt;/P&gt;
&lt;P&gt;Thanks for the reply.&lt;/P&gt;
&lt;P&gt;I'm using locally switched with central authentication and central DHCP with a scope on the controller.&lt;/P&gt;
&lt;P&gt;My understanding has always been&amp;nbsp;that normally with web auth, the client associates, gets an IP address and then opens a browser. The client device then does a DNS lookup for the browser page, tries to go to that IP address, and then the controller intercepts and redirects the client to the login page.&lt;/P&gt;
&lt;P&gt;My concern is the DNS element of this process. If this isn't switched locally then I would need to provide a path for the controller to be able to get to an external DNS server. Obviously I can't have the same subnet switched locally and also available on the controller.&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Roger&lt;/P&gt;</description>
    <pubDate>Sun, 01 Nov 2015 19:23:16 GMT</pubDate>
    <dc:creator>Roger Alderman</dc:creator>
    <dc:date>2015-11-01T19:23:16Z</dc:date>
    <item>
      <title>Flex Connect Web Authentication</title>
      <link>https://community.cisco.com/t5/wireless/flex-connect-web-authentication/m-p/2773718#M140015</link>
      <description>&lt;P&gt;Hi All&lt;/P&gt;
&lt;P&gt;Can anyone tell me what path DNS takes when using Web Authentication with Flex Connect Local Switching and Central Authentication?&lt;/P&gt;
&lt;P&gt;Does the DNS traffic for the authentication go down the CAPWAP tunnel to the controller or does it break out locally?&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Roger&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 11:09:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flex-connect-web-authentication/m-p/2773718#M140015</guid>
      <dc:creator>Roger Alderman</dc:creator>
      <dc:date>2021-07-05T11:09:26Z</dc:date>
    </item>
    <item>
      <title>Rodger,</title>
      <link>https://community.cisco.com/t5/wireless/flex-connect-web-authentication/m-p/2773719#M140016</link>
      <description>&lt;P&gt;Rodger,&lt;/P&gt;
&lt;P&gt;Authententication happens through the CAPWAP tunnel as the controller does the authentication or send the auth to a radius sever. Once the authentication happens, then all traffic is either centrally switched or locally switched depending on how you setup the WLAN for a FlexConnect AP.&lt;/P&gt;
&lt;P&gt;-Scott&lt;/P&gt;</description>
      <pubDate>Sun, 01 Nov 2015 16:20:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flex-connect-web-authentication/m-p/2773719#M140016</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2015-11-01T16:20:21Z</dc:date>
    </item>
    <item>
      <title>Hi Scott</title>
      <link>https://community.cisco.com/t5/wireless/flex-connect-web-authentication/m-p/2773720#M140017</link>
      <description>&lt;P&gt;Hi Scott&lt;/P&gt;
&lt;P&gt;Thanks for the reply.&lt;/P&gt;
&lt;P&gt;I'm using locally switched with central authentication and central DHCP with a scope on the controller.&lt;/P&gt;
&lt;P&gt;My understanding has always been&amp;nbsp;that normally with web auth, the client associates, gets an IP address and then opens a browser. The client device then does a DNS lookup for the browser page, tries to go to that IP address, and then the controller intercepts and redirects the client to the login page.&lt;/P&gt;
&lt;P&gt;My concern is the DNS element of this process. If this isn't switched locally then I would need to provide a path for the controller to be able to get to an external DNS server. Obviously I can't have the same subnet switched locally and also available on the controller.&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Roger&lt;/P&gt;</description>
      <pubDate>Sun, 01 Nov 2015 19:23:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flex-connect-web-authentication/m-p/2773720#M140017</guid>
      <dc:creator>Roger Alderman</dc:creator>
      <dc:date>2015-11-01T19:23:16Z</dc:date>
    </item>
    <item>
      <title>Please check this links</title>
      <link>https://community.cisco.com/t5/wireless/flex-connect-web-authentication/m-p/2773721#M140018</link>
      <description>&lt;P&gt;Please check this links&lt;/P&gt;
&lt;P&gt;http://www.cisco.com/c/en/us/support/docs/wireless/flex-7500-series-wireless-controllers/113605-ewa-flex-guide-00.html&lt;/P&gt;
&lt;P&gt;https://supportforums.cisco.com/discussion/11897761/flexconnect-local-guest-wireless-w-web-auth&lt;/P&gt;</description>
      <pubDate>Wed, 04 Nov 2015 10:11:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flex-connect-web-authentication/m-p/2773721#M140018</guid>
      <dc:creator>Prakash Parvathala</dc:creator>
      <dc:date>2015-11-04T10:11:22Z</dc:date>
    </item>
  </channel>
</rss>

