Hello,
I've recently noticed that ip pools are not being cleared after disconnect and ips stay reserved/I don't know why?!?!?/. So...everytime a user connects next ip is being chosen/not the free one/.Basicly that leads to filling the pools and mikrotik is choosing it's own pools/everytime I have to clear the ippool cache manually/.
Is that a known problem or I'm the first one with such question?

Work as designed!

first pool will give out all addresses (254,253,252,....4,3,2)
Then when it run out of addressees it will check for all free addressees
and the will make a next run only trough free addresses


I think this is the right way to do it - it would be much more expensive to check your pool each time.

If you don't like it you can use many pools and next-pool option. then It will jump to the next pool only when previous pool will be full

Work as designed!

first pool will give out all addresses (254,253,252,....4,3,2)
Then when it run out of addressees it will check for all free addressees
and the will make a next run only trough free addresses


I think this is the right way to do it - it would be much more expensive to check your pool each time.

If you don't like it you can use many pools and next-pool option. then It will jump to the next pool only when previous pool will be full

Hi,
I'm not talking about manually made ippools inside mikrotik.
I'm providing ospf to all my routers and I have made ippools using freeradius.
MikroTik router should select ips from my sql database and free the addresses after user disconnect/but it doesn't/.
rlm_ippool_tool -av rzpool1.ippool rzpool1.ipindex
NAS:XXX.XXX.XXX.XXX port:0xa0b - ipaddr:10.3.30.90 active:1 cli:0 num:1
NAS:XXX.XXX.XXX.XXX port:0xa24 - ipaddr:10.3.30.61 active:1 cli:0 num:1
NAS:XXX.XXX.XXX.XXX port:0xa1f - ipaddr:10.3.30.134 active:1 cli:0 num:1
NAS:XXX.XXX.XXX.XXX port:0xa28 - ipaddr:10.3.30.55 active:1 cli:0 num:1
NAS:XXX.XXX.XXX.XXX port:0xa10 - ipaddr:10.3.30.250 active:1 cli:0 num:1
NAS:XXX.XXX.XXX.XXX port:0xa19 - ipaddr:10.3.30.113 active:1 cli:0 num:1
NAS:XXX.XXX.XXX.XXX port:0x9e4 - ipaddr:10.3.30.221 active:1 cli:0 num:1
NAS:XXX.XXX.XXX.XXX port:0xa29 - ipaddr:10.3.30.175 active:1 cli:0 num:1
NAS:XXX.XXX.XXX.XXX port:0x32 - ipaddr:10.3.30.59 active:1 cli:0 num:1
NAS:XXX.XXX.XXX.XXX port:0xa1a - ipaddr:10.3.30.246 active:1 cli:0 num:1
NAS:XXX.XXX.XXX.XXX port:0xa0a - ipaddr:10.3.30.102 active:1 cli:0 num:1
NAS:XXX.XXX.XXX.XXX port:0xa1c - ipaddr:10.3.30.8 active:1 cli:0 num:1
NAS:XXX.XXX.XXX.XXX port:0xa2c - ipaddr:10.3.30.187 active:1 cli:0 num:1
NAS:XXX.XXX.XXX.XXX port:0x9f7 - ipaddr:10.3.30.245 active:1 cli:0 num:1
NAS:XXX.XXX.XXX.XXX port:0x36 - ipaddr:10.3.30.48 active:1 cli:0 num:1
NAS:XXX.XXX.XXX.XXX port:0xa27 - ipaddr:10.3.30.66 active:1 cli:0 num:1

[/quote]
Only 5 of these are currently in use the others remain ghosts.
Just to import that I don't have that problem on other linux/bsd powered devices.

I hope that you are just doing stupid mistake cause i am about to implement dynamic ips through radius as well

Do you have interim update interval set? maybe that is the problem.

Cheers
Michal