<?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 @shh5455, webauth does work in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/flexconnect-central-webaythentication-for-remote-user/m-p/2565021#M32036</link>
    <description>&lt;P&gt;&lt;STRONG&gt;@shh5455&lt;/STRONG&gt;, webauth does work with flexconnect local switching (&lt;A href="http://www.cisco.com/c/en/us/support/docs/wireless/5500-series-wireless-controllers/112042-technote-wlc-00.html"&gt;FlexConnect Feature Matrix&lt;/A&gt;). When a client associates to the WLAN, the pre-auth ALC will allow DHCP and DNS and traffic. The next step is that when a client tries to reach a website it will be redirected by the WLC to the virtual IP address of the WLC. This traffic is being tunneled by the AP into a CAPWAP tunnel to the management interface of the WLC, in this way there is no need for end-to-end IP connectivity between the client and the WLC.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;@MuhammadSaad_2&lt;/STRONG&gt;, there is not much what you can do about it. The client needs to do at least one http request to get redirected to the portal page. Apple does have a "solution" for this problem with a pseudo web browser /&amp;nbsp;Captive Network Assistant which get launched after it detects that there is no direct internet access. However that does not always work flawless as well. So unless you really need the portal for something like marketing, I would prefer a dot1x solution or just a simple psk over the portal.&lt;/P&gt;</description>
    <pubDate>Tue, 20 Jan 2015 00:19:55 GMT</pubDate>
    <dc:creator>Freerk Terpstra</dc:creator>
    <dc:date>2015-01-20T00:19:55Z</dc:date>
    <item>
      <title>Flexconnect Central Webaythentication for Remote user</title>
      <link>https://community.cisco.com/t5/wireless/flexconnect-central-webaythentication-for-remote-user/m-p/2565019#M32034</link>
      <description>&lt;DIV class="jive-rendered-content"&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Am facing problem with Flexconnect with guest user. My scenario is i have local DHCP at remote site for guest but i want them to authenticate through central WLC.&lt;/P&gt;&lt;P&gt;Am using Layer 3 web authentication. also the web authentication page is not popping up automatically, we have to type Google or any web than it redirect to virtual WLC interface.&lt;/P&gt;&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank You&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 05 Jul 2021 09:17:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flexconnect-central-webaythentication-for-remote-user/m-p/2565019#M32034</guid>
      <dc:creator>MuhammadSaad_2</dc:creator>
      <dc:date>2021-07-05T09:17:44Z</dc:date>
    </item>
    <item>
      <title>Are you using local switching</title>
      <link>https://community.cisco.com/t5/wireless/flexconnect-central-webaythentication-for-remote-user/m-p/2565020#M32035</link>
      <description>&lt;P&gt;EDIT: Freerk is correct. &amp;nbsp;See below.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jan 2015 00:19:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flexconnect-central-webaythentication-for-remote-user/m-p/2565020#M32035</guid>
      <dc:creator>shh5455</dc:creator>
      <dc:date>2015-01-20T00:19:54Z</dc:date>
    </item>
    <item>
      <title>@shh5455, webauth does work</title>
      <link>https://community.cisco.com/t5/wireless/flexconnect-central-webaythentication-for-remote-user/m-p/2565021#M32036</link>
      <description>&lt;P&gt;&lt;STRONG&gt;@shh5455&lt;/STRONG&gt;, webauth does work with flexconnect local switching (&lt;A href="http://www.cisco.com/c/en/us/support/docs/wireless/5500-series-wireless-controllers/112042-technote-wlc-00.html"&gt;FlexConnect Feature Matrix&lt;/A&gt;). When a client associates to the WLAN, the pre-auth ALC will allow DHCP and DNS and traffic. The next step is that when a client tries to reach a website it will be redirected by the WLC to the virtual IP address of the WLC. This traffic is being tunneled by the AP into a CAPWAP tunnel to the management interface of the WLC, in this way there is no need for end-to-end IP connectivity between the client and the WLC.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;@MuhammadSaad_2&lt;/STRONG&gt;, there is not much what you can do about it. The client needs to do at least one http request to get redirected to the portal page. Apple does have a "solution" for this problem with a pseudo web browser /&amp;nbsp;Captive Network Assistant which get launched after it detects that there is no direct internet access. However that does not always work flawless as well. So unless you really need the portal for something like marketing, I would prefer a dot1x solution or just a simple psk over the portal.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jan 2015 00:19:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flexconnect-central-webaythentication-for-remote-user/m-p/2565021#M32036</guid>
      <dc:creator>Freerk Terpstra</dc:creator>
      <dc:date>2015-01-20T00:19:55Z</dc:date>
    </item>
    <item>
      <title>Freerk, you are correct.  I</title>
      <link>https://community.cisco.com/t5/wireless/flexconnect-central-webaythentication-for-remote-user/m-p/2565022#M32037</link>
      <description>&lt;P&gt;Freerk, you are correct. &amp;nbsp;I was going by memory. &amp;nbsp;Thanks for the update.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jan 2015 14:36:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flexconnect-central-webaythentication-for-remote-user/m-p/2565022#M32037</guid>
      <dc:creator>shh5455</dc:creator>
      <dc:date>2015-01-20T14:36:55Z</dc:date>
    </item>
  </channel>
</rss>

