<?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 New APs take a DHCP lease when they are connected to our network and one of our new APs at a different location than our hivemanager also overrides the IP of our static DNS entry for the ap. in Aerohive Migrated Content</title>
    <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/new-aps-take-a-dhcp-lease-when-they-are-connected-to-our-network/m-p/76151#M6950</link>
    <description>&lt;P&gt;Some more details. We've configured a static ip on the aps before they are connected to the hivemanager. Even though we've configured a static ip, the ap takes several dhcp leases from our different client vlans which are tagged on the ap-port and also, like already said, overrides the ip of our static DNS entry, even after we delete it and re-create it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone got a possible solution for this?&lt;/P&gt;</description>
    <pubDate>Fri, 07 Dec 2018 16:10:21 GMT</pubDate>
    <dc:creator>AnonymousM</dc:creator>
    <dc:date>2018-12-07T16:10:21Z</dc:date>
    <item>
      <title>New APs take a DHCP lease when they are connected to our network and one of our new APs at a different location than our hivemanager also overrides the IP of our static DNS entry for the ap.</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/new-aps-take-a-dhcp-lease-when-they-are-connected-to-our-network/m-p/76151#M6950</link>
      <description>&lt;P&gt;Some more details. We've configured a static ip on the aps before they are connected to the hivemanager. Even though we've configured a static ip, the ap takes several dhcp leases from our different client vlans which are tagged on the ap-port and also, like already said, overrides the ip of our static DNS entry, even after we delete it and re-create it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone got a possible solution for this?&lt;/P&gt;</description>
      <pubDate>Fri, 07 Dec 2018 16:10:21 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/new-aps-take-a-dhcp-lease-when-they-are-connected-to-our-network/m-p/76151#M6950</guid>
      <dc:creator>AnonymousM</dc:creator>
      <dc:date>2018-12-07T16:10:21Z</dc:date>
    </item>
    <item>
      <title>Re: New APs take a DHCP lease when they are connected to our network and one of our new APs at a different location than our hivemanager also overrides the IP of our static DNS entry for the ap.</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/new-aps-take-a-dhcp-lease-when-they-are-connected-to-our-network/m-p/76152#M6951</link>
      <description>&lt;P&gt;P.s. we are using Bonjour Gateway&lt;/P&gt;</description>
      <pubDate>Fri, 07 Dec 2018 16:10:59 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/new-aps-take-a-dhcp-lease-when-they-are-connected-to-our-network/m-p/76152#M6951</guid>
      <dc:creator>AnonymousM</dc:creator>
      <dc:date>2018-12-07T16:10:59Z</dc:date>
    </item>
    <item>
      <title>Re: New APs take a DHCP lease when they are connected to our network and one of our new APs at a different location than our hivemanager also overrides the IP of our static DNS entry for the ap.</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/new-aps-take-a-dhcp-lease-when-they-are-connected-to-our-network/m-p/76153#M6952</link>
      <description>&lt;P&gt;Bump, problem is still ocurring.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Jan 2019 18:29:41 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/new-aps-take-a-dhcp-lease-when-they-are-connected-to-our-network/m-p/76153#M6952</guid>
      <dc:creator>AnonymousM</dc:creator>
      <dc:date>2019-01-03T18:29:41Z</dc:date>
    </item>
  </channel>
</rss>

