<?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 [WiNG 7.6.0.0-024R, VX9000, AP360e] Captive Portal policy accepts only host ip alias? in ExtremeWireless (WiNG)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-wing/wing-7-6-0-0-024r-vx9000-ap360e-captive-portal-policy-accepts/m-p/63500#M5680</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I’d like to ask about using aliases to have multiple different captive portal FQDNs in different locations. Assuming AP is the captive portal server.&lt;/P&gt;&lt;P&gt;When configuring Captive Portal Server Host parameter directly, it allows “ip or hostname” and we typically do some nonexistent FQDNs, but creating string alias in an RF-Domain to be put as the parameter gives an error in result. I mean, controller commits ok but the AP returns an error under show adoption status, so I check for config-errors and I get:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;vx9000(config)#show adoption config-errors ap360-xxxx&lt;BR /&gt;*** (4, '/wing-config/device[mac=AA-BB-CC-DD-EE-FF', "Cannot commit, alias $test of type(s) ['host_alias', 'host_alias'] is undefined.")&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;When I define a host alias with an IP instead of a string alias, config push is acknowledged by the AP with no issues.&lt;/P&gt;&lt;P&gt;Shouldn’t that be possible?&lt;/P&gt;&lt;P&gt;As a workaround I have recommended the partner to use some static generic hostname instead multiplying captive portal policies to get various FQDNs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Tomasz&lt;/P&gt;</description>
    <pubDate>Fri, 09 Apr 2021 03:32:21 GMT</pubDate>
    <dc:creator>Tomasz</dc:creator>
    <dc:date>2021-04-09T03:32:21Z</dc:date>
    <item>
      <title>[WiNG 7.6.0.0-024R, VX9000, AP360e] Captive Portal policy accepts only host ip alias?</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/wing-7-6-0-0-024r-vx9000-ap360e-captive-portal-policy-accepts/m-p/63500#M5680</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I’d like to ask about using aliases to have multiple different captive portal FQDNs in different locations. Assuming AP is the captive portal server.&lt;/P&gt;&lt;P&gt;When configuring Captive Portal Server Host parameter directly, it allows “ip or hostname” and we typically do some nonexistent FQDNs, but creating string alias in an RF-Domain to be put as the parameter gives an error in result. I mean, controller commits ok but the AP returns an error under show adoption status, so I check for config-errors and I get:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;vx9000(config)#show adoption config-errors ap360-xxxx&lt;BR /&gt;*** (4, '/wing-config/device[mac=AA-BB-CC-DD-EE-FF', "Cannot commit, alias $test of type(s) ['host_alias', 'host_alias'] is undefined.")&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;When I define a host alias with an IP instead of a string alias, config push is acknowledged by the AP with no issues.&lt;/P&gt;&lt;P&gt;Shouldn’t that be possible?&lt;/P&gt;&lt;P&gt;As a workaround I have recommended the partner to use some static generic hostname instead multiplying captive portal policies to get various FQDNs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Tomasz&lt;/P&gt;</description>
      <pubDate>Fri, 09 Apr 2021 03:32:21 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/wing-7-6-0-0-024r-vx9000-ap360e-captive-portal-policy-accepts/m-p/63500#M5680</guid>
      <dc:creator>Tomasz</dc:creator>
      <dc:date>2021-04-09T03:32:21Z</dc:date>
    </item>
    <item>
      <title>Re: [WiNG 7.6.0.0-024R, VX9000, AP360e] Captive Portal policy accepts only host ip alias?</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/wing-7-6-0-0-024r-vx9000-ap360e-captive-portal-policy-accepts/m-p/63501#M5681</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;Aliases are not currently supported in the Captive Portal Host field / Captive Portal Host command.&amp;nbsp; &amp;nbsp;For a list of fields that support aliases please refer to page 19 of the WiNG Best Practices and Recommendations document.&amp;nbsp; &amp;nbsp;The document can be found here….&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.extremenetworks.com/support/documentation/wing-5-x-how-to-guides/" target="_blank" rel="nofollow noreferrer noopener"&gt;https://www.extremenetworks.com/support/documentation/wing-5-x-how-to-guides/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Thank You&lt;/P&gt;</description>
      <pubDate>Fri, 23 Apr 2021 02:34:15 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/wing-7-6-0-0-024r-vx9000-ap360e-captive-portal-policy-accepts/m-p/63501#M5681</guid>
      <dc:creator>G_May</dc:creator>
      <dc:date>2021-04-23T02:34:15Z</dc:date>
    </item>
  </channel>
</rss>

