I'm wondering if anyone else uses action=arp-reply in the bridge NAT section. I don't like using obscure features with MT for fear that they'll randomly remove it one day. However, since that post they appear to have added a rule to match gratuitous ARP, which could greatly simplify my config. I haven't tested it yet though.
-Kristian On Wed, 2011-01-26 at 15:48 -0500, Josh Luthman wrote: > Not sure exactly what you're asking. I did put a bridge filter on the > MT AP to stop SM to SM communication, yes. > > Josh Luthman > Office: 937-552-2340 > Direct: 937-552-2343 > 1100 Wayne St > Suite 1337 > Troy, OH 45373 > > > On Wed, Jan 26, 2011 at 3:04 PM, Kristian Hoffmann > <[email protected]> wrote: > Although it's a bit of work to get setup, and it helps to have > scripts > and automated provisioning to keep everything organized, we > haven't had > any problems with rouge DHCP since implementing it... > > http://www.butchevans.com/pipermail/mikrotik/2009-November/001178.html > > Josh, did you end up implementing something like this > yourself? > > > -Kristian > > > On Wed, 2011-01-26 at 14:44 -0500, Andy Trimmell 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/ > > > -------------------------------------------------------------------------------- > 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/
