[pap] WARNING: Auth-Type already set. Not setting to PAP
Failed to authenticate the user.
WARNING: Unprintable characters in the password. Double-check the shared secret on the server and the NAS!
I included dailup.conf in voip-postpaid.conf.
ecv: Access-Request packet from host 212.13.228.58 port 38380, id=198, length=206
Acct-Multi-Session-Id = "1291817780502"
Cisco-Attr-130 = 0x683332332d63616c6c696e672d656e74657270726973652d69643d656e74504258
Calling-Station-Id = "81609000"
NAS-Identifier = "intraswitch"
NAS-IP-Address = 212.13.228.58
3GPP2-Prepaid-acct-Capability = 0x010600000002
3GPP2-Session-Termination-Capability = 1
h323-conf-id = "h323-conf-id=1291817780502"
Vendor-Specific = 0x00000009
Event-Timestamp = "Dec 8 2010 15:16:20 CET"
User-Name = "081609000"
User-Password = "12345"
# Executing section authorize from file /etc/raddb/sites-enabled/default
+- entering group authorize {...}
++[preprocess] returns ok
++[chap] returns noop
++[mschap] returns noop
++[digest] returns noop
[suffix] No '@' in User-Name = "081609000", looking up realm NULL
[suffix] No such realm "NULL"
++[suffix] returns noop
[eap] No EAP-Message, not doing EAP
++[eap] returns noop
[pgsql-voip] expand: %{User-Name} -> 081609000
[pgsql-voip] sql_set_user escaped user --> '081609000'
rlm_sql (pgsql-voip): Reserving sql socket id: 24
[pgsql-voip] expand: SELECT id, UserName, Attribute, Value, Op FROM radcheck WHERE Username = '%{SQL-User-Name}' ORDER BY id -> SELECT id, UserName, Attribute, Value, Op FROM radcheck WHERE Username = '081609000' ORDER BY id
rlm_sql_postgresql: Status: PGRES_TUPLES_OK
rlm_sql_postgresql: query affected rows = 1 , fields = 5
[pgsql-voip] expand: SELECT GroupName FROM radusergroup WHERE UserName='%{SQL-User-Name}' ORDER BY priority -> SELECT GroupName FROM radusergroup WHERE UserName='081609000' ORDER BY priority
rlm_sql_postgresql: Status: PGRES_TUPLES_OK
rlm_sql_postgresql: query affected rows = 0 , fields = 1
rlm_sql (pgsql-voip): Released sql socket id: 24
[pgsql-voip] User 081609000 not found
++[pgsql-voip] returns notfound
++[expiration] returns noop
++[logintime] returns noop
[pap] WARNING! No "known good" password found for the user. Authentication may fail because of this.
++[pap] returns noop
ERROR: No authenticate method (Auth-Type) found for the request: Rejecting the user
Failed to authenticate the user.
Using Post-Auth-Type Reject
# Executing group from file /etc/raddb/sites-enabled/default
+- entering group REJECT {...}
[attr_filter.access_reject] expand: %{User-Name} -> 081609000
attr_filter: Matched entry DEFAULT at line 11
++[attr_filter.access_reject] returns updated
Delaying reject of request 0 for 1 seconds
Going to the next request
Waking up in 0.9 seconds.
rad_recv: Access-Request packet from host 212.13.228.58 port 38380, id=198, length=206
Waiting to send Access-Reject to client intraswitch port 38380 - ID: 198
Sending delayed reject for request 0
Sending Access-Reject of id 198 to 212.13.228.58 port 38380
Waking up in 4.9 seconds.
> Date: Wed, 8 Dec 2010 16:29:27 +0700
> Subject: Re: Voip database
> From: work@fajar.net
> To: freeradius-users@lists.freeradius.org
>
> On Wed, Dec 8, 2010 at 2:55 PM, Miha Zoubek <miha_zoubek@hotmail.com> wrote:
> > I have replace voip-postpaid.conf with new one but still the same.
> > I this configuration file (voip-postpaid.conf) is written:
> > uthcheck_table = "radcheck"
> > authreply_table = "radreply"
> > groupcheck_table = "radgroupcheck"
> > groupreply_table = "radgroupreply"
> > usergroup_table = "radusergroup"
>
> Perhaps we started on the wrong assumptions.
> What do you intend to use postgresql for? Is it
> (a) only to store accounting data, or
> (b) to store user names/password AND accounting data
>
> if it's (a), then there should be nothing wrong with your first
> config. You simply need to place user data for "081609000" in whatever
> "database" you choose (whether it's users file, or something else).
> The error could simply be because you haven't define that user yet.
>
>
> If it's (b), then you need to forget for a moment that you're using it
> for voip. It doesn't really matter with regards to the problem you're
> facing. Get freeradius working with postgresql first.
>
> Your debug log says
>
> authorize_check_query = ""
> authorize_group_check_query = ""
> authorize_group_reply_query = ""
>
> when the they should not be empty. Fix that first. Worry about the
> rest later, after you fix that.
>
> The easiest way to do that, IMHO, is forget about voip-postpaid.conf
> and cisco_h323_db_schema.sql for the moment. Stick to the default
> sql.conf, sql/postgresql/dialup.conf, and sql/postgresql/schema.sql.
>
>
> AFTER you get it to work, then you can try to get that particular conf
> and sql scheme working. Perhaps the author might be able to help.
>
> The default sql.conf/dialup.conf and schema should work for voip or
> whatever. Probably not as efficient, but it'd still work.
>
> --
> Fajar
>
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html