ippool behavior
Peter Manckok
peter_manckok at yahoo.es
Wed Jan 25 15:51:47 CET 2006
Hy all :-)
I am introducing in the RADIUS (and FreeRadius) world
since two months ago. And now I am doing tests trying
to understand all the possibilities offered by
FreeRadius (congratulations to all the community, I am
really impressed).
Now, I am testing the rlm_ippool module. I have been
looking for documentation about this module, but I
have only found information in the radiusd.conf file
and in some posts in the forum so excuse me if my
nexts questions are stupid or yet answered.
------------
Well, my configuration is:
* In radiusd.conf I have:
....
modules {
...
ippool main_pool {
range-start = 192.168.1.1
range-stop = 192.168.3.254
netmask = 255.255.255.0
cache-size = 800
session-db = ${raddbdir}/db.ippool
ip-index = ${raddbdir}/db.ipindex
override = no
maximum-timeout = 0
}
...
}
...
accounting {
detail
unix
radutmp
main_pool
}
...
post-auth {
main_pool
...
}
* In users file I have:
DEFAULT Auth-Type := Accept, Pool-Name := "main_pool"
Service-Type = Framed-User,
Framed-Protocol = PPP
* I use the radclient utility to test the mod
$ radclient -f Attributes localhost auth testing
Received response ID 42, code 2, length = 44
Service-Type = Framed-User
Framed-Protocol = PPP
Framed-IP-Address = 192.168.3.181
Framed-IP-Netmask = 255.255.255.0
And in the Attributes file I have:
User-Name = "telemati"
User-Password = "telemati"
NAS-IP-Address = aa.bb.cc.dd
NAS-Port = 55
My debugs are:
modcall: entering group post-auth for request 0
rlm_ippool: Searching for an entry for nas/port:
aa.bb.cc.dd/55
rlm_ippool: Allocating ip to nas/port: aa.bb.cc.dd/55
rlm_ippool: num: 1
rlm_ippool: Allocated ip 192.168.3.181 to client on
nas aa.bb.cc.dd,port 55
modcall[post-auth]: module "main_pool" returns ok for
request 0
modcall: group post-auth returns ok for request 0
Sending Access-Accept of id 42 to 127.0.0.1:35183
Service-Type = Framed-User
Framed-Protocol = PPP
Framed-IP-Address = 192.168.3.181
Framed-IP-Netmask = 255.255.255.0
--------------
Well, my questions are:
1) Is this a correct behavior?
2) The FreeRadius assigns the IP 192.168.3.181. Why
does not it start assigning the IP 192.168.1.1?
3) If I send another Access-Request packet with a
different NAS-Port attribute, I observe that
FreeRadius assigns an IP that is not consecutive with
regard to the previous IP. Is this a correct behavior
or am I doing something wrong?
4) Which is the consequence of deleting the db.ippool
and db.ipindex files?
5) How does the rlm_ippool module free the IP address
assigned?
Sorry about the large of the mail (and my poor
english)
Regards,
Peter
______________________________________________
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
More information about the Freeradius-Users
mailing list