Configuring FreeRADIUS and BAM for Motorola Canopy SM authentication and Bandwidth Maanagement
Hello All, I have configured FreeRADIUS to do bandwidth and authentication together with the BAM server, however the RADIUS does authenticate but it fails on BAM hence the CPEs are not authenticated and registered by the Access Points. Anyone who can help on this? Bernard
On Wed 07 Feb 2007 07:30, Bernard Ochieng wrote:
Hello All,
I have configured FreeRADIUS to do bandwidth and authentication together with the BAM server, however the RADIUS does authenticate but it fails on BAM hence the CPEs are not authenticated and registered by the Access Points. Anyone who can help on this?
What do you mean by "fails on BAM"? -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc
On Wed 07 Feb 2007 07:30, Bernard Ochieng wrote:
Hello All,
I have configured FreeRADIUS to do bandwidth and authentication together with the BAM server, however the RADIUS does authenticate but it fails on BAM hence the CPEs are not authenticated and registered by the Access Points. Anyone who can help on this?
What do you mean by "fails on BAM"?
BAM does not accept the the authenticated elements from the FreeRADIUS hence CPEs are not registered to the respective APs. -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc ----- Original Message ----- From: "Peter Nixon" <listuser@peternixon.net> To: "Bernard Ochieng" <bernard@malawi.net>; "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Sent: Wednesday, February 07, 2007 3:13 PM Subject: Re: Configuring FreeRADIUS and BAM for Motorola Canopy SM authentication and Bandwidth Maanagement
Bernard Ochieng wrote:
What do you mean by "fails on BAM"?
BAM does not accept the the authenticated elements from the FreeRADIUS hence CPEs are not registered to the respective APs.
Perhaps you could try explaining in more detail, and using fewer acronyms. i.e. BAM? What's that? You appear to be the first person on this list asking about BAM. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
Alan, Thank you for your e-mail in which you have sort more explanation on the problem. We have deployed Motorola Canopy network using Access Points(AP) and Subscriber Modules(SM) to provide fixed wireless broadbadn solution to our customers. Motorola have a management software known as PrizmEMS which incorporates Bandwidth and Authentication Management (BAM) module in it. There are several ways to configure the bandwidth and authentication for the SMs. I opted to use FreeRADIUS which has been configured as per the users manual provided. I still cannot have the Subscriber Modules be registered to authentacion eneabled Access Points. When I check the logs it shows that FreeRADIUS has authenticated the Subscriber Modules however it fails to authenticate on the Bandwidth and Authentication Management module of the PrizmEMS s/w. Kindly let me know if this is more clear. Regards, Bernard ----- Original Message ----- From: "Alan DeKok" <aland@deployingradius.com> To: "Bernard Ochieng" <bernard@malawi.net>; "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Sent: Thursday, February 08, 2007 11:41 AM Subject: Re: Configuring FreeRADIUS and BAM for Motorola Canopy SM authentication and Bandwidth Maanagement
Bernard Ochieng wrote:
What do you mean by "fails on BAM"?
BAM does not accept the the authenticated elements from the FreeRADIUS hence CPEs are not registered to the respective APs.
Perhaps you could try explaining in more detail, and using fewer acronyms.
i.e. BAM? What's that? You appear to be the first person on this list asking about BAM.
Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
Bernard Ochieng wrote:
... When I check the logs it shows that FreeRADIUS has authenticated the Subscriber Modules however it fails to authenticate on the Bandwidth and Authentication Management module of the PrizmEMS s/w.
If the server tells the NAS to do something, and the NAS doesn't do it, blame the NAS. i.e. read the NAS documentation to see what attributes it expects to see in an Access-Accept, or failing that, how to give you more information about why the Access-Accept was ignored. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
participants (3)
-
Alan DeKok -
Bernard Ochieng -
Peter Nixon