2016-03-06 - Re: [GRASE-Hotspot] Problem with Redirection to Users Login Page

Header Data

From: Timothy White <ti***8@gmail.com>
Message Hash: 3caa98e386cbfca8b9b4e847ab0d3634d9627a70b1a632210a19c9eb83cfb41d
Message ID: <CAESLx0LL_DHdYSa3-BsK21v6KDWTP7ftMP9zCXuKQvhoThfa5g@mail.gmail.com>
Reply To: <e753fe7d-23de-4892-9178-1e799347bb74@grasehotspot.org>
UTC Datetime: 2016-03-06 05:17:40 UTC
Raw Date: Sun, 06 Mar 2016 22:17:40 +1000

Raw message 

I've set up brand new testing VM's, and am also having issues with the
3.8.0 not redirecting properly. I'll investigate and try and get a fix out.
Previously when there had been reports of issues, I couldn't reproduce them
in my testing environment. So I've setup a brand new environment to try and
work out what's happening.

I'll keep you updated as I work out the issue.

Thanks

Tim

On Sat, Mar 5, 2016 at 9:52 PM, Ali Farajpahlou <al***u@gmail.com>
wrote:

> thankyou kira
>
> I was thinking about a cron job my self. thanks for the suggestion and
> reviewing my problem.
>
> On Saturday, March 5, 2016 at 3:18:48 PM UTC+3:30, KIRA Ynet wrote:
>>
>> You need to restart dnsmasq and chilli.  I know its a trouble,  but for
>> now that's the only way to make it working after reboot after you face this
>> unable to redirect issue.  Maybe Tim can take a look why was this happen.
>>
>> So far for me to fix the issue, i've setup cron job 4 minutes after
>> bootup,  it restart the dnsmasq and chilli.
>>
>> Maybe Tim can find out the possibilities of this issue appeared.
>> On 5 Mar 2016 19:30, "Timothy White" <ti***.@gmail.com> wrote:
>>
>>> It does sound like it could be DNS related.
>>>
>>> Can you check with either dig, or nslookup, (or even ping) if DNS is
>>> working.
>>>
>>> e.g.
>>> ping google.com (should give you an IP address then it'll attempt to
>>> ping)
>>> Might be good to try
>>> ping grasehotspot.org (as it should be in the walled garden, and so
>>> should work).
>>>
>>> dig @10.1.0.1 google.com
>>>
>>> Regards
>>>
>>> Tim
>>>
>>> On Sat, Mar 5, 2016 at 9:18 PM, Ali Farajpahlou <al***.@gmail.com>
>>> wrote:
>>>
>>>> thanks for the reply
>>>>
>>>> I'm so sry, I forgot to mention that I actually use www.yahoo.com for
>>>> tests, as other posts have suggested that the SSL limitations might be the
>>>> problem. no luck. its really an odd thing to happen actually, cuz after
>>>> approximately 30 mins it gets fixed! i don't know if this should be
>>>> considered as a problem (it gets fixed by it self, but it takes time :D ).
>>>> so sry if I'm consuming your time. and thank you again.
>>>>
>>>> i just rebooted the server. tried on 2 clients, when i enter ip address
>>>> in the browser, the redirection works (i tried 8.8.8.8), but when i use a
>>>> web url, it doesn't work. does it have anything to do with the dns?
>>>>
>>>> On Saturday, March 5, 2016 at 2:16:01 PM UTC+3:30, timwhite88 wrote:
>>>>>
>>>>> Hi Ali
>>>>>
>>>>> Can you try using come command line web clients (curl is a great one)
>>>>> to diagnose the issue. They key may be to do with the kind of sites they
>>>>> are visiting, as the UAM redirect can not work for SSL sites (limitation of
>>>>> how SSL works).
>>>>>
>>>>> I normally use Yahoo to test, as they don't default to SSL. I also try
>>>>> going directly to an ip address like 8.8.8.8 because even though normally
>>>>> there isn't a website there, the UAM redirect will catch that.
>>>>>
>>>>> Regards
>>>>>
>>>>> Tim
>>>>>
>>>>> On Sat, Mar 5, 2016 at 7:41 PM, Ali Farajpahlou <al***.@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hey!
>>>>>>
>>>>>> First of all, a thanx for all the work to all who had a hand in
>>>>>> making this project. Seriously thanx!!!
>>>>>>
>>>>>> I first search other posts for this, couldn't find any answer, and
>>>>>> the Problem:
>>>>>>
>>>>>> I have successfully installed grase on latest version of debian,
>>>>>> Everything is working fine, the server machine boots up fine, DHCP to
>>>>>> clients over lan OK, but when i connect client machines it will take around
>>>>>> 30 mins (after the complete server bootup) for them to be redirected to the
>>>>>> UAM login page. i couldn't find the reason why it takes this long. users
>>>>>> can ping the lan ip (10.1.0.1) and manually can enter the login page and
>>>>>> login, but untill the redirection is fixed, clients can't open pages even
>>>>>> after the manual login thing. the intresting thing saw was after manual
>>>>>> login, "Telegram" application starts using the internet, but webpages still
>>>>>> not working.
>>>>>>
>>>>>> sry for my bad english, i would appriciate u'r oppinion on this
>>>>>> matter.
>>>>>>
>>>>>> with Regards.
>>>>>>
>>>>>> Ali Farajpahlou.
>>>>>>
>>>>>> --
>>>>>> 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.
>>>>>> To post to this group, send email to gr***.@grasehotspot.org.
>>>>>> Visit this group at
>>>>>> https://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/56d1a710-4b41-47a6-bb80-a8980e5a6b7a%40grasehotspot.org
>>>>>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/56d1a710-4b41-47a6-bb80-a8980e5a6b7a%40grasehotspot.org?utm_medium=email&utm_source=footer>
>>>>>> .
>>>>>>
>>>>>
>>>>> --
>>>> 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.
>>>> To post to this group, send email to gr***.@grasehotspot.org.
>>>> Visit this group at
>>>> https://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/124194f1-98cf-4bc7-a60e-66685b5bd886%40grasehotspot.org
>>>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/124194f1-98cf-4bc7-a60e-66685b5bd886%40grasehotspot.org?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>
>>> --
>>> 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.
>>> To post to this group, send email to gr***.@grasehotspot.org.
>>> Visit this group at
>>> https://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/CAESLx0J5%3Dv6SWiTW%3D04ZR_Fb8JFrhkcZjUAW8k9j2N0DW-doyg%40mail.gmail.com
>>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/CAESLx0J5%3Dv6SWiTW%3D04ZR_Fb8JFrhkcZjUAW8k9j2N0DW-doyg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
> 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***e@grasehotspot.org.
> To post to this group, send email to gr***t@grasehotspot.org.
> Visit this group at
> https://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/e753fe7d-23de-4892-9178-1e799347bb74%40grasehotspot.org
> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/e753fe7d-23de-4892-9178-1e799347bb74%40grasehotspot.org?utm_medium=email&utm_source=footer>
> .
>

Thread