Re: Rewriting wimax calling-station-id with perl

Hi, As you are undoubtedly aware, the ubuntu/debian package of freeradius comes without the wimax module (despite having the wimax module) installed. My own attempts to compile/install/build deb package for ubuntu always die with the infamous undefined reference to `lt_preloaded_symbols'

Re: Rewriting wimax calling-station-id with perl

Hi, Apologies for the late response. Our mail system went down at a terrible time! From: Johan Meiringjmeir...@pcservices.co.za Subject: Re: Rewriting wimax calling-station-id with perl Which version of debian do you need packages for? I am trying to install it on ubuntu 11.04

Re: Rewriting wimax calling-station-id with perl

Hi, All Thanks a bunch for this. I have tested both the ubuntu and CentOS/RedHat variants successfully on separate machines, integrated with postgresql. (The mysql was a typo incited by a previous install of freeradius-mysql). Ironically, i also managed to build deb packages from the 2.1.12

Freeradius rlm_sql: Failed to create the pair: Invalid TLV specification (WiMAX MS)

Hi, I am running 2.1.12 in an attempt to auth Wimax users. However I am having difficulty defining TLVs for WiMAX-QoS-Descriptor and associated WiMAX-Packet-Flow-Descriptor I used a post on the matter in the freeradius mailing list which suggested something to the effect of: INSERT INTO

Re: Freeradius-Users Digest, Vol 78, Issue 111

On 10/26/2011 12:11 AM, freeradius-users-requ...@lists.freeradius.org wrote: You just add the attributes, and the server will take care of encapsulating them in TLVs. Is there any thing i must pay attention to with regard to either (or both of): 1. The order in which i define the

Re: Freeradius rlm_sql: Failed to create the pair: Invalid TLV specification (WiMAX MS)

Apologies for my incorrectly headed last response: On 10/26/2011 12:11 AM, freeradius-users-requ...@lists.freeradius.org wrote: You just add the attributes, and the server will take care of encapsulating them in TLVs. Is there any thing i must pay attention to with regard to either (or

Unencrypted username in radacct/radpostauth for ttls tunnel authenticated user

Hi, I have managed to auth a Greenpacket WiMAX MS via an eap ttls tunnel. Thanks to Alan's direction earlier, I can also send the service flow definitions correctly. I have now found that subsequent db writes (and logging) associated with accounting and postauth functions are the encrypted

Re: Unencrypted username in radacct/radpostauth for ttls tunnel authenticated user

On 10/26/2011 02:49 PM, freeradius-users-requ...@lists.freeradius.org wrote: On Access-Accept, store the unencrypted User-Name in the DB, along with a Class attribute. When you receive an accounting packet, look up the Class attribute to find the unencrypted User-Name. Thanks I notice

Proxy Treatment of PAP/Chap Auth Types

Hi, Hope someone can give me a pointer on this matter. We have 2 RADIUS installations, thus: 1. FreeRADIUS/mysql Version 2.1.1, in whose radcheck, Password attribute is 'User-Password' 2. FreeRADIUS/mysql Version 2.1.10, in whose radcheck, Password attribute is 'Cleartext-Password' On both

Re: Proxy Treatment of PAP/Chap Auth Types

Thanks for your usual indulgence and assistance, Alan and all. Much appreciated. I did the hopelessly illogical thing of testing it from an actual NAS associated with the proxy. The home server, which had been returning those rejects thus far, now accepted the user without fuss. Must be