ARP and DHCP are two different things. Assuming you're correctly blocking the DHCP server for answering or hearing discoveries, ARP is still going to happen and the (guessing here) Linksys Wifi Router is plugged in backwards answering ARP for the address it is listening on.
Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Wed, Jan 26, 2011 at 2:44 PM, Andy Trimmell <[email protected]>wrote: > We’re blocking DHCP traffic on mikrotik client units. We’ve found a rogue > dhcp that I’ve talked about the last couple weeks in a few threads. I found > the unit. We’re blocking the 67 port like we’re suppose to but unit are > still attempting to connect to the DHCP behind it. Should I be blocking 67 > and 68 to alleviate this? The clients need to get an IP with the tower dhcp > server but I don’t want people’s routers giving out responses. > > > > The counters are going up but im still seeing the 192.168.1.1 IP on the ARP > table and the only units on the tower having a problem is these 320 units > but it’s the rogue server behind one of these mikrotiks. > > > > Irritating. > > > > Andy Trimmell > > Network Administrator > > [email protected] > > 317.831.3000 ext 211 > > > > > > > -------------------------------------------------------------------------------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > > -------------------------------------------------------------------------------- > > WISPA Wireless List: [email protected] > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ >
-------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: [email protected] Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
