2015-09-25 - Re: [GRASE-Hotspot] Turn off DHCP for coova chilli

Header Data

From: Timothy White <ti***8@gmail.com>
Message Hash: 0690300de72d610f4047c701d4ccb20b4a982a30755e3820ba2259ca446a2eee
Message ID: <CAESLx0L=KPyaJg7QDXmg5WBUaC122OpoBa9pvGqNQMKe_8CcBw@mail.gmail.com>
Reply To: <51177490-7EB1-4399-8DC5-CC093B53964C@argyle.com.au>
UTC Datetime: 2015-09-25 13:20:13 UTC
Raw Date: Sat, 26 Sep 2015 06:20:13 +1000

Raw message 

Hi Joseph

You should be able to just set the DNS servers in the Grase Hotspot Admin
interface, and the Hotspot server should forward all requests to the
upstream DNS server, which would be the AD server. They should then be able
to login. As Dave already said, you need to ensure the DHCP is passing out
the correct addresses for the AD network.

You can see from here https://support.microsoft.com/en-us/kb/247811 that
DNS is key to finding a domain controller. So we just need to forward
requests to the AD server. I don't have a test environment for this, but it
should work as I work in an AD environment regularly with a DNS forwarder.
The only downside to this setup is that you can't look at the AD servers
DHCP leases to find a client, and clients often can't register in the AD
servers DNS. These shouldn't affect clients. However, for a windows server,
it may cause issues, so you should set them up statically pointing to the
windows AD DNS server.

Regards

Tim

On Thu, Sep 24, 2015 at 11:38 PM, David Wilson <da***e@argyle.com.au> wrote:

> Hi Joseph,
>
> It is not really something that Grase is currently designed to do.
> But you could (if you are brave) edit the functions file in /etc/chilli/
>
> Around about line 55
>
> Replace
>
> HS_DNS1=${HS_DNS1:-$HS_DNS}
> HS_DNS1=${HS_DNS1:-$(grep '^nameserver' /etc/resolv.conf | head -n1 | awk '{print
> $2}’)}
>
> with
>
> HS_DNS1=‘192.168.2.2'
> HS_DNS2=‘192.168.2.2'
>
> In fact if you just add the last two lines and then just put a # in front
> of the existing ones then that will work too.
>
>
> I am no Windows guru and so there is no guarantee that the DNS resolution
> alone will be all that you need - but it may work - or at least get you
> closer to a solution.
> However you will also need to make Grase hand out IP’s in the same network
> at your DC.
> You can set the LAN IP address in Grase web admin - Network Settings
> and you will need to set the DHCP Start and End in Grase web admin -
> CovaChilli Settings so as to avoid IP address conflicts.
>
>
> I have to say - I am not sure what you are doing is the best thing for
> what you need - but I understand that sometimes you just have to make
> something work with minimal investment.
>
> Dave
>
>
>
> On 22 Sep 2015, at 5:12 pm, Joseph Opio <jo***1@gmail.com> wrote:
>
> I am a systems admin in a school and I am trying to manage bandwidth of
> every machine on the network but blocking out all new computers on the
> network from accessing internet. In some cases, I want some computers to
> have connectivity at specific times of the day. but now, I have failed to
> adapt this server to my network. when ever i try to deactivate DHCP on my
> DC, some machines cant log on to the domain.
>
>
> This is my network topology.
>
>
> <https://lh3.googleusercontent.com/-xIBLOKuZcRU/VgD-AKw6tDI/AAAAAAAADew/IZ-S0qsEVKE/s1600/CADE11.jpg>
>
> I just had a view of deactivating DHCP on grase hotspot and I failed
>
> Note that: my DC is on the same lan with every machine on the network
>
>
> Thanks 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/e1faf4fe-93a6-4bb7-a0b9-f858c7915c9d%40grasehotspot.org
> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/e1faf4fe-93a6-4bb7-a0b9-f858c7915c9d%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***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/51177490-7EB1-4399-8DC5-CC093B53964C%40argyle.com.au
> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/51177490-7EB1-4399-8DC5-CC093B53964C%40argyle.com.au?utm_medium=email&utm_source=footer>
> .
>

Thread