Re: (RADIATOR) AuthBy DYNADDRESS and Emerald/Platypus 3.0

2002-10-28 Thread Hugh Irvine
Hello Matt - It might be simplest to define an additional AuthBy SQL clause to do the query and assign the returned value to the PoolHint attribute. Then you just have to define your AddressPool's with those values directly. Otherwise you can specify your own AuthSelect clause and the appropr

(RADIATOR) AuthBy DYNADDRESS and Emerald/Platypus 3.0

2002-10-28 Thread Matthew Taylor
I wonder if someone might be able to suggest a simple way to trigger the use of an address allocator pool, based on when the customer.accttype field in Platypus (running in RADIUSNT mode) contains one of a few values? I need a way to set PoolHint for a couple of different values of the accttype fi

(RADIATOR) AuthBy DYNADDRESS and Emerald/Platypus 3.0

2002-10-28 Thread matt
I wonder if someone might be able to suggest a simple way to trigger the use of an address allocator pool, based on when the customer.accttype field in Platypus (running in RADIUSNT mode) contains one of a few values? I need a way to set PoolHint for a couple of different values of the accttype fi

(RADIATOR) AuthBy DYNADDRESS and Emerald/Platypus 3.0

2002-10-28 Thread Matthew Taylor
I wonder if someone might be able to suggest a simple way to trigger the use of an address allocator pool, based on when the customer.accttype field in Platypus (running in RADIUSNT mode) contains one of a few values? I need a way to set PoolHint for a couple of different values of the accttype fi