(RADIATOR) hrm.. dynaddress config issues..

[Hugh Irvine]

Hello Jeremy -

I suspect the problem is your definition for PoolHint:

     PoolHint            %{Reply:NAS-Identifier}

as there will not normally be a NAS-Identifier attribute in the reply packet 
that is going to be returned to the NAS.

You should probably do this instead:

     PoolHint            %{NAS-Identifier}

You may also find that it is much easier to do this as follows:

# define Client clauses with Identifiers

<Client 1.1.1.1>
	Identifier WA
	.....
</Client>

<Client 2.2.2.2>
	Identifier WA
	.....
</Client>

<Client 3.3.3.3>
	Identifier SA
	.....
</Client>

<Client 4.4.4.4>
	Identifier SA
	.....
</Client>

........

# define AuthBy DYNADDRESS with Client-Identifier as PoolHint

<AuthBy DYNADDRESS>
    Identifier          ADSLDYNADDRESS
    PoolHint            %{Client-Identifier}
    AddressAllocator    ADSLAllocator
</AuthBy>

# define AddressAllocator with AddressPool's 
# corresponding to each state (or whatever)

<AddressAllocator SQL>
    Identifier  ADSLAllocator
    Log         DebugDump #we're dubugging,  so watch it all
    DBSource    dbi:mysql:dbname=radius;host=somehost
    DBUsername  xxxxxxxx
    DBAuth      xxxxxxxx
    DefaultLeasePeriod 3600
    LeaseReclaimInterval 1800
    FindQuery   select TIME_STAMP, YIADDR, SUBNETMASK from RADPOOL \
                where POOL='%0' and STATE=0 order by TIME_STAMP LIMIT 1
    <AddressPool WA>
        Range 192.1.1.1 192.1.1.50
    </AddressPool>
    <AddressPool SA>
        Range 192.1.2.1 192.1.2.50
    </AddressPool>
    ......
</AddressAllocator>

.......


regards

Hugh


On Wed, 8 May 2002 13:25, Jeremy Burton wrote:
> Hi All,
>   I'm trying to sort out some dynamic address allocation issues. Due to our
> broadband wholesaler having issues with the allocation of IP addresses,
> they've allowed us to allocate them to our customers. The way we need to do
> the alloaction is to have a pool for each state. Fairly easy, or so I
> thought. There is no easy way of telling which state the customer is in
> other than the NASIP of the request - each state has fixed NASIPs.
> So the way I had figured I would do this is have two tables for the
> DYNADDRESS:
> 1. RADPOOL as shipped.
> 2. NASPOOL which links POOL in RADPOOL to a NAS-Identifier.
>
> So I have:
>
> # autoallocate IPS
> <AuthBy DYNADDRESS>
>     Identifier          ADSLDYNADDRESS
>     PoolHint            %{Reply:NAS-Identifier}
>     AddressAllocator    ADSLAllocator
> </AuthBy>
>
> <AddressAllocator SQL>
>     Identifier  ADSLAllocator
>     Log         DebugDump #we're dubugging,  so watch it all
>     DBSource    dbi:mysql:dbname=radius;host=somehost
>     DBUsername  xxxxxxxx
>     DBAuth      xxxxxxxx
>     DefaultLeasePeriod 3600
>     LeaseReclaimInterval 1800
>     FindQuery   select TIME_STAMP, YIADDR, SUBNETMASK from RADPOOL, NASPOOL
> \ where RADPOOL.POOL=NASPOOL.POOL \
>                 and STATE=0 \
>                 and NASIDENTIFIER = '%N' \
>                 order by TIME_STAMP \
>                 LIMIT 1
>     <AddressPool TESTING1>
>         Range 192.1.1.1 192.1.1.50
>     </AddressPool>
>     <AddressPool TESTING2>
>         Range 192.1.2.1 192.1.2.50
>     </AddressPool>
> </AddressAllocator>
>
> In theory, this should work i would thik.... However, in the logfile, i
> get:
>
> Wed May  8 13:12:22 2002: DEBUG: Handling with Radius::AuthDYNADDRESS
> Wed May  8 13:12:22 2002: DEBUG: No PoolHint found. No address will be
> allocated
>
> Any ideas? thanks
>
> Jeremy

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.