RE: FreeRADIUS and Postgres annoyance

2006-08-29 Thread Santiago Balaguer GarcĂ­a
[EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED],FreeRadius users mailing listfreeradius-users@lists.freeradius.org To: 'FreeRadius users mailing list' freeradius-users@lists.freeradius.org Subject: RE: FreeRADIUS and Postgres annoyance Date: Tue, 8 Aug 2006 11:24:24 -0400 I have the nas

Re: FreeRADIUS and Postgres annoyance

2006-08-09 Thread Joe Warren-Meeks
On 8 Aug 2006, at 18:02, Dennis Skinner wrote: Or always run your test queries as the user that FR is using and from the FR machine instead of root and/or from localhost. I would have done that, except I've made my own package which only contains the minimum postgres stuff needed, i.e.

FreeRADIUS and Postgres annoyance

2006-08-08 Thread Joe Warren-Meeks
radiusd: FreeRADIUS Version 1.1.2, for host , built on Jul 27 2006 at 16:42:40 Linux auth2 2.6.15-23-server #1 SMP Tue May 23 15:10:35 UTC 2006 i686 GNU/Linux Hey there, I had radiusd working nicely with MySQL, but apparently we have to use Postgres, which is fine.. Recompiled it with

Re: FreeRADIUS and Postgres annoyance

2006-08-08 Thread Joe Warren-Meeks
Sorry guys, my fault.. mainly permissions problems on the relevant tables in postgres. Although I haven't got the nas table working yet though, so pointers there will help.. (moral of the story, tcpdump -w out.dmp -A -nvi eth0 -s0 port 5432 plus ethereal is a good thing.) -- joe.

Re: FreeRADIUS and Postgres annoyance

2006-08-08 Thread Josh Howlett
Joe Warren-Meeks wrote: (moral of the story, tcpdump -w out.dmp -A -nvi eth0 -s0 port 5432 plus ethereal is a good thing.) Agreed, but you can make this a bit simpler by using tethereal. josh. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

RE: FreeRADIUS and Postgres annoyance

2006-08-08 Thread Gregory J. Marsh
users mailing list Subject: Re: FreeRADIUS and Postgres annoyance Sorry guys, my fault.. mainly permissions problems on the relevant tables in postgres. Although I haven't got the nas table working yet though, so pointers there will help.. (moral of the story, tcpdump -w out.dmp -A -nvi eth0