2013-10-29 - Re: [GRASE-Hotspot] Thin client support

Header Data

From: Timothy White <ti***8@gmail.com>
Message Hash: 123ae9b93dbd1c6628a82228d82d694e7a085203329d66f6a79a855c20125a75
Message ID: <CAESLx0+iH_ifvwTT2SbDansQfpB-j6qu1ALrSVSfZEgz5qZAEA@mail.gmail.com>
Reply To: <CAFVFZ2aEV=aq68Qx7RcH+yuQxYohg3LoUcUN8RZP2Qpeuk+Yaw@mail.gmail.com>
UTC Datetime: 2013-10-29 22:26:53 UTC
Raw Date: Wed, 30 Oct 2013 15:26:53 +1000

Raw message 

Assuming each client does get a unique IP address from Grase, does it also
present to the network a unique MAC address? We rely on MAC addresses to
identify clients, so if it's 100 unique IP addresses but all appearing as a
single MAC, then it won't work.

Also, check that the IP's aren't being NATted before Grase.

Tim


On Sat, Aug 3, 2013 at 12:44 AM, Nelson Tandug <ne***g@gmail.com>wrote:

> First, thanks for this great project! Access for wireless devices works
> well with Grase, from the captive portal down to the accounting features.
>
> We are also serving internet access to wired workstations using NComputing
> thin clients. While the captive portal works for any client in a cluster,
> we notice that Grase seems to regard the cluster as one PC, thus giving
> access to the other clients in that cluster using the first authenticated
> account. Our hosts are a mix of WinXP and Win2003.
>
> Has anyone managed to setup Grase in such a way that it can accurately
> detect each client session as a separate session? Each thin client gets a
> unique IP address, by the way.
>
> Any help will be most appreciated. Thanks!
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> Grase-hotspot mailing list
> Gr***t@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/grase-hotspot
>
>

Thread