In my case this actually turned out to be a user error (on my part). I'd failed to see these lines in the release note: ) radius - added "require-message-auth" option that requires "Message-Authenticator" in received Access-Accept/Challenge/Reject messages; ) radius - include &qu...

Is any config to disable "require-message-auth" option ?

Yes - set require-message-auth (in the server definition in the RADIUS menu) to 'none'.

This sound identical to a problem I very occasionally ran into on v6 (that was never solved to my knowledge).

I was kind of hoping it had magically disappeared in v7 - I guess not though!

In fairness I think this is the first ever issue I've had with Hotspot Radius in 10+ years of using Mikrotiks.

I have the same issue with the Hotspot using Radius on 7.15.

I've confirmed via Wireshark that 'Access-Accept' packets are being received by the Mikrotik, yet the 'Accepts' on the Mikrotik shows 0 (and the Hotspot doesn't auth users).

The thing is that it does cause a problem on sites where you have a high 'churn' of users. When conflict detection is turn on the DHCP server (which is always a good idea) it sends an ARP request for the IP it is about to hand out. If the entry already exists in the ARP table it doesn't even bother ...

I've now just seen it on a router without proxy-arp configured (in fact with a fairly simple config), so I think the proxy-arp connection is perhaps a red-herring.... I too have had to add a scheduled script to clear entries every night.... Not ideal, but it'll do for now. I can't believe 100s of pe...

Still seeing this on 7.10.2. I haven't managed to re-create it on a minimal setup yet, but I'm wondering if it's related to setting arp=proxy-arp. Although this isn't set on the vlans that are experiencing this lack of ARP clearing, it is set on another interface on the system. That's the only thing...

Hi Folks, I seem to be having an issue with the DNS forwarding process on a CCR1072 running 6.49.8. The symptoms are that it stops answering DNS requests. Attempts to interact with DNS settings either in WinBox or on the CLI fail: [xxxx@yyy] /ip dns> print action timed out - try again, if error cont...

Still seeing this on 7.9.2 (will let you know if 7.10 still has this issue)....

Has anyone else seen this?

I can't really believe we're the only ones....