<?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 Re: WLC Authentication Routing in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wlc-authentication-routing/m-p/1583277#M46707</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Authentication requests are sent from the management interface always.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not sure if there is any point in doing what you are looking for. The guest user authentication is an encrypted (chap) authentication request going to your radius server. What is dangerous about putting that in your internal VLAN ? It's the WLC sending the radius request, not the client. The only traffic that the client will ever be able to send is through your untrusted vlan.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nicolas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 14 Mar 2011 06:40:12 GMT</pubDate>
    <dc:creator>Nicolas Darchis</dc:creator>
    <dc:date>2011-03-14T06:40:12Z</dc:date>
    <item>
      <title>WLC Authentication Routing</title>
      <link>https://community.cisco.com/t5/wireless/wlc-authentication-routing/m-p/1583276#M46706</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a requirement to provide 802.1X certificate authentication for internal users and web authentication to guest users.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The certificate server will be on an internal trusted network where the internal employee get mapped to the internal VLAN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Guest users will map to an untrusted VLAN once authenticated using web auth then will be able to access the Internet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is that I would like the internal authentication requirest to go to the internal server and route via an internal&lt;/P&gt;&lt;P&gt;trusted VLAN and the guest user web auth authentication to route via the untrusted VLAN to the guest server on the&lt;/P&gt;&lt;P&gt;untrusted network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone confirm if this is possible or is all authentication sourced from the management interface IP address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Appreciate any help on this.&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 02:56:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-authentication-routing/m-p/1583276#M46706</guid>
      <dc:creator>billsayegh</dc:creator>
      <dc:date>2021-07-04T02:56:47Z</dc:date>
    </item>
    <item>
      <title>Re: WLC Authentication Routing</title>
      <link>https://community.cisco.com/t5/wireless/wlc-authentication-routing/m-p/1583277#M46707</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Authentication requests are sent from the management interface always.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not sure if there is any point in doing what you are looking for. The guest user authentication is an encrypted (chap) authentication request going to your radius server. What is dangerous about putting that in your internal VLAN ? It's the WLC sending the radius request, not the client. The only traffic that the client will ever be able to send is through your untrusted vlan.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nicolas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Mar 2011 06:40:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-authentication-routing/m-p/1583277#M46707</guid>
      <dc:creator>Nicolas Darchis</dc:creator>
      <dc:date>2011-03-14T06:40:12Z</dc:date>
    </item>
    <item>
      <title>Re: WLC Authentication Routing</title>
      <link>https://community.cisco.com/t5/wireless/wlc-authentication-routing/m-p/1583278#M46708</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your response, the guest authentication server will be sitting in a custom hosted environment which is physically in a different location on an unstrusted environment which is accessed via a different VPN than the customers internal VPN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can we route the authentication traffic via different VLAN based on which authentication server we want to use for a particular SSID.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If authentication request are only sent on a single VLAN IE the WLC management VLAN then we would need to do some policy based routing to direct the traffic to each VPN, not ideal.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;BR /&gt;Bill&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Mar 2011 23:04:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-authentication-routing/m-p/1583278#M46708</guid>
      <dc:creator>billsayegh</dc:creator>
      <dc:date>2011-03-14T23:04:26Z</dc:date>
    </item>
    <item>
      <title>Re: WLC Authentication Routing</title>
      <link>https://community.cisco.com/t5/wireless/wlc-authentication-routing/m-p/1583279#M46709</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As you are stating, you need routing configuration on the infrastructure. The WLC will send out through the management interface to the radius server defined in the SSID.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Mar 2011 07:57:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-authentication-routing/m-p/1583279#M46709</guid>
      <dc:creator>Nicolas Darchis</dc:creator>
      <dc:date>2011-03-15T07:57:33Z</dc:date>
    </item>
    <item>
      <title>Re: WLC Authentication Routing</title>
      <link>https://community.cisco.com/t5/wireless/wlc-authentication-routing/m-p/1583280#M46710</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your reply, I think you have answered the question that all radius authentication is sent out on the management interface, it is then up to the network to direct the traffic to where it needs to go.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Bill CCIE 3906&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Mar 2011 22:42:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-authentication-routing/m-p/1583280#M46710</guid>
      <dc:creator>billsayegh</dc:creator>
      <dc:date>2011-03-15T22:42:33Z</dc:date>
    </item>
  </channel>
</rss>

