SQLIPPOOL problem
- To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org>
- Subject: SQLIPPOOL problem
- From: "Guilherme Franco" <guilhermefranco@gmail.com>
- Date: Thu, 26 Oct 2006 19:50:16 -0300
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=WRfx6KukihOYm+99DWLFVsS6OALOdizfp6o3rBIBM4gHw5wj/p4N6JXA9OMNMrrF4gRaZaKcW/XrSQ2VSfY3OIoD+Sdd4sFP85NcD0Sy5Ez4vM66W2kiM/rA6dKjntZGC89U7bbhKjPHnF/3fvzhryCA5mQ8+gNhen8B8B0srI4=
- Reply-to: FreeRadius users mailing list <freeradius-users@lists.freeradius.org>
Hi,
This is very important, please.
In ippool module I can use two or more pools just by setting
ippool POOL1{...}
ippool POOL2{...}
In SQLIPPOOL, I know that I can create as many pools as I wan't but I
need to treat that pools differently, say, POOL1 assigns static IPs
and POOL2 dynamic ones, or POOL1 is in databaseX and POOL2 in
databaseY.
So I did this sqlippool.conf:
sqlippool POOL1{...}
sqlippool POOL2{...}
And then in radiusd.conf
post-auth{
POOL1
POOL2
}
But the user that have Pool-Name := POOL2 in radcheck receives the IP
(because POOL2 exists in the database), but it's not treated by the
POOL2 instance created in sqlippool.conf (radiusd -X shows that both
module POOL1 and POOL2 are instantiated), it's being treated by the
POOL1 instance.
So, how can I tell that for users that belong to POOL2 use the POOL2
module, instead of POOL1 and vice-versa?
Thank you.
This archive was generated by a fusion of
Pipermail (Mailman edition) and
MHonArc.