I have been developing my new AAA and BW Management system using Mikrotiks and RouterOS and ran into something odd.

When first on the DEV, I was running ROS 2.9.29, Using the MT's to do my DHCP requests via a Radius Connection which worked exactly like we want.

[admin@MikroTik] ip dhcp-server> print detail
Flags: X - disabled, I - invalid
0 name="Hotspot2DHCP" interface=ether2 lease-time=3d address-pool=static-only bootp-support=static
add-arp=yes authoritative=after-2sec-delay use-radius=yes

There is no actual address pool, and test client machine gets their IP and surfs as expected. Now that 2.9.30 is out, that no longer works, to get it to work I need to add in IP Pool for the range.

Is this considered how it SHOULD be working or is there a new bug ? Any more details i need to post on this ? The dhcp-server config is identicle between 2.9.30 and 2.9.29.

Anyone else have experience with using DHCP and Radius ?

I'm using Freeradius if that matters any.

Does mikrotik have any thoughts ?

I've setup another MT for production, and its now doing the same thing but now regardless if I've got a pool in or not. Just no DHCP via Radius. I've been mulling over the logs, and I'm getting Access-Accept replys from Radius, but the MT doesnt' appear to do anything with them. So I'm pretty confident that the issue is on the MT.

Oh yes, Hotspot authentication using same Mac Address and radius server works correctly. I'll try rolling back to 2.9.29 to see if it makes a difference on this production MT.