(RADIATOR) BindAddress multiple IPs?

2002-10-28 Thread Jeremy Hinton
Hugh & crew, From reading the docs, and my own testing, it looks like the BindAddress parameter can only accept a single IP. As a result, it looks like you're limited to either having radiator respond on all IPs, or just on one. If this is not the case, someone please feel free to correct me.

Re: (RADIATOR) Acct-Session-Id Error

2002-10-28 Thread Doug Clements
That did not seem to do much.. I'm still getting the errors. The secondary problem we have is that since Radiator is assuming the Acct-Session-Id is 0, then people for whom we proxy radius to are getting 0 for this value, and can't track their users. Is there a way to force Radiator to "cast" t

(RADIATOR) using the already connected DB refs

2002-10-28 Thread Martin Edge
Hey Guys, Little curious, I need to perform an Extra SQL query while processing RADIUS requests, and set the value to an internal Radiator variable, it comes from the same database, so I was wondering how one would utilise the existing DB connection easily, without having to spawn an additional on

Re: (RADIATOR) using the already connected DB refs

2002-10-28 Thread Hugh Irvine
Hello Martin - I think from the code below you are referring to the session database? In any case, my answer holds true for an AuthBy SQL as well. You should have a look at the example code in "goodies/hooks.txt", the reply hook that does dynamic address allocation. This is how to find a spec

Re: (RADIATOR) Acct-Session-Id Error

2002-10-28 Thread Hugh Irvine
Hello Doug - Have you restarted Radiator to re-read the dictionary? Are you sure you have changed the correct dictionary? I am actually surprised that Radiator is trying to use Acct-Session-Id as an integer in any case - it should be a string. And changing the dictionary definition results in

Re: (RADIATOR) BindAddress multiple IPs?

2002-10-28 Thread Hugh Irvine
Hello Jeremy - I have copied this mail to Mike, but he is travelling until next week. My understanding is that this is a lower-level problem than Perl can deal with. Mike will be able to clarify I'm sure. regards Hugh On Tuesday, October 29, 2002, at 02:23 AM, Jeremy Hinton wrote: Hugh &

(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

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