2016-05-24 - Re: [GRASE-Hotspot] dhcp lease pool after default install

Header Data

From: Timothy White <ti***8@gmail.com>
Message Hash: 5a04131d15afde1988b9abd0d658cf22e4cd90282d992b8632e91e3d256783fd
Message ID: <CAESLx0LB7vTSfYK61=az5ajWZgGtHvr+4ABeyLZ=crjpVtNnrQ@mail.gmail.com>
Reply To: <84870b6b-dc3a-4e10-ad78-a1ffdaa094b4@grasehotspot.org>
UTC Datetime: 2016-05-24 05:05:17 UTC
Raw Date: Tue, 24 May 2016 22:05:17 +1000

Raw message 

I'm not sure why, but the range in the database isn't the default one. Have
you since changed it?


   1. #chilli_lanip 10.0.0.2
   2. #chilli_wanif eth0
   3. #chilli_lanif eth1
   4. #chilli_network 10.0.0.0
   5. #chilli_netmask 255.0.0.0


If you changed the netmask to 255.0.0.0, then even with an IP of 10.1.0.1
as the server IP, it would start the DHCP range at 10.0.0.1

A good tool to see ip ranges is sipcalc. You can see that the start of the
range is 10.0.0.1. You also have a stupidly large IP range. You should
reduce your netmask to something reasonable, such as 255.255.255.0, or
255.255.254.0 if you need more than 250 odd clients.

Tim

$sipcalc 10.1.0.1/8
-[ipv4 : 10.1.0.1/8] - 0

[CIDR]
Host address - 10.1.0.1
Host address (decimal) - 167837697
Host address (hex) - A010001
Network address - 10.0.0.0
Network mask - 255.0.0.0
Network mask (bits) - 8
Network mask (hex) - FF000000
Broadcast address - 10.255.255.255
Cisco wildcard - 0.255.255.255
Addresses in network - 16777216
Network range - 10.0.0.0 - 10.255.255.255
Usable range - 10.0.0.1 - 10.255.255.254



On Tue, May 24, 2016 at 9:34 PM, 'christopher' via Grase Hotspot <
gr***t@grasehotspot.org> wrote:

> Hello Tim
>
> Here is the support information as requested:
>
> https://paste.grasehotspot.org/view/76b9031d
>
> With regards to something else giving out the incorrect leases, that is
> not possible.  Reason I can confidently state that is that this was on a
> fresh install of Debian.
>
> When I encountered that error ie after the fresh install I did indeed
> check in radmin page and the 10.1.0.1 ip was listed there.  I then did a
> complete wipe of the harddrive again and a fresh install of Debian.  The
> wireless router before this installation had an ip address of 192.168.0.1
> and dhcp was not enabled on it as we were using a windows based commercial
> hotspot which handled the dhcp itself, and that harddrive is physically
> disconnected from the motherboard.
>
> I am totally puzzled as to where the dhcp range was being allocated from.
> I am the only one who administers the network.  I checked after the second
> clean installation and the only dhcp that is installed is dhcp-client.
>
> The  /etc/dnsmasq.d/01-grasehotspot after both installs had shown the
> default per your instructions ip address of 10.1.0.1.
>
> I could accept that on a server that had been running that things can go
> wrong, which is why I find that after I have been testing things out and
> made changes that I do a complete re-installation of the operating system
> prior to putting the server into use.
>
> Before installing gracehotspot or anything else I purged systemd.  I will
> not use systemd in a production environment at this stage, even though I
> have tested it out for a couple of years on my own computer.
>
> I normally compile the whole os from scratch, but as the owner of the
> backpackers is not an IT person it is better to have a system that can get
> regular security updates.
>
> I am glad to be finally rid of windows 2003 server.
>
> It may well be that we will never work out exactly where it was picking
> the ip pool up from.  I just hate mysteries like that.
>
> Regards,
>
> Chrristopher.
>
>
> On Tuesday, 24 May 2016 22:09:04 UTC+12, timwhite88 wrote:
>>
>> Hi Christopher
>>
>> It may help to collect support information as stated on
>> https://grasehotspot.org/support/collecting-support-information/
>> The IP range that is served is set in the Admin interface. You can see on
>> the demo version the correct location (
>> http://demo.grasehotspot.org/grase/radmin/netconfig)
>>
>> You can also check /etc/dnsmasq.d/01-grasehotspot to see that the
>> settings are actually being sent as expected. That file is used by dnsmasq
>> and coova-chilli to load the network range. I wonder if you somehow have
>> something other than coova-chilli serving DHCP, and hence that's why it's
>> not appear in the DHCP leases page, and also giving the correct lease.
>>
>> I have a Debian Jessie testing machine, so I'll check that DHCP leases
>> page works for me.
>>
>> Tim
>>
>> On Tue, May 24, 2016 at 6:24 PM, 'christopher' via Grase Hotspot <
>> gr***.@grasehotspot.org> wrote:
>>
>>> Hello,
>>>
>>> After attempting to get daloradius, freeradius, mysql and dhcp to work
>>> nicely together I discovered grasehotspot so I did a fresh install of
>>> Debian Jessie.  No desktop just LAMP and ssh server.
>>>
>>> After installing gracehotspot the admin url etc is 10.1.0.1, so I had
>>> assumed that this is the range that would hand out ip addresses.  After
>>> people failing to obtain an ip address I checked the iptables --list and it
>>> showed all the forwarding rules with the 10.1.0.1 range as you would
>>> expect.  What I did not expect and really would appreciate knowing where in
>>> the config files to find it, is that for some bizzar reason it was
>>> allocating ip addresses in the 10.0.0.0 range.
>>>
>>> I ended up changing the ip address on the wireless router to the
>>> 10.0.0.x range, and having to change the default 10.1.0.1 settings used for
>>> the installation.
>>>
>>> The setup we have here is that there is an tplink wireless router on the
>>> wall (dhcp is disabled on it so no dhcp there) with the ethernet cable
>>> plugged into a straight ethernet port rather than the wan port.  This then
>>> goes to the server and plugs into eth1.  Eth0 goes to another tplink
>>> gigabit wireless router that is plugged into the Fibre access point.
>>> Wireless is turned off for this device.
>>>
>>> I had a poke around in the mysql database using phpmyadmin but was not
>>> able to find it there.
>>>
>>> As previous people have mentioned, the re-directs to the login page were
>>> not working here either.  We are a backpackers and have people with
>>> tablets, iphones, mac's windows pc's android phones of various ages all
>>> behaving the same way.
>>>
>>> I downloaded the fixed version of coova-chilli and it started working.
>>>
>>> The one thing that is not working, and I would like it to, is that on
>>> the dhcp leases page nothing is shown there.  It all gets posted to
>>> syslog.  What file do I need to change in order to make the leases show up
>>> there?
>>>
>>> Regards,
>>>
>>> Christopher.
>>>
>>> --
>>> 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***.@grasehotspot.org.
>>> To post to this group, send email to gr***.@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/48630296-537e-4fff-9a92-234766cea8a2%40grasehotspot.org
>>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/48630296-537e-4fff-9a92-234766cea8a2%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
> 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/84870b6b-dc3a-4e10-ad78-a1ffdaa094b4%40grasehotspot.org
> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/84870b6b-dc3a-4e10-ad78-a1ffdaa094b4%40grasehotspot.org?utm_medium=email&utm_source=footer>
> .
>

Thread