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

[Michael Lenczner]

Even if this doesn't become the place to develop those tools, I hope
that you'll remain on the list to help as resources (to answer
questions like the one I just asked in another email).  And please do
let us know if you do start any development efforts elsewhere.

Thanks!

On Wed, May 27, 2009 at 1:32 AM, wlanmac <wlan at mac.com> wrote:
> Hi Marc,
>
> I wouldn't turn 'off'... you just may need to find a more receptive
> community. There are a few WiFiDog derivative projects out there, why
> not another. You have to keep in mind that WiFiDog project isn't
> 'driven' by development as much as it is a community of hotspot
> operators and website administrators. As such, I'm afraid that any
> discussion of RADIUS is simply too complicated. However, once there is
> such a RADIUS/Dog proxy, and once it is available in firmware and
> routers (wrapped up with a GUI for easy use), then perhaps WifiDog
> network operators will be interested. They will not care that much about
> the 'how' but would be interested in the wider range of
> available/compatible hardware/firmware.
>
> So, don't give up! and don't be discouraged! You aren't the first
> RADIUS-minded developer turned 'off' on the list.. perhaps there is some
> momentum possible for the RADIUS/Proxy concept as a separate project.
> Let's discuss.
>
> David
>
>
> On Tue, 2009-05-26 at 16:23 -0400, Marc Blanchet wrote:
>> Benoit Grégoire a écrit :
>> > On May 26, 2009, Marc Blanchet wrote:
>> >> wlanmac a écrit :
>> >
>> >> 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
>>
>> well, I've been implementing and deploying RADIUS (and Tacacs) for more
>> than 15 years and for many ISPs. I also implemented client and server on
>> a commercial networking product. I wrote some early versions of a RADIUS
>> IETF RFC. Therefore, I think I can claim that I know what RADIUS is all
>> about.
>>
>> I guess I'll just shut off now.
>>
>> Marc.
>>
>> >
>> > 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
>>
>>
>
> _______________________________________________
> WiFiDog mailing list
> WiFiDog at listes.ilesansfil.org
> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
>