On Thu, Nov 28, 2002 at 10:54:51AM +0200, Kostas Kalevras wrote:
> > May I release similar assignment with radius+rlm_ippol ???
> 
> Just put the corresponding values in range-start and range-stop.
> The netmask is only used to find the network and broadcast addresses of the
> range given.

Thanks you. Your explain very help me.
But I have some trouble with routing...
NAS - Lucent MAX6000
If I write user-profile like this:
===users===
user_name .......... Pool-Name := "main_pool"
===========
IP address is assign, but in routing table it does not present...

At with configuration:
===users===
user_name .......... Pool-Name := "main_pool"
        Framed-IP-Netmask = 255.255.255.255
===========

In routing table IP-address present like ip.add.res.s/32 i.e everuthing
is ok...

Thank you

> No you don't need to. The only requirment is that if you change the range-start
> and/or range-stop parameters you should then delete the db files.

And this moment also very important.
My changes does not have power, if I did not remove db*-files before
restarting radius.

> > I have bad english :(
> > I may example of config files put here, if I can release _not_ CLASSLESS IP 
>address pool...
> 
> Just explaining what is missing in the documentation will also do the job just
> fine.

Some moment I decribe above.
1. rm db*
2. Framed-IP-Netmask on reply-attribute (May be only MAX?)
3. May be in future release of rlm_ippool add parameter like 
   "debug = yes/no" or like "logging_debug = yes/no" ??

-- 
WBR, Vitaliy Karlov [KV1670-RIPE]

- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to