Ok,
I implemented a list. Everytime a user connects he gets the least number
which is free or a new number is added to the list.
But how do you want to create the ip address pool?
Every client needs two ip addresses for one interface.
I get the framed ip address from the radius answer packet.
The
Am Dienstag, den 31.05.2005, 10:09 + schrieb Ralf Lübben:
> If a client connects the nas port number is locked , if a client disconnect
> the port number is freed.
> A new client will always get the least number of the array.
>
> Would this behaviour ok?
Yes. That would be OK.
> How many
lar...@gullik.net (Lars Gullik Bjønnes) writes:
| Kelledin writes:
>
| | Hi all, LZO 2.00 was just released, and it has a few API changes.
| | Specifically the worst-case expansion formula prescribed by LZO.FAQ
| | has changed, and headers now get their own lzo/ directory.
>
| I also thought th
Ok,
I think I understand the problem.
If a client send no stop packet the ip address will never be freed if the
nas-port is never used again.
So if a other client connects with the same nas port number, of the client
which has not send the stop packet, the freeradius server will free the ip
ad
Am Montag, den 30.05.2005, 19:49 + schrieb Ralf Lübben:
> I have still one question about the NAS-Port attribute. At the moment the
> port number is increment for every user, but never decremt.
> Will this be a problem with freeradius? Must the number be in a special
> range, maybe for assignm
Kelledin writes:
| Hi all, LZO 2.00 was just released, and it has a few API changes.
| Specifically the worst-case expansion formula prescribed by LZO.FAQ
| has changed, and headers now get their own lzo/ directory.
I also thought that the license changed. Isn't this the case?
--
Lgb
