I have not. These are PTPs between routed interfaces. Traffic goes over the link without a problem. Routed management traffic (in-band only) to the radios doesn't generate any errors. It's only radio to radio packets that seems to trigger it. I can run a ping, telnet or ssh session between the radios and I get Rx FCS and Code errors on both ends. I also have flow control disabled on everything.

So, you obviously know more about these things than I do but... I've mentioned this before, if I'm managing a radio directly connected to a router port (which holds the IP gateway), that traffic hits the other side, which tells me these things don't have a MAC table/FDB and/or are not store-and-forward switching. Could it be just a MikroTik thing, sure, I don't know, I don't have any other gear to test with. But this doesn't happen with the same MikroTik's and any other radios. Ubiquiti M's, Cambium, Trango licensed, etc. Just sayin'.

On 11/6/2014 8:51 PM, Chuck Macenski via Af wrote:
Have you tried putting a non-Microtik switch in line to see if that is part of the equation?

Chuck

On Thu, Nov 6, 2014 at 4:59 PM, George Skorup (Cyber Broadcasting) via Af <[email protected] <mailto:[email protected]>> wrote:

    Found this interesting. I have some AF24's on 2.0 and AF5's on
    2.2-beta3. They work fine. If I do a Tools > Discovery, the MT
    ethernet counters on both sides will increment FCS and Code
    errors. Same thing happens if I run some pings between the radios
    (not router to router, radio to radio). I'm guessing this because
    of the switching method the AF's use (cut-through?).



Reply via email to