MonsterOpsIP Pools¶
Overview¶
IP Pools manage the radippool table — the ranges of framed IP addresses FreeRADIUS hands out
to subscribers at authentication. A group or user references a pool by name (via a Framed-Pool
reply attribute), and FreeRADIUS leases an address from it for the session.
Where things are¶
- Pool list — each pool with its occupancy (leased vs. total) so you can see how full it is at a glance.
- Pool detail — the CIDR ranges that make up the pool, and the individual leases, including which are currently allocated and to whom.
- Actions — add a CIDR/range to a pool, and release a stuck lease that a client never gave back.
Common tasks¶
- Create a pool — add a named pool and one or more CIDR ranges (e.g.
10.10.0.0/22). - Hand a pool to a plan — set
Framed-Pool = <pool-name>as a reply attribute on the relevant Group. - Reclaim a stuck address — find the lease in the pool detail and release it; useful after a NAS reboot leaves phantom allocations.
- Grow a pool — add another CIDR range before it fills.
Problems you may hit¶
Pool exhausted — users get no address
If occupancy is at 100%, new sessions can't get a Framed-IP-Address. Add a range, or release
stale leases. Stuck leases are common after a NAS loses power without sending accounting-stop.
- Addresses never free up — accounting-stop packets aren't reaching FreeRADIUS, so leases look permanently held. Confirm accounting works (see Sessions); a scheduled stale IP sweep (Scheduler) can clean these automatically.
- User gets no IP despite a free pool — the
Framed-Poolname on the group/user must exactly match the pool name.