2015-11-06 - Re: [GRASE-Hotspot] Re: New install and problems dnsmasq

Header Data

From: Timothy White <ti***8@gmail.com>
Message Hash: 4234332588558af4c1b58db2c120ceb2b768c708829abef04077329bca88e818
Message ID: <CAESLx0JYW1pOA1+_4UHtWqTMJXwA-cmtUnyR5EqjF2QA8SNasQ@mail.gmail.com>
Reply To: <3274dea9-f26e-4c98-afba-161ff89385ed@grasehotspot.org>
UTC Datetime: 2015-11-06 05:37:12 UTC
Raw Date: Fri, 06 Nov 2015 22:37:12 +1000

Raw message 

On Fri, Nov 6, 2015 at 10:18 AM, Jean Létourneau <ve***t@gmail.com> wrote:

> Good day all,
>
>
>         I solve my problem, probably not the right way, but its working.
> This is what I have done.
>
>
>  After several hours of reading, rebooting, modifying files and testing, I
> found my  port 53 was used by  ‘named’, so I went  to /usr/sbin and did
> chmod –x named , re-booted and now Grase work.
>
>
> Like I said it’s probably not the right way but I am not a Linux guru. I
> am posting what I have done for the guru’s.
>
>  I  noticed at re-boot and error, but was too fast to read what it was
> exactly, but I think it’s something like ‘’ name service bind9 ‘’. So that
> proves me it was not the right thing to do.
>

Interesting
It seems you have bind9 (named) installed. This probably means when you did
your server install, you selected DNS server as one of the options.

One solution is to mark my grase-conf-dnsmasq package as conflicting with
Bind. However, this means someone who knows what they are doing, can't
override how it's setup.

Any suggestions of a better way to handle this? Big warning in the Admin
interface if we detect bind? Or are people OK with us blocking the
installation of bind on a Grasehotspot server?

Regards

Tim

Thread