<?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: ISE Use Case in the L2TP Dial-in in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-use-case-in-the-l2tp-dial-in/m-p/3572363#M535424</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Adding to Craig.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/wireless/asr_5000/20/GGSN/b_20_GGSN_Admin/b_19_GGSN_Admin_chapter_010011.pdf" style="font-size: 10pt;"&gt;https://www.cisco.com/c/en/us/td/docs/wireless/asr_5000/20/GGSN/b_20_GGSN_Admin/b_19_GGSN_Admin_chapter_010011.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;mentions&lt;/P&gt;&lt;DIV class="column"&gt;&lt;OL start="0" style="list-style-type: none;"&gt;&lt;LI&gt; &lt;SPAN style="font-size: 10.000000pt; font-family: 'TimesNewRomanPSMT';"&gt;The system determines that the egress context is the destination context based on the configuration of either the Default subscriber's ip-context name or from the &lt;STRONG&gt;SN-VPN-NAME&lt;/STRONG&gt; or &lt;STRONG&gt;SN1-VPN-NAME&lt;/STRONG&gt; attributes that is configured in the subscriber's RADIUS profile. &lt;/SPAN&gt; &lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I found &lt;A href="https://github.com/redBorder/freeradius/blob/master/share/dictionary.starent" title="https://github.com/redBorder/freeradius/blob/master/share/dictionary.starent"&gt;freeradius/dictionary.starent at master · redBorder/freeradius · GitHub&lt;/A&gt; and made a minor change so ISE can import it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 07 Aug 2017 22:08:41 GMT</pubDate>
    <dc:creator>hslai</dc:creator>
    <dc:date>2017-08-07T22:08:41Z</dc:date>
    <item>
      <title>ISE Use Case in the L2TP Dial-in</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-use-case-in-the-l2tp-dial-in/m-p/3572361#M535420</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="text-align: justify; font-size: 12pt; font-family: DengXian; color: #000000;"&gt;&lt;SPAN style="font-size: 10.5pt; font-family: Helvetica, sans-serif;"&gt;My customer’s requirement is the L2TP VPDN.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="text-align: justify; font-size: 12pt; font-family: DengXian; color: #000000;"&gt;&lt;SPAN style="font-size: 10.5pt; font-family: Helvetica, sans-serif;"&gt;They want to deploy a Radius server behind the LAC (L2TP Access Concentrator), which is used to return the LNS (L2TP Network Server) address to the LAC, when L2TP client initiates the Dial-in process.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="text-align: justify; font-size: 12pt; font-family: DengXian; color: #000000;"&gt;&lt;SPAN style="font-size: 10.5pt; font-family: Helvetica, sans-serif;"&gt;I heard that this was a standard Radius behavior, and Cisco ACS works well.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="text-align: justify; font-size: 12pt; font-family: DengXian; color: #000000;"&gt;&lt;SPAN style="font-size: 10.5pt; font-family: Helvetica, sans-serif;"&gt;Does ISE work in this use case?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="text-align: justify; font-size: 12pt; font-family: DengXian; color: #000000;"&gt;&lt;SPAN style="font-size: 10.5pt; font-family: Helvetica, sans-serif;"&gt;Thank you.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="text-align: justify; font-size: 12pt; font-family: DengXian; color: #000000;"&gt;&lt;SPAN style="font-size: 10.5pt; font-family: Helvetica, sans-serif;"&gt;Best regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="text-align: justify; font-size: 12pt; font-family: DengXian; color: #000000;"&gt;&lt;SPAN style="font-size: 10.5pt; font-family: Helvetica, sans-serif;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="text-align: justify; font-size: 12pt; font-family: DengXian; color: #000000;"&gt;&lt;SPAN style="font-size: 10.5pt; font-family: Helvetica, sans-serif;"&gt;Weibo Rao.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Aug 2017 16:10:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-use-case-in-the-l2tp-dial-in/m-p/3572361#M535420</guid>
      <dc:creator>Weiborao</dc:creator>
      <dc:date>2017-08-07T16:10:00Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Use Case in the L2TP Dial-in</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-use-case-in-the-l2tp-dial-in/m-p/3572362#M535421</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, it should work, but not aware of any specific QA testing on this less common use case.&amp;nbsp; These are standard RADIUS attributes.&amp;nbsp; If the default values do not include the attributes specific to L2TP, then you can use the Advanced Attributes section to add custom value settings.&amp;nbsp; Some example RADIUS attributes shown in example here: &lt;A href="https://www.cisco.com/c/en/us/td/docs/ios/12_2/12_2b/12_2b8/feature/guide/ftunauth.html#wp1030473" title="https://www.cisco.com/c/en/us/td/docs/ios/12_2/12_2b/12_2b8/feature/guide/ftunauth.html#wp1030473"&gt;Tunnel Authentication via RADIUS on Tunnel Terminator - Cisco&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/Craig&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Aug 2017 20:50:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-use-case-in-the-l2tp-dial-in/m-p/3572362#M535421</guid>
      <dc:creator>Craig Hyps</dc:creator>
      <dc:date>2017-08-07T20:50:51Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Use Case in the L2TP Dial-in</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-use-case-in-the-l2tp-dial-in/m-p/3572363#M535424</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Adding to Craig.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/wireless/asr_5000/20/GGSN/b_20_GGSN_Admin/b_19_GGSN_Admin_chapter_010011.pdf" style="font-size: 10pt;"&gt;https://www.cisco.com/c/en/us/td/docs/wireless/asr_5000/20/GGSN/b_20_GGSN_Admin/b_19_GGSN_Admin_chapter_010011.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;mentions&lt;/P&gt;&lt;DIV class="column"&gt;&lt;OL start="0" style="list-style-type: none;"&gt;&lt;LI&gt; &lt;SPAN style="font-size: 10.000000pt; font-family: 'TimesNewRomanPSMT';"&gt;The system determines that the egress context is the destination context based on the configuration of either the Default subscriber's ip-context name or from the &lt;STRONG&gt;SN-VPN-NAME&lt;/STRONG&gt; or &lt;STRONG&gt;SN1-VPN-NAME&lt;/STRONG&gt; attributes that is configured in the subscriber's RADIUS profile. &lt;/SPAN&gt; &lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I found &lt;A href="https://github.com/redBorder/freeradius/blob/master/share/dictionary.starent" title="https://github.com/redBorder/freeradius/blob/master/share/dictionary.starent"&gt;freeradius/dictionary.starent at master · redBorder/freeradius · GitHub&lt;/A&gt; and made a minor change so ISE can import it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Aug 2017 22:08:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-use-case-in-the-l2tp-dial-in/m-p/3572363#M535424</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2017-08-07T22:08:41Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Use Case in the L2TP Dial-in</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-use-case-in-the-l2tp-dial-in/m-p/3572364#M535426</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for your support.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Aug 2017 13:47:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-use-case-in-the-l2tp-dial-in/m-p/3572364#M535426</guid>
      <dc:creator>Weiborao</dc:creator>
      <dc:date>2017-08-08T13:47:05Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Use Case in the L2TP Dial-in</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-use-case-in-the-l2tp-dial-in/m-p/3572365#M535428</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for your support and contribution.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Aug 2017 13:47:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-use-case-in-the-l2tp-dial-in/m-p/3572365#M535428</guid>
      <dc:creator>Weiborao</dc:creator>
      <dc:date>2017-08-08T13:47:37Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Use Case in the L2TP Dial-in</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-use-case-in-the-l2tp-dial-in/m-p/3877906#M535429</link>
      <description>&lt;P&gt;I have cisco router for vpdn server and my clients are windows l2tp connection , and i use cisco ise ( join domain) for radius server and router send aaa to ise . Every thing is ok but radius live log is bad , i have not any clients endpoint address,clients mac address and live session in radius live log , it s show just user authenticatin and authorization users . Please help me .&lt;/P&gt;</description>
      <pubDate>Sat, 22 Jun 2019 15:45:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-use-case-in-the-l2tp-dial-in/m-p/3877906#M535429</guid>
      <dc:creator>hamidreza.taghipur</dc:creator>
      <dc:date>2019-06-22T15:45:30Z</dc:date>
    </item>
  </channel>
</rss>

