Peering/Pairing hostapd radius servers? Urgent help!!

[khali singh]

Thank you for explaining. I managed to get a freeradius server to proxy my
requests to hostapd.

I have one more minor question. When I am initializing my new EAP method, I
want to scan all SSIDs and find out the ones that support my new custom EAP
method and write them to the configuration file. What would be ideal way to
do this? I am not asking for the code here, but rather the approach that I
should use.

I guess I need to use the scan file, but how can I check if a particular
EAP method is supported while initializing my EAP method in the
wpa_supplicant.

Thanks Jouni and team!!


On Thu, Nov 28, 2013 at 8:08 PM, Jouni Malinen <j at w1.fi> wrote:

> On Thu, Nov 28, 2013 at 03:06:38PM +0200, khali singh wrote:
> > I have successfully managed to get my own hostapd radius server and
> > wpa_supplicant to work together and it works like a charm.
> >
> > Now I wish to have 2 different hostapd radius servers that can talk to
> each
> > other and forward requests. So users from one domain are served by one
> > server and the other domain are served by the other server.
> >
> > Meaning the servers might receive a request from any user and may respond
> > with local authentication or forward it to the other server based on the
> > domain/realm in the identity received.
>
> hostapd does not include support for RADIUS proxy functionality. If you
> want something like that, you may want to look at more complete RADIUS
> implementations, like FreeRADIUS. The purpose of the RADIUS
> authentication server implementation in hostapd is to have a convenient
> test setup available for testing various EAP methods. This does not aim
> to be a complete RADIUS server in any way.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
> _______________________________________________
> HostAP mailing list
> HostAP at lists.shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.shmoo.com/pipermail/hostap/attachments/20131202/1cf710a0/attachment.htm>