2017-01-20 - Re: [GRASE-Hotspot] DHCP problem

Header Data

From: Timothy White <ti***8@gmail.com>
Message Hash: de1f78f7036b00092ac145ec6a39104a7499df3c417eb3dd610d767b6fe69bc9
Message ID: <CAESLx0+LVm2wxipdoKr6o3E7LUXFA0cdXM37hQeq2n1jAiGz+A@mail.gmail.com>
Reply To: N/A
UTC Datetime: 2017-01-20 14:05:02 UTC
Raw Date: Sat, 21 Jan 2017 07:05:02 +1000

Raw message 

Hi Tomas

There is something really weird going on. There should only be 1 chilli
process running. And under /var/run there are extra files that shouldn't be
there.

Can you please do a reboot and then within 5 minutes of the reboot, run
those 3 commands again please.

Thanks


On Fri, Jan 20, 2017 at 10:03 PM, tomas213 <to***3@gmail.com> wrote:

> ************************************************************
> ******************************
>
>
> /var/run/chilli.1247.cfg.bin   /var/run/chilli.17444.cfg.bin
> /var/run/chilli.24447.cfg.bin  /var/run/chilli.3350.cfg.bin
> /var/run/chilli.eth1.ipc   /var/run/chilli.tun0.sh
> /var/run/chilli.16757.cfg.bin  /var/run/chilli.1960.cfg.bin
> /var/run/chilli.28074.cfg.bin  /var/run/chilli.6328.cfg.bin
> /var/run/chilli.eth1.pid   /var/run/chilli.tun2.sh
> /var/run/chilli.16759.cfg.bin  /var/run/chilli.22354.cfg.bin
> /var/run/chilli.29303.cfg.bin  /var/run/chilli.6330.cfg.bin
> /var/run/chilli.eth1.sock
>
>
> ************************************************************
> ******************************
>
> root     16759  1.1  0.8  27164  8408 ?        Ss   13:00   0:42
> /usr/sbin/chilli -c /etc/chilli.conf
> root     21911  0.0  0.6  27164  6124 ?        S    14:01   0:00
> /usr/sbin/chilli -c /etc/chilli.conf
> root     21961  0.0  0.6  27164  6124 ?        S    14:02   0:00
> /usr/sbin/chilli -c /etc/chilli.conf
> wifi     22043  0.0  0.2  11748  2248 pts/0    S+   14:02   0:00 grep
> --color=auto chilli
>
>
>
> ************************************************************
> ******************************
>
>
>
> # THIS FILE IS AUTOMATICALLY GENERATED
> cmdsocket       /var/run/chilli.eth1.sock
> unixipc         chilli.eth1.ipc
> pidfile         /var/run/chilli.eth1.pid
> net             10.1.0.0/255.255.0.0
> uamlisten       10.1.0.1
> uamport         3990
> dhcpif          eth1
> uamallowed      "10.1.0.1,10.1.0.1,purewhite.id.au,hotspot.purewhite.id.au
> ,grasehotspot.org"
> uamanydns
> domain "hotspot.lan"
> dns1 "10.1.0.1"
> dns2 "10.1.0.1"
> uamhomepage http://10.1.0.1/grase/uam/hotspot
> wwwdir /etc/chilli/www
> wwwbin /etc/chilli/wwwsh
> uamuiport 4990
> adminuser "CoovaChilli"
> adminpasswd "radmin"
> locationname "GRASE HotSpot"
> radiuslocationname "GRASE_HotSpot"
> radiuslocationid "isocc=,cc=,ac=,network=Grase,"
>
> ************************************************************
> ******************************
>
>
> On Fri, Jan 20, 2017 at 1:02 PM, Timothy White <ti***8@gmail.com>
> wrote:
>
>>
>>
>> On Fri, Jan 20, 2017 at 6:39 AM, emre erdoğan <po***e@gmail.com>
>> wrote:
>>
>>>
>>> The main problem I couldn't solve is Android devices' https problem.
>>> Android devices are not automatically redirected to the login screen like
>>> IOS devices doing. Also most Android users not writing any web address,
>>> they just press G sign on the phone to access Internet. This opens a web
>>> browser to search with Google and it has HTTPS! So user got an IP address
>>> but no Internet! Then he calls me and I told him to open a browser, write
>>> any web address etc. I saw some hotspot systems having SSL certificate to
>>> redirect HTTPS pages (mainly google, facebook, youtube) to the login screen
>>> but there was some browser errors (like XSS attack) also.
>>>
>>>
>>>
>> I'm going to guess that the reason for this is that the updated
>> coova-chilli package hasn't been installed. There was a bug in Coova Chilli
>> that prevented the default Android hotspot detection from working. This
>> should be working now.
>>
>> Regards
>>
>> Tim
>>
>> --
>> 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/gr
>> asehotspot.org/group/grase-hotspot/.
>> To view this discussion on the web visit https://groups.google.com/a/gr
>> asehotspot.org/d/msgid/grase-hotspot/CAESLx0JO08iV0wR7mN3Co
>> 8UYpMCv54WHDgdwQ4iOpum15%3DFgtA%40mail.gmail.com
>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/CAESLx0JO08iV0wR7mN3Co8UYpMCv54WHDgdwQ4iOpum15%3DFgtA%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/CAPz6xh5KNnDqCjWgJZT70Pqq9XYvt
> N2WJh%2B6uhMkS0QEFw%3Dq-w%40mail.gmail.com
> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/CAPz6xh5KNnDqCjWgJZT70Pqq9XYvtN2WJh%2B6uhMkS0QEFw%3Dq-w%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

Thread