Hello Everyone, I would like to add a custom variable to get stored in our Free Radius DB. We have a functioning environment, and would like to know the suggested way of adding a new variable to the long list. The service is Session Initiation Protocol (SIP) Kind Regards, Nick from Toronto.
On Mon, Aug 4, 2014 at 6:11 AM, Nick Cameo <symack@gmail.com> wrote:
Hello Everyone,
I would like to add a custom variable to get stored in our Free Radius DB. We have a functioning environment, and would like to know the suggested way of adding a new variable to the long list.
You mean add new column to radius tables (e.g. radacct)? Have you read the default queries? This is the default one for mysql on v2.x.x: https://github.com/FreeRADIUS/freeradius-server/blob/v2.x.x/raddb/sql/mysql/... Adding a new column requires that you alter the table definition on the db, and adjust the queries used by FR. -- Fajar
Hello Fajar, Thank you for your response. Oooops. I should have been more clear. The queries, table fields, and dictionaries have been modified. I just can't figure out how to get Freeradius to pick up the value of the variable automatically as it does with the rest of the standard values (ie, SIP-To-Tag) for our service. Also, when trying to sniff the running port using ngrep -d eth0 -qt -W byline portrange 1812-1814, I am not able to pick up an freerad related packets. Are those still the ports we need to sniff out? <conf snippet> ipaddr = 127.0.0.1 # OR, you can use an IPv6 address, but not both # at the same time. # ipv6addr = :: # any. ::1 == localhost # Port on which to listen. # Allowed values are: # integer port number (1812) # 0 means "use /etc/services for the proper port" port = 0 <conf snippet> Thanks in Advance, Nick.
On Mon, Aug 4, 2014 at 6:16 PM, Nick Cameo <symack@gmail.com> wrote:
Hello Fajar, Thank you for your response. Oooops. I should have been more clear. The queries, table fields, and dictionaries have been modified.
I just can't figure out how to get Freeradius to pick up the value of the variable automatically as it does with the rest of the standard values (ie, SIP-To-Tag) for our service.
... and the variable is ...? Is it printed out when you run FR in debug log? i.e. does the nas send the attribute, and FR correctly receive/decode it?
Also, when trying to sniff the running port using ngrep -d eth0 -qt -W byline portrange 1812-1814, I am not able to pick up an freerad related packets. Are those still the ports we need to sniff out?
1812 -> auth, 1813 -> acct. Don't know about ngrep, but it should work with tcpdump -vv -i eth0 udp and portrange 1812-1813 ... then again, debug mode would print the packets and decoded attributes and values, making it easier to troubleshoot, so you should use that instead/as well. -- Fajar
participants (2)
-
Fajar A. Nugraha -
Nick Cameo