2015-06-11 - Re: [GRASE-Hotspot] Re: Grase nightlyBuilds connection problem

Header Data

From: Timothy White <ti***8@gmail.com>
Message Hash: 9963fce9fdac5a37eaac9d33eceedc61d08fa403250f0f315ec28866383b692f
Message ID: <CAESLx0JGUro0O8c-RLZWQqyX0PmCockOotbUdMq9B6CCtx_Zgg@mail.gmail.com>
Reply To: <94c78ef1-705d-4589-9ce2-6d0afbdd0d51@grasehotspot.org>
UTC Datetime: 2015-06-11 02:13:45 UTC
Raw Date: Thu, 11 Jun 2015 19:13:45 +1000

Raw message 

To keep the list updated, it turns out this is a bug in dnsmasq.
There is a new option --local-service that is to minimise the risk of
dnsmasq being attacked for a DDOS. Unfortunately, what this means is that
it ignores DNS queries from "non local" clients. You'll see messages such
as "Ignoring query from non-local network" in the syslog. What has
happened, is dnsmasq has started before Coova Chilli has setup the tun
interface, so dnsmasq doesn't know that the 10.1.0.0/24 network is local,
and so ignores queries from it.

A restart of dnsmasq after coova chilli has setup it's tun interface fixes
the problem, until you next reboot.

I've not yet found a way to fix this properly, and I'm not yet sure if I
can fix it in the Grase package, or if it'll need to be a bug submitted to
upstream for fixing.

I'll try and discuss it with the dnsmasq developers and see what they
suggest.

Regards

Tim

On Thu, Jun 11, 2015 at 5:19 PM, Sheena Arora <sh***2@gmail.com>
wrote:

> Hi Tim,
>
> We tried this and we are getting the eth1 interface!!!! and the two
> tunnels.
> Unfortunately, we are still not able to connect to grase via our mobile
> phones. Should we try and change the DNS servers to see if it works?
>
> On Thursday, June 11, 2015 at 12:13:35 PM UTC+5:30, timwhite88 wrote:
>>
>>
>>
>> On Thu, Jun 11, 2015 at 4:06 PM, Sheena Arora <sh***.@gmail.com>
>> wrote:
>>
>>> Hi Tim,
>>>
>>> Sorry we couldn't give you proper logs earlier. We are sending you fresh
>>> logs for the commands you've asked us to run.
>>>
>>> Also , I tried executing below commands mentioned in the link
>>>
>>>
>>>
>>> *sudo sed -i -e 's/dns=dnsmasq/#dns=dnsmasq/'
>>> /etc/NetworkManager/NetworkManager.conf*
>>>
>>
>> Can you please try this command again, and then reboot. I'm almost sure
>> that it's the NetworkManager dnsmasq causing issues. You should find that
>> eth1 should come back, if not immediately, after a reboot.
>>
>> 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
> 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/94c78ef1-705d-4589-9ce2-6d0afbdd0d51%40grasehotspot.org
> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/94c78ef1-705d-4589-9ce2-6d0afbdd0d51%40grasehotspot.org?utm_medium=email&utm_source=footer>
> .
>

Thread