<?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: How to block Rogue DHCP Servers on the connected clients in Aerohive Migrated Content</title>
    <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/how-to-block-rogue-dhcp-servers-on-the-connected-clients/m-p/82538#M9522</link>
    <description>&lt;P&gt;Your source and destination ports look good, this is traffic from a dhcp server back to the client. So creating a rule like this is straight forward - the trick is to apply it on traffic FROM any client, and not the other way.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Classic: From-Access&lt;/LI&gt;&lt;LI&gt;NG: Outbound Traffic&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On NG it should look like this:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="7054be361cbe40a888455b5579cb2484_0690c000006V0iXAAS.png"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/5892i5B863D8C66FBD9D1/image-size/large?v=v2&amp;amp;px=999" role="button" title="7054be361cbe40a888455b5579cb2484_0690c000006V0iXAAS.png" alt="7054be361cbe40a888455b5579cb2484_0690c000006V0iXAAS.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I still highly recommend to test this first.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;</description>
    <pubDate>Tue, 24 Apr 2018 16:27:00 GMT</pubDate>
    <dc:creator>AnonymousM</dc:creator>
    <dc:date>2018-04-24T16:27:00Z</dc:date>
    <item>
      <title>How to block Rogue DHCP Servers on the connected clients</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/how-to-block-rogue-dhcp-servers-on-the-connected-clients/m-p/82535#M9519</link>
      <description>&lt;P&gt;Looking to block DHCP Offers from connected clients.&lt;/P&gt;&lt;P&gt;From: Any (client)&lt;/P&gt;&lt;P&gt;To: Any&lt;/P&gt;&lt;P&gt;Source port: 67&lt;/P&gt;&lt;P&gt;Destination Port: 68&lt;/P&gt;&lt;P&gt;Protocol : UDP&lt;/P&gt;&lt;P&gt;Action: Block&lt;/P&gt;&lt;P&gt;Everything else: Permit&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can i have some guidance on how to set this up, so I don't also block DHCP Offers from our DHCP Server?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 20 Apr 2018 16:04:41 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/how-to-block-rogue-dhcp-servers-on-the-connected-clients/m-p/82535#M9519</guid>
      <dc:creator>george_margarit</dc:creator>
      <dc:date>2018-04-20T16:04:41Z</dc:date>
    </item>
    <item>
      <title>Re: How to block Rogue DHCP Servers on the connected clients</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/how-to-block-rogue-dhcp-servers-on-the-connected-clients/m-p/82536#M9520</link>
      <description>&lt;P&gt;My thought is block interstation traffic between wireless clients or using provided example allow DHCP requests to authorized DHCP servers and block all other DHCP traffic while permitting everything else.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Apr 2018 19:34:51 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/how-to-block-rogue-dhcp-servers-on-the-connected-clients/m-p/82536#M9520</guid>
      <dc:creator>sderikonja1</dc:creator>
      <dc:date>2018-04-20T19:34:51Z</dc:date>
    </item>
    <item>
      <title>Re: How to block Rogue DHCP Servers on the connected clients</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/how-to-block-rogue-dhcp-servers-on-the-connected-clients/m-p/82537#M9521</link>
      <description>&lt;P&gt;Enable DHCP snooping on your switches.  You mark trusted ports where DHCP is allowed, such as routers, uplinks, trunk ports, and DHCP server location.  The configuration varies from vendor to vendor.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Apr 2018 21:16:05 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/how-to-block-rogue-dhcp-servers-on-the-connected-clients/m-p/82537#M9521</guid>
      <dc:creator>jose_gonzalez</dc:creator>
      <dc:date>2018-04-20T21:16:05Z</dc:date>
    </item>
    <item>
      <title>Re: How to block Rogue DHCP Servers on the connected clients</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/how-to-block-rogue-dhcp-servers-on-the-connected-clients/m-p/82538#M9522</link>
      <description>&lt;P&gt;Your source and destination ports look good, this is traffic from a dhcp server back to the client. So creating a rule like this is straight forward - the trick is to apply it on traffic FROM any client, and not the other way.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Classic: From-Access&lt;/LI&gt;&lt;LI&gt;NG: Outbound Traffic&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On NG it should look like this:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="7054be361cbe40a888455b5579cb2484_0690c000006V0iXAAS.png"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/5892i5B863D8C66FBD9D1/image-size/large?v=v2&amp;amp;px=999" role="button" title="7054be361cbe40a888455b5579cb2484_0690c000006V0iXAAS.png" alt="7054be361cbe40a888455b5579cb2484_0690c000006V0iXAAS.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I still highly recommend to test this first.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Apr 2018 16:27:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/how-to-block-rogue-dhcp-servers-on-the-connected-clients/m-p/82538#M9522</guid>
      <dc:creator>AnonymousM</dc:creator>
      <dc:date>2018-04-24T16:27:00Z</dc:date>
    </item>
    <item>
      <title>Re: How to block Rogue DHCP Servers on the connected clients</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/how-to-block-rogue-dhcp-servers-on-the-connected-clients/m-p/82539#M9523</link>
      <description>&lt;P&gt;Thanks Carsten.&lt;/P&gt;&lt;P&gt;It's only been a week using Aerohive and navigating through the GUI is still a tricky.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have created that exact policy on your screenshot, but was finding tricky to make sure where to 'apply' this and the User Profiles (IP Firewall -&amp;gt; From-access) is the answer here. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As a follow up, do we have an option to similarly block IPv6 Router-Advertisements?&lt;/P&gt;&lt;P&gt;It's not on the list of network services (under that name at least).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Apr 2018 17:34:05 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/how-to-block-rogue-dhcp-servers-on-the-connected-clients/m-p/82539#M9523</guid>
      <dc:creator>george_margarit</dc:creator>
      <dc:date>2018-04-24T17:34:05Z</dc:date>
    </item>
    <item>
      <title>Re: How to block Rogue DHCP Servers on the connected clients</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/how-to-block-rogue-dhcp-servers-on-the-connected-clients/m-p/82540#M9524</link>
      <description>&lt;P&gt;Ah, that ICMPv6 / Multicast, which is a bit tricky with Aerohive... I suggest to open a new thread explicitly for this topic. Hopefully someone else will jump on it &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Apr 2018 17:57:28 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/how-to-block-rogue-dhcp-servers-on-the-connected-clients/m-p/82540#M9524</guid>
      <dc:creator>AnonymousM</dc:creator>
      <dc:date>2018-04-24T17:57:28Z</dc:date>
    </item>
    <item>
      <title>Re: How to block Rogue DHCP Servers on the connected clients</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/how-to-block-rogue-dhcp-servers-on-the-connected-clients/m-p/82541#M9525</link>
      <description>&lt;P&gt;Cool, thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Apr 2018 18:12:50 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/how-to-block-rogue-dhcp-servers-on-the-connected-clients/m-p/82541#M9525</guid>
      <dc:creator>george_margarit</dc:creator>
      <dc:date>2018-04-24T18:12:50Z</dc:date>
    </item>
    <item>
      <title>Re: How to block Rogue DHCP Servers on the connected clients</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/how-to-block-rogue-dhcp-servers-on-the-connected-clients/m-p/82542#M9526</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Have you tried running a rogue DHCP server?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In the feature branch of HiveOS, you should observe enabled by default:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;forwarding-engine dhcp-shield enable&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;forwarding-engine arp-shield enable&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;These have to be switched off by supplemental CLI if they are not wanted.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Nick&lt;/P&gt;</description>
      <pubDate>Wed, 25 Apr 2018 16:30:54 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/how-to-block-rogue-dhcp-servers-on-the-connected-clients/m-p/82542#M9526</guid>
      <dc:creator>nlowe</dc:creator>
      <dc:date>2018-04-25T16:30:54Z</dc:date>
    </item>
  </channel>
</rss>

