2014-04-30 - Re: [GRASE-Hotspot] router to grase issue…
Header Data
From: “James C.” <to***n@gmail.com>
Message Hash: 4a2969d05172978428a035b64739f9a8fa320737da8176318cffcdeccdd0e72c
Message ID: <04ac8b58-5559-46ff-b1d6-183e790eff13@grasehotspot.org>
Reply To: <CAESLx0+c-A+uXZ5sNRNBYWyZfci_gN=wO8SXUHVbkdhFCU5-xA@mail.gmail.com>
UTC Datetime: 2014-04-30 13:32:10 UTC
Raw Date: Wed, 30 Apr 2014 13:32:10 -0700
Raw message
Tim,
I have the network broken up
RouterA serves 192.168.30.1-254
RouterB serves 192.168.40.1-254
etc based on geographic area. I am trying to use grase as central
authentication/captive portal for everyone.
I used to have separate commercial hospitality routers but they were
unreliable so I scrapped them.
So one router in every area routes over a body of water to the main land
where I have the Grase Server and out to the internet.
Bad Idea?
On Wednesday, April 30, 2014 4:22:03 PM UTC-4, timwhite88 wrote:
>
> Seeing as GRASE is a router, why do you have the fortigate at all?
>
> Tim
> On May 1, 2014 5:05 AM, "James C." <to***.@gmail.com <javascript:>>
> wrote:
>
>> <https://lh3.googleusercontent.com/-zYEzONpCX6U/U2FIIjpvo7I/AAAAAAAAAsg/84NrDUUzbnA/s1600/killmenow.bmp>
>> Folks,
>>
>> I have people on the lan side with ips of 192.168.30.1-254 my WAN port is
>> 192.168.10.9.
>> PC LAN 192.168.10.8
>> WAN public IP
>>
>> Now my issue I get to grase and login monitoring users says
>>
>> 192.168.10.9 and mac of the router.
>>
>> Once I login EVERYONE doesn't need to. I am guessing that is I set the
>> router without NAT it would have unique IPs and I would be fine?
>>
>> Unfortunately, the Fortigate only does two things NAT or transparent.
>> How would you solve it?
>>
>> --
>> This mailing list is for the Grase Hotspot Project
>> http://grasehotspot.org
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Grase Hotspot" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to gr***.@grasehotspot.org <javascript:>.
>> To post to this group, send email to gr***.@grasehotspot.org<javascript:>
>> .
>> Visit this group at
>> http://groups.google.com/a/grasehotspot.org/group/grase-hotspot/.
>> To view this discussion on the web visit
>> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/f38522b6-ac3a-4732-9d4f-e5b929681387%40grasehotspot.org<https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/f38522b6-ac3a-4732-9d4f-e5b929681387%40grasehotspot.org?utm_medium=email&utm_source=footer>
>> .
>>
>
Thread
- Return to April 2014
-
Return to May 2014
- Return to “Peter Boon <gp***n@gmail.com>”
- Return to “Timothy White <ti***8@gmail.com>”
-
Return to ““James C.” <to***n@gmail.com>”
- 2014-04-30 (Wed, 30 Apr 2014 12:05:01 -0700) - router to grase issue… - “James C.” <to***n@gmail.com>
- 2014-04-30 (Thu, 01 May 2014 06:22:03 +1000) - Re: [GRASE-Hotspot] router to grase issue… - Timothy White <ti***8@gmail.com>
- 2014-04-30 (Wed, 30 Apr 2014 13:32:10 -0700) - Re: [GRASE-Hotspot] router to grase issue… - “James C.” <to***n@gmail.com>
- 2014-05-01 (Thu, 01 May 2014 14:27:45 +0200) - Re: [GRASE-Hotspot] router to grase issue… - Peter Boon <gp***n@gmail.com>
- 2014-04-30 (Thu, 01 May 2014 06:22:03 +1000) - Re: [GRASE-Hotspot] router to grase issue… - Timothy White <ti***8@gmail.com>