I have the nas table working. Here's what you might need to know: 1) You don't configure it in radiusd.conf, you configure it in sql.conf -- look at the last few lines of the sample. 2) The documentation is wrong. Look at the sql query and the schema of the table. They don't agree. I wrote my query to match my needs and made the schema match that. 3) You must still have at least one entry in the clients.conf file. I just put in a dummy for the local machine. 4) On boot, FreeRadius starts before PostgreSQL is ready sometimes. So, I put a delay in the FreeRadius start. I'll do something better later.
Now if I can get the radius.log written to sql instead of a file, I'll be 100% sql which is what I really need. Greg... -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joe Warren-Meeks Sent: Tuesday, August 08, 2006 9:53 AM To: FreeRadius 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 -s0 port 5432 plus ethereal is a good thing.) -- joe. Joe Warren-Meeks T: +44 (0) 208 962 0007 Aggregator Ltd. M: +44 (0) 7789 176 078 Unit 62/63 Pall Mall Deposit F: +44 (0) 208 962 0008 124-128 Barlby Road, London W10 6BL PGP: 361F 78D0 56F5 8D7F 2639 947D 71E2 8811 F825 64CC - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
