Peter Micunek wrote:
So I have to design a Accounting FreeRADIUS server which will store the
RADIUS acconting with IP and MSISDN to OpenLDAP.
That's not good. LDAP isn't really designed for large volumes of
writes. I would suggest using an SQL database.
Alan DeKok.
--
Peter Micunek wrote:
A problem is that this proxy know IP address of customer instead of
MSISDN and unfortunately cannot use a RADIUS to
obtain the MSISDN from another source. This proxy is able to use only
the LDAP request with IP of customer and then
FreeRadius can't write to (account to)
The proxy cannot speak to an SQL server.
Do you know some LDAP-SQL proxy which listen on LDAP server port and
convert LDAP request to SQL and vice versa.
Also, I am considering to use:
NAS --- FreeRADIUS (rlm_sql_mysql) --- MySQL DB --- OpenLDAP with
slapd-sql --- LDAP client
what do
Peter Micunek wrote:
The proxy cannot speak to an SQL server.
Why not?
Do you know some LDAP-SQL proxy which listen on LDAP server port and
convert LDAP request to SQL and vice versa.
Huh? In one word: No.
Also, I am considering to use:
NAS --- FreeRADIUS (rlm_sql_mysql)
Peter Micunek wrote:
The proxy cannot speak to an SQL server.
Then it's very poor software, and my advice would be to look elsewhere.
Do you know some LDAP-SQL proxy which listen on LDAP server port and
convert LDAP request to SQL and vice versa.
OpenLDAP will do this, but it's not
Hello everyone,
I work for a mobile operator and we have a product (something like proxy)
which is able to do so-called Header Enrichment.
A mobile customer who is connected over this proxy will have enriched his
http header with phone number (MSISDN).
A problem is that this proxy know IP
6 matches
Mail list logo
