<?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 Mobility Anchor and RADIUS in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/mobility-anchor-and-radius/m-p/3845946#M204975</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I am looking to advertise a number of wireless profiles for an organisation that has a presence on our campus.&amp;nbsp; I will use our APs to do this and then run Foreign/Anchor set up for each profile so that clients of these profiles break out onto the other parties network.&amp;nbsp; One of these profiles will use EAP-PEAP.&lt;/P&gt;&lt;P&gt;My question is, will all the RADIUS transactions take place within the EoIP tunnel, i.e. mediated by the Anchor, or will they be mediated by the Foreign WLC.&amp;nbsp; This is important when it comes to opening ports on the firewall that will be running a VPN between sites.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Terry&lt;/P&gt;</description>
    <pubDate>Mon, 05 Jul 2021 17:17:46 GMT</pubDate>
    <dc:creator>terrywatson651</dc:creator>
    <dc:date>2021-07-05T17:17:46Z</dc:date>
    <item>
      <title>Mobility Anchor and RADIUS</title>
      <link>https://community.cisco.com/t5/wireless/mobility-anchor-and-radius/m-p/3845946#M204975</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I am looking to advertise a number of wireless profiles for an organisation that has a presence on our campus.&amp;nbsp; I will use our APs to do this and then run Foreign/Anchor set up for each profile so that clients of these profiles break out onto the other parties network.&amp;nbsp; One of these profiles will use EAP-PEAP.&lt;/P&gt;&lt;P&gt;My question is, will all the RADIUS transactions take place within the EoIP tunnel, i.e. mediated by the Anchor, or will they be mediated by the Foreign WLC.&amp;nbsp; This is important when it comes to opening ports on the firewall that will be running a VPN between sites.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Terry&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 17:17:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/mobility-anchor-and-radius/m-p/3845946#M204975</guid>
      <dc:creator>terrywatson651</dc:creator>
      <dc:date>2021-07-05T17:17:46Z</dc:date>
    </item>
    <item>
      <title>Re: Mobility Anchor and RADIUS</title>
      <link>https://community.cisco.com/t5/wireless/mobility-anchor-and-radius/m-p/3845979#M204976</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&amp;nbsp;Anchor WLC is responsible to handle RADIUS requests and response when on this scenario. Foreign will handle RADIUS to those profiles that is not tunneled back to the Anchor.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-If I helped you somehow, please, rate it as useful.-&lt;/P&gt;</description>
      <pubDate>Fri, 26 Apr 2019 12:24:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/mobility-anchor-and-radius/m-p/3845979#M204976</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2019-04-26T12:24:57Z</dc:date>
    </item>
    <item>
      <title>Re: Mobility Anchor and RADIUS</title>
      <link>https://community.cisco.com/t5/wireless/mobility-anchor-and-radius/m-p/3845982#M204977</link>
      <description>&lt;P&gt;Hi Flavio&lt;/P&gt;&lt;P&gt;I thought that's how it worked, just wanted to be sure.&amp;nbsp; Thanks for taking the time to respond.&lt;/P&gt;&lt;P&gt;Kind Regards&lt;/P&gt;&lt;P&gt;Terry&lt;/P&gt;</description>
      <pubDate>Fri, 26 Apr 2019 12:30:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/mobility-anchor-and-radius/m-p/3845982#M204977</guid>
      <dc:creator>terrywatson651</dc:creator>
      <dc:date>2019-04-26T12:30:01Z</dc:date>
    </item>
  </channel>
</rss>

