[ previous ] [ next ] [ threads ]
 
 From:  "Imran K" <gururug at gmail dot com>
 To:  radiussupport at lrcommunications dot net
 Cc:  "Monowall Support List" <m0n0wall at lists dot m0n0 dot ch>, "Mono Dev List" <m0n0wall dash dev at lists dot m0n0 dot ch>
 Subject:  Re: [m0n0wall-dev] Ticket Printer Project
 Date:  Wed, 19 Dec 2007 12:16:50 +1100
Seems like a good idea, why limit to a printer only though. Printer device
is an output device, of which there will be a few you may need to use. Web
interface is used to add, print, monitor etc. etc. (not the button on the
printer as you suggested - maybe i misunderstood)

So in otherwords it is a "ticketing module";

-click a print ticket (users - times - printers)
-self register/provision/extend via captive portal

So major subcompontents are;

-interface
-authentication
-accounting/record keeping/monitoring???
-output (printers,sign-up-screen,email,other)
-payment? (probrably simpler to not integrate but maybe worth a thought)

As a proof of concept, you could -

-write a query to grab all users / generate 1 off uid and pwds
-select 1 an click allow which will print ticket and open access for Xmins
-test

from there you can re-work to suit!

Question;

Would be more efficient / scalable on larger deployments if this "temp
access provisioning system" is not running from mono's??? But perhaps you
would still need printers running off them or near them and auth / AAA
hooks???

Anyone keen with Cisco stuff would know of their recent advances in
distributed accounting and access control. I'm pretty sure their proprietary
but some articatural principles could be applied here.












On Dec 18, 2007 1:32 PM, Donald Day <donald dot day at adrian dash mi dot us> wrote:

> Steven,
>
> There are several ways to authenticate with MWs' captive portal.  Why
> limit
> the solution to radius only?  I guess I would need some reason as to why
> one
> would want to have the absolute requirement and added expense of a radius
> server when MW is capable of radius auth and at a minimum 'simple username
> password' method with an associated timeout.
>
> Don
>
> -----Original Message-----
> From: Steven Ringwald [mailto:asric at asric dot com]
> Sent: Monday, December 17, 2007 8:02 PM
> Cc: Monowall Support List; 'Mono Dev List'
> Subject: Re: [m0n0wall-dev] Ticket Printer Project
>
>
> On Dec 17, 2007, at 4:18 PM, Alex M wrote:
>
> > Hey all,
> >
> > I finally got some time for development.
> >
> > I wanna add ticket printing functionality for mono. Ex: Thermal
> > printer
> > connected to mono box via RS232 (Serial Port). Customer comes to the

> > button on the
> > thermal printer and mono prints the ticket with the Username and
> > Password
> > that will be active for  x minutes. Same thing as you would get with
> > D-Link
> > DSA3100 hotspots but implemented in mono.
> >
> >
> >
> > Now if you are interested I would appreciate some here:
> >
> > a)       I need to know if ppl want it as public release, and if u
> > do I will
> > need some one to help me w/ coding (I cant do everything myself)
> >
> > b)       I need to find out how can I send (and receive) print
> > commands from
> > RS232 under BSD
> >
> > c)       And we will have to do all the dity work that come as side
> > affect
> > of having b) integrated in mono interface.
>
> It seems like the better place to have the printer function would be
> adding/removing people from a radius server. I think that M0n0 already
> supports using Radius as an authentication backend in captive portal.
>
>
>
> Steve
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash dev dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash dev dash help at lists dot m0n0 dot ch
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash dev dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash dev dash help at lists dot m0n0 dot ch
>
>