2015-09-11 - Re: [GRASE-Hotspot] Need help please!!!

Header Data

From: Timothy White <ti***8@gmail.com>
Message Hash: b1388dad48bb0a298b78bf3effe0614b5941e6626205bfde6e805997593b0557
Message ID: <CAESLx0K109BO+EoLy3ak9XSYWJfRx9YmKV4hmgbh=U3+k6+WdQ@mail.gmail.com>
Reply To: <3AED6B06-22B9-45A9-8319-325D36E185DA@gmail.com>
UTC Datetime: 2015-09-11 22:51:28 UTC
Raw Date: Sat, 12 Sep 2015 15:51:28 +1000

Raw message 

Hi James

An architecture map probably would help. I don't have one at this
stage (maybe open a bug for it?)

dnsmasq is used for DNS for a few reasons. One is that it caches from
upstream (and we can easily set upstream regardless of the system
/etc/resolv.conf file). The other is that we can override the results
from upstream. We use the bogus-nxdomain feature to allow people to
use OpenDNS but without the redirect to OpenDNS for what should be an
NX result. We can also inject our own hosts, like "logout" and
"logoff". The file /etc/dnsmasq.d/01-grasehotspot is generated by
Grase Hotspot, and dnsmasq reads config from it.
DHCP comes directly from Coova Chilli, and should ideally stay that
way. This way, machine accounts are authenticated at DHCP time.

Bind9 is much heavier than Dnsmasq, and doesn't offer all the features
we are using from dnsmasq. Both do caching from upstream, but dnsmasq
is more suited for what we are doing.

Regards

Tim

On Tue, Sep 8, 2015 at 7:44 AM, ADMIN DPHOTSPOT <ad***t@gmail.com> wrote:
> Thank you Tim.
> Sorry for my misunderstanding.
>
> Finally, It makes sense compare to what I've tested yesterday about dhcp and I was looking for answer :
> Isc-dhcp-server I wanted to use is enable to provide services through tun interface and dhcp functionality from dnsmasq was somehow useless: seems that dhcp came directly from chilli. Is it correct?
>
> Using internal dns caching with bind9 looks much more advantageous for services compare to dnsmasq. Can you tell the impact of this custom configuration?
>
> Regards,
>
> James.
>
> Ps : do you have an architecture of services and product, some kind of stream map for a better understanding to newbies ?
> It could help for populating iptables rules too.
>
>
>
>
>
>
>> Le 7 sept. 2015 à 23:01, Timothy White <ti***8@gmail.com> a écrit :
>>
>> We don't actually use the DHCP from dnsmasq, we use the DNS
>> functionality. It's tied into the Admin interface where you can choose
>> upstream DNS servers, OpenDNS filtering etc.
>> If you are running the Hotspot with dnsmasq disabled for DNS, then
>> some features will not work.
>>
>> Regards
>>
>> Tim
>>
>> On Mon, Sep 7, 2015 at 10:47 PM, ADMIN DPHOTSPOT
>> <ad***t@gmail.com> wrote:
>>>
>>> It's possible to deactivate the DNS function from dnsmasq with port=0 config and use the dhcp only that's what I said.
>>>
>>> The DNS function could be provided independently isn't it? Or is it an issue ?
>>>
>>>
>>>> Le 7 sept. 2015 à 08:20, Timothy White <ti***8@gmail.com> a écrit :
>>>>
>>>> Not sure why you are saying to disable dnsmasq and ensure you have
>>>> bind9 running. You want to ensure you don't have bind running, so that
>>>> dnsmasq can run (which is part of the Grase Hotspot).
>>>>
>>>> Regards
>>>>
>>>> Tim
>>>>
>>>>> On Mon, Sep 7, 2015 at 8:27 AM, dphotspot <ad***t@gmail.com> wrote:
>>>>> So far, deactivate DNS from DSNSMASQ by adding "port=0" to dnsmasq.conf
>>>>> Be sure to have a working bind9 service active or providing transparent dns
>>>>> services, relatives to you iptables rules and openDNS proposed by Tim.
>>>>>
>>>>> Le vendredi 14 octobre 2011 11:14:40 UTC+2, fybiyoh a écrit :
>>>>>>
>>>>>> Hello everyone, I have a problem with dnsmasq. the message is that dnsmasq
>>>>>> can not start because of port 53 is in use. does anyone can help me?
>>>>>>
>>>>>> thank you in advance.
>>>>>
>>>>> --
>>>>> 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/dea0c044-44b3-43bf-b9db-0c5073709d64%40grasehotspot.org.
>>>>
>>>> --
>>>> This mailing list is for the Grase Hotspot Project http://grasehotspot.org
>>>> ---
>>>> You received this message because you are subscribed to a topic in the Google Groups "Grase Hotspot" group.
>>>> To unsubscribe from this topic, visit https://groups.google.com/a/grasehotspot.org/d/topic/grase-hotspot/0sQbViDCanI/unsubscribe.
>>>> To unsubscribe from this group and all its topics, 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/CAESLx0JpEyi5-9tMCVbcm4mW6x2kM55aE6ah84zOZev2gzjLKQ%40mail.gmail.com.
>>>
>>> --
>>> 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/8CFECE58-F1CA-4E6A-8F45-D607D8DA29FE%40gmail.com.
>>
>> --
>> This mailing list is for the Grase Hotspot Project http://grasehotspot.org
>> ---
>> You received this message because you are subscribed to a topic in the Google Groups "Grase Hotspot" group.
>> To unsubscribe from this topic, visit https://groups.google.com/a/grasehotspot.org/d/topic/grase-hotspot/0sQbViDCanI/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/CAESLx0%2BOp0EPzupuuO3LZVwEg5xUnpVVRi6dotJFZ8D%3DYfWHmA%40mail.gmail.com.
>
> --
> 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/3AED6B06-22B9-45A9-8319-325D36E185DA%40gmail.com.

Thread