In our migration test bed from our antique radius to freeradius I seem to have issue with freeradius sql dishing out IP's... if I use ippool, sure works great, but our NAS's do this now and we are trying to move away to sql, which doesn't in fact doesn't seem to even look for it using radiusd -X We have populated radippool with pool name: 'main_pool', ' i.p.add.ress' added DEFAULT Pool-Name := main_pool
On 30/08/2015 15:43, Noel Butler wrote:
In our migration test bed from our antique radius to freeradius I seem to have issue with freeradius sql dishing out IP's... if I use ippool, sure works great, but our NAS's do this now and we are trying to move away to sql, which doesn't in fact doesn't seem to even look for it using radiusd -X
We have populated radippool with pool name: 'main_pool', ' i.p.add.ress'
added DEFAULT Pool-Name := main_pool
apologies sent too early, dumb webmail .. OK, we also included the fall through. added sqlippool to post-auth and accounting (strangely the conf file says use main_pool, but radiusd fails to run about no module/policy) is there something for v3.09 we are missing? Sorry for being a pain with questions but docs are highly lacking, and wiki (and googlefuing) seems mostly applicable to 2. No problems with auth as mentioned, just failure to dish out IP's. Cheere
On Aug 30, 2015, at 1:48 AM, Noel Butler <noel.butler@ausics.net> wrote:
Sorry for being a pain with questions but docs are highly lacking, and wiki (and googlefuing) seems mostly applicable to 2.
The virtual servers and "update" sections haven't really changed from v2 to v3.
No problems with auth as mentioned, just failure to dish out IP's.
So... what does the debug output say? This shouldn't be hard to post it. The FAQ, "man" pages, web pages, and messages daily on this list say to post the debug output. Alan DeKok.
On 30/08/2015 23:44, Alan DeKok wrote:
On Aug 30, 2015, at 1:48 AM, Noel Butler <noel.butler@ausics.net> wrote:
Sorry for being a pain with questions but docs are highly lacking, and wiki (and googlefuing) seems mostly applicable to 2.
The virtual servers and "update" sections haven't really changed from v2 to v3.
No problems with auth as mentioned, just failure to dish out IP's.
So... what does the debug output say? This shouldn't be hard to post it.
The FAQ, "man" pages, web pages, and messages daily on this list say to post the debug output.
Alan DeKok.
I never posted the debug output, because there was no reference to sqlippool in it, however, running -Xxxxxxxxx -l foo.txt I was able to see the problem, my scrollback only goes back 1K lines so I was missing the stuff that would have caught my eye in the first place and i wouldnt have needed to post, its resolved now our circa late 90's existing radius needed a framed-ip-address 255.255.255.254 as last entry, free radius, does not mandate it, so re-commented out that bit and all is well, assigning from general pool and also the statics works fine But have one more Q, my philosophy is only run what you must, so the inner-tunnel enabled-sites which makes note at the top being for testing, is only for testing? ie, we can disable it now things are running, or is it needed some other way? cheers
On Aug 30, 2015, at 9:55 PM, Noel Butler <noel.butler@ausics.net> wrote:
I never posted the debug output, because there was no reference to sqlippool in it,
Then it's not using SQL IP pools, is it?
But have one more Q, my philosophy is only run what you must, so the inner-tunnel enabled-sites which makes note at the top being for testing, is only for testing? ie, we can disable it now things are running, or is it needed some other way?
It's not needed for anything other than testing. Alan DeKok.
On 31/08/2015 22:21, Alan DeKok wrote:
On Aug 30, 2015, at 9:55 PM, Noel Butler <noel.butler@ausics.net> wrote:
I never posted the debug output, because there was no reference to sqlippool in it,
Then it's not using SQL IP pools, is it?
Yes it was and is, as I made it clear before, the output exceeded my scrollback, only when I pipped it all to file could I see everything , debug was 2198 lines, so I missed seeing 1198 of em :)
But have one more Q, my philosophy is only run what you must, so the inner-tunnel enabled-sites which makes note at the top being for testing, is only for testing? ie, we can disable it now things are running, or is it needed some other way?
It's not needed for anything other than testing.
Awesome, thanks
participants (2)
-
Alan DeKok -
Noel Butler