Trouble "SQL Based IP Pool"
tnt at kalik.net
Wed May 7 23:05:24 CEST 2008
>^^ It's not ippool.sql - we're talking about the RADIPPOOL table - No I
>haven't changed this - go and check it by
>And besides that I'm not using "ippool.sql" but instead of I'm using
>"postgresqlippool.conf" because I'm using PostgreSQL as DB Server.
You are correct. Schema in 1.1.7 is broken and will not work as
documented. I have attached postgre ippool.sql schema from 2.0.4. That
will correct the input errors. It's also indexed so it should work
>Didn't you read what I wrote? ; ) It won't work , because there are
>fields which can't be NULL ... for example "pool_key" and so on
>proper shema won't work.
This one should.
>>> ^^ 2. What is expiry_time good for if there is already an
>>> lease-duration = 3600 configured in the postgresqlippool.conf? And why
>>> do I get forced to use unix timestamp instead of using a simple time in
>>> secounds when it'll be expired?
>> Seconds from when? You do need a timestamp for lease start then.
>^^ ah, ok that makes sence ; ) but untill now I'm only able to tell the
>DB a fix Timestamp like 2008-12-31 11:15:00 but how do I change that the
>server is picking up the actual time everytime somebody gets an IP.
>Might there be a special variable for our case?
start-update query should do that.
Kalik Informatika ISP
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
More information about the Freeradius-Users