<?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 Calling station ID attribute  needs MAC address  for Anyconnect  in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/calling-station-id-attribute-needs-mac-address-for-anyconnect/m-p/2362937#M105779</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Parag,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Calling Station ID will always contain IP Address in case of Anyconnect VPN.&lt;/P&gt;&lt;P&gt;L3 being the cause unlike Wireless which has L2 Assoc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Currently no workaround.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regard&lt;/P&gt;&lt;P&gt;Ed&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 08 Dec 2013 02:42:41 GMT</pubDate>
    <dc:creator>edwjames</dc:creator>
    <dc:date>2013-12-08T02:42:41Z</dc:date>
    <item>
      <title>Calling station ID attribute  needs MAC address  for Anyconnect VPN client</title>
      <link>https://community.cisco.com/t5/network-access-control/calling-station-id-attribute-needs-mac-address-for-anyconnect/m-p/2362936#M105769</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are testing Anyconnect VPN users tring to connect using certificate. ASA is validating/ authenticating user based on cert and for authorization it is requesting Radius server(ISE). Currently ASA&amp;nbsp; is sending Ip address of VPN client in "calling station ID" .We want ASA to send MAC address of Anyconnect VPN client to radius server in 'calling station ID' radius attribute.&amp;nbsp; Is it possible to achieve this. Any workround ?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 04:09:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/calling-station-id-attribute-needs-mac-address-for-anyconnect/m-p/2362936#M105769</guid>
      <dc:creator>Parag Mahajan</dc:creator>
      <dc:date>2019-03-11T04:09:47Z</dc:date>
    </item>
    <item>
      <title>Calling station ID attribute  needs MAC address  for Anyconnect</title>
      <link>https://community.cisco.com/t5/network-access-control/calling-station-id-attribute-needs-mac-address-for-anyconnect/m-p/2362937#M105779</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Parag,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Calling Station ID will always contain IP Address in case of Anyconnect VPN.&lt;/P&gt;&lt;P&gt;L3 being the cause unlike Wireless which has L2 Assoc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Currently no workaround.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regard&lt;/P&gt;&lt;P&gt;Ed&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 08 Dec 2013 02:42:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/calling-station-id-attribute-needs-mac-address-for-anyconnect/m-p/2362937#M105779</guid>
      <dc:creator>edwjames</dc:creator>
      <dc:date>2013-12-08T02:42:41Z</dc:date>
    </item>
    <item>
      <title>Calling station ID attribute  needs MAC address  for Anyconnect</title>
      <link>https://community.cisco.com/t5/network-access-control/calling-station-id-attribute-needs-mac-address-for-anyconnect/m-p/2362938#M105803</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Edward&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Dec 2013 11:58:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/calling-station-id-attribute-needs-mac-address-for-anyconnect/m-p/2362938#M105803</guid>
      <dc:creator>Parag Mahajan</dc:creator>
      <dc:date>2013-12-16T11:58:36Z</dc:date>
    </item>
  </channel>
</rss>

