<?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: IP-MAC CONFLICT:  Conflict in ip-mac binding between packet and snoop table data in ExtremeWireless (WiNG)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-wing/ip-mac-conflict-conflict-in-ip-mac-binding-between-packet-and/m-p/22333#M1743</link>
    <description>Where ever a static ip address is located, it has to be configured as a trusted port.&lt;BR /&gt;
I always recommend configuring the ports of any AP into a trusted state.&lt;BR /&gt;
All it takes is for someone to assign a static IP to a wireless NIC and the port is locked down&lt;BR /&gt;
 Been there, seen that&lt;BR /&gt;
Jason Parker</description>
    <pubDate>Thu, 28 Jan 2016 03:30:00 GMT</pubDate>
    <dc:creator>Jason_Parker</dc:creator>
    <dc:date>2016-01-28T03:30:00Z</dc:date>
    <item>
      <title>IP-MAC CONFLICT:  Conflict in ip-mac binding between packet and snoop table data</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/ip-mac-conflict-conflict-in-ip-mac-binding-between-packet-and/m-p/22332#M1742</link>
      <description>The wireless on our AP-4511's keep going in and out. After checking the logs I see hundreds of ip-mac conflicts. For example:&lt;BR /&gt;
&lt;BR /&gt;
Jan 26 15:57:29 192.168.3.177 2014-07-20T18: 52:30.%02u-04:00 ap4511-63DFFC %DATAPLANE-4-IPMACCONFLICT: IP-MAC CONFLICT: Conflict in ip-mac binding between packet and snoop table data : Vlan = 1, Pkt Src Mac: C0-BD-D1-26-56-29, Pkt Dst Mac: 00-04-96-52-36-EF, Pkt Dst IP : 192.168.10.3, Snoop Table Mac: 4C-EB-42-82-2C-CE, Snoop Table IP: 192.168.10.3 .&lt;BR /&gt;
&lt;BR /&gt;
192.168.10.3 is our DNS server&lt;BR /&gt;
&lt;BR /&gt;
The snoop table MAC is one of our laptops. That laptops network settings all check out. It still appears in the logs when I disable that NIC too. We have a master AP as a dhcp server.  &lt;BR /&gt;
&lt;BR /&gt;
What could be causing this?  This one laptop seems to be the culprit, but it looks like it is preventing other machines from getting to the DNS.</description>
      <pubDate>Wed, 27 Jan 2016 23:29:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/ip-mac-conflict-conflict-in-ip-mac-binding-between-packet-and/m-p/22332#M1742</guid>
      <dc:creator>Paul_Como</dc:creator>
      <dc:date>2016-01-27T23:29:00Z</dc:date>
    </item>
    <item>
      <title>RE: IP-MAC CONFLICT:  Conflict in ip-mac binding between packet and snoop table data</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/ip-mac-conflict-conflict-in-ip-mac-binding-between-packet-and/m-p/22333#M1743</link>
      <description>Where ever a static ip address is located, it has to be configured as a trusted port.&lt;BR /&gt;
I always recommend configuring the ports of any AP into a trusted state.&lt;BR /&gt;
All it takes is for someone to assign a static IP to a wireless NIC and the port is locked down&lt;BR /&gt;
 Been there, seen that&lt;BR /&gt;
Jason Parker</description>
      <pubDate>Thu, 28 Jan 2016 03:30:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/ip-mac-conflict-conflict-in-ip-mac-binding-between-packet-and/m-p/22333#M1743</guid>
      <dc:creator>Jason_Parker</dc:creator>
      <dc:date>2016-01-28T03:30:00Z</dc:date>
    </item>
  </channel>
</rss>

