Re: (ASCEND) Ascend TNT and large IP-Pools

[Peter Lalor <plalor@infoasis.com>]

>From: Oliver Stettner <os@landshut.org>
>
>Meanwhile I found a solution, but it's not usefull for me.
>
>>  > So in our TNT we want to have two IP-Pools, like this (the
>>  > IP-addresses are just examples):
>>  >
>>  > pool-base-address 1 = 192.168.0.1
>>  > assign-count 1 = 1022
>>  >
>>  > That would be the network 192.168.0.0/22, or in other words:
>>  > Network:   192.168.0.0
>>  > Netmask:   255.255.252.0
>>  > Broadcast: 192.168.3.255
>>  >
>>  > pool-base-address 2 = 172.16.0.1
>>  > assign-count 2 = 1022
>>  >
>>  > And this would be the network 172.16.0.0/22, or in other words:
>>  > Network:   172.16.0.0
>>  > Netmask:   255.255.252.0
>>  > Broadcast: 172.16.3.255
>
>You must use the Ascend radiusd and the Ascend radipad (both from
>ftp.ascend.com). Radipad is a Radius IP-Address Daemon and can manage
>different IP-Pools for many TNTs. It's described in the Ascend
>"Network Configuration Guide" and in the Ascend "RADIUS Configuration
>Guide".

<snip>

>The reason I can't use it: you *have to* use the Ascend radiusd. But
>we want the Merit radiusd for roaming (differnt realms and
>distributed authentication).

You can set up multiple separate chains locally, or in RADIUS as you 
describe. Either way, just leave a null pool definition between pool 
chains, and the TNT will not jump to the next pool. Presto: multiple 
separate chained IP pools.

The TAOS 8.0.1 docs describe it clearly, but the feature was 
available starting in 7.2.0.
-- 

Peter Lalor           Infoasis
plalor@infoasis.com   http://www.infoasis.com/

"Where's my burrito?" -- Homer
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>