[isf-wifidog] [AllianceCSF] postgresql vs mysql, get into the flamebait

[Benoit Grégoire]

On May 26, 2009, Marc Blanchet wrote:
> wlanmac a écrit :
> > The question becomes, where should it be optional?
> >
> > Optional in the way it is now where it is used by the portal to be
> > compatible on the roaming side,
> >
> > AP/WiFiDog ---> <wifidog protocol> ---> WiFiDog Portal ---> RADIUS
> >
> > or optional for access provisioning to the router, for device / access
> > controller compatibility?
> >
> > AP/NAS ---> <RADIUS> ---> <something?> ---> WiFiDog Portal
> >
> > (Note: "NAS" for Network Access Server is a more generic term for access
> > controller in RADIUS documentation).
> >
> > A concept I have been thinking of would be something along the lines of
> > what Marc suggested. A proxy to map the AAA features of a NAS with the
> > WiFiDog HTTP protocol.
> >
> > Such that you might have:
> >
> > AP/NAS/Proxy ---> <wifidog> ---> WiFiDog Portal (to support old-school
> > sites)
> >
> > AP/NAS ---> <RADIUS> ---> Proxy/WiFiDog Portal (to support standard
> > access controllers)
> >
> > AP/NAS ---> <RADIUS> ---> <FreeRADIUS/SuperProxy> ---> Multiple WiFiDog
> > Portals based on Realm (the future)
> >
> > It's just an idea... but, could be a way of achieving the best of all
> > worlds, RADIUS-wise.
>
> you were just 5 minutes faster than me to write almost exact same
> drawings... a few minor edits below:
>
> this is my view of v2:
>
> "v1" AP -> wifidog-http -> v2 wifidog portal -> radius backend
> "v2" AP ->              radius               -> radius backend

You just described CoovaChilli.  If this is what you want, continuing with 
wifidog is just plain silly (Coova is really good at what it does, and it's 
main developer has EXACTLY the same worldview as you do).

It is funny however to see people suggest using RADIUS would make everything 
simpler to understand and implement.  Unless someone spends most of his 
workdays writing I really find that hilarious.  
The mere LIST of distinct RFCs specific to RADIUS 
(http://en.wikipedia.org/wiki/RADIUS#RFCs) 
http://dev.wifidog.org/wiki/doc/developer/WiFiDogProtocol_V1

as "simpler".  Especially since "using RADIUS" is just about as precise in the 
wifidog project as "Using http".  I don't think people understand quite well 
what the RADIUS protocol is, what a RADIUS server is, the characteristics of a 
RADIUS database, and finally what interoperability between RADImeans just about 

Let's go back to the genesis of the wifidog project (End of 2003)

The gateway:  Using the RADIUS protocol for gw-auth server communication was 
considered, and was 

http://bugs.mysql.com/bug.php?id=2364

-- 
Benoit Grégoire
-------------- section suivante --------------
Une pièce jointe HTML a été nettoyée...
URL: http://listes.ilesansfil.org/pipermail/wifidog/attachments/20090526/b3aa94e7/attachment.htm