Re: freeradius redback sms
Samson Martinez wrote: We are currently using a Redback SMS 500 to terminate PPPoE sessions for client desktops. Up until now an older Steelbelted Radius server has been used to authenticate RADIUS requests forwarded by the Redback and it's worked ok. We want to transfer the RADIUS support to a freeradius installation but I am having a bit of a fit trying to get it to work. See radsniff from the current release. Watch the packets going TO your old RADIUS server, and the responses comign BACK from it. Configure FreeRADIUS to respond to requests with the same attributes. The NAS has no idea which server you're running. All it sees is the attributes in the packet. The solution is to first find out what needs to be sent back, and then make FreeRADIUS send the correct response. There is no magic, and there is no need to fight with any configuration. The redback log looks like you're not sending back the correct attributes. If you don't know what attributes to send back, you WILL NOT be able to solve the problem. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: freeradius redback sms
Hi, We are running freeradius version 1.0.1, I've added the 1.0.1? why? 09:10:40 9May2007: %RAD-7-SEND_IPADDR: Sent to 10.103.0.4: port 1812 09:10:40 9May2007: %RAD-7-SPKT: Sent packet: 0x01 00 00 4f 65 0f 55 dd 7c a2 0b 7d a4 bf a0 b3 85 37 a3 4e 01 0d 6a 61 6b 65 31 40 6c 6f 63 61 6c 03 13 01 c7 24 7a b9 3e 1f 8d ec bc ea 4d 35 84 10 2d cf 20 09 52 65 64 42 61 63 6b 06 06 00 00 00 02 07 06 00 00 00 01 05 06 07 00 00 01 09:10:40 9May2007: %RAD-7-RPKT: Received packet: 0x02 00 00 20 c8 c3 8a c4 dc d3 6a 6b 59 a4 25 57 ea 1a ba 06 06 06 00 00 00 02 07 06 00 00 00 01 no. this is not the redback support list. this is the freeradius list. the 'rule' of this list is you post (obfuscating confidential information) the output of 'radiusd -X' Speaking of which, what should my nastype in the clients.conf file be? I entered redback but I couldn't confirm if that was correct. if redback is unknown or cannot be probed by the tools which utilise that entry, then 'other' is the answer alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
RE: freeradius redback sms
My apologies for including the redback trace - won't happen again. 1.0.1 because it was already installed and running - haven't had a chance to upgrade. Thanks for the feedback. -Samson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, May 09, 2007 2:18 PM To: FreeRadius users mailing list Subject: Re: freeradius redback sms Hi, We are running freeradius version 1.0.1, I've added the 1.0.1? why? 09:10:40 9May2007: %RAD-7-SEND_IPADDR: Sent to 10.103.0.4: port 1812 09:10:40 9May2007: %RAD-7-SPKT: Sent packet: 0x01 00 00 4f 65 0f 55 dd 7c a2 0b 7d a4 bf a0 b3 85 37 a3 4e 01 0d 6a 61 6b 65 31 40 6c 6f 63 61 6c 03 13 01 c7 24 7a b9 3e 1f 8d ec bc ea 4d 35 84 10 2d cf 20 09 52 65 64 42 61 63 6b 06 06 00 00 00 02 07 06 00 00 00 01 05 06 07 00 00 01 09:10:40 9May2007: %RAD-7-RPKT: Received packet: 0x02 00 00 20 c8 c3 8a c4 dc d3 6a 6b 59 a4 25 57 ea 1a ba 06 06 06 00 00 00 02 07 06 00 00 00 01 no. this is not the redback support list. this is the freeradius list. the 'rule' of this list is you post (obfuscating confidential information) the output of 'radiusd -X' Speaking of which, what should my nastype in the clients.conf file be? I entered redback but I couldn't confirm if that was correct. if redback is unknown or cannot be probed by the tools which utilise that entry, then 'other' is the answer alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
