2012-08-26 - [GRASE-Hotspot] define dhcp range probably unnecessary
Header Data
From: Bob Hunt <bo***2@gmail.com>
Message Hash: a3027ab0ada52ff5debf94c4a914044f718031da728a518c337b2d99c31e0f1e
Message ID: <CAA-jMMTpCGp-QfviwkKVxw5ZoJFPvHbidA1Yk6hyHZx=LV244g@mail.gmail.com>
Reply To: N/A
UTC Datetime: 2012-08-26 19:02:57 UTC
Raw Date: Mon, 27 Aug 2012 12:02:57 +1000
Raw message
Hi Tim and All,
To define dhcp range chilli uses, http://www.coova.org/node/1865
advises to edit /etc/chilli/local.conf and add;
dhcpstart 10
dhcpend 253
But what worked for me is;
dhcpstart=10
dhcpend=253
And this only seemed to work if the netmask is 255.255.255.0. For a
broader netmask I think you may need increase dhcpend above 255 (I
read something somewhere about this but haven't tested it).
A reboot is needed to apply the changes and to get chilli working
again. After the reboot, /etc/chilli/local.conf, appearsto have been
rewritten so that it looks as if you'd never edited it at all but the
changes are in effect! I've no idea how to check on the running system
what the DHCP settings are now set to so I think writing it down
somewhere is a good idea.
I made changes to the dhcp range as I was concerned about potential IP
address conflicts with my static addresses but I've now undone the
changes and it looks like Grase is doing a good job issuing dhcp
addresses to "computer account" devices which match the device static
IP settings.
Behind Grase I'm running a layer 2 mesh network, which needs static
addresses and in order to get Astrerisk (voip) working across the
network, it seems that each mesh node needs to have a Grase "computer
account" set up and to have its static IP address to be within the
shared address space. I'm pleased that Grase appears to accommodate
this setup.
Cheers,
Bob
On Tue, Aug 21, 2012 at 7:11 AM,
<gr***t@lists.sourceforge.net> wrote:
> Send Grase-hotspot mailing list submissions to
> gr***t@lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/grase-hotspot
> or, via email, send a message with subject or body 'help' to
> gr***t@lists.sourceforge.net
>
> You can reach the person managing the list at
> gr***r@lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Grase-hotspot digest..."
>
>
> Today's Topics:
>
> 1. Re: Batch tickets (Timothy White)
> 2. Re: UDP traffic (Timothy White)
> 3. Re: Define dhcp range (Timothy White)
> 4. Re: Define dhcp range (Johnny Solbu)
> 5. Got stuck in v3.6.3 (Benedict Raymond)
> 6. Re: UDP traffic (Shamih Sami)
> 7. New Voucher System (Was Re: Paypal integration ??) (Timothy White)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 18 Aug 2012 07:15:22 +1000
> From: Timothy White <ti***8@gmail.com>
> Subject: Re: [GRASE-Hotspot] Batch tickets
> To: GRASE Hotspot General Discussions
> <gr***t@lists.sourceforge.net>
> Message-ID:
> <CA***A@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> This shouldn't be hard to do. Just file a bug at trac.grasehotspot.org
> and I'll implement it.
> If you can't wait, find in the code the right parts and update it.
> However your changes will get overridden each update.
>
> Tim
>
> On Mon, Aug 6, 2012 at 6:45 AM, Prem Kang <pr***g@gmail.com> wrote:
>> Hi,
>>
>> Is it possible to simplify the login using a ticket. It currently used a 8
>> digit username and 8 digit password and I would like to use ideally a fixed
>> username and a shorter (5 digit) password. If thats not possible, the just
>> shortening both username and password to 5 digits would do.
>>
>> Thanks
>>
>> Prem
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Grase-hotspot mailing list
>> Gr***t@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/grase-hotspot
>>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 18 Aug 2012 07:16:42 +1000
> From: Timothy White <ti***8@gmail.com>
> Subject: Re: [GRASE-Hotspot] UDP traffic
> To: GRASE Hotspot General Discussions
> <gr***t@lists.sourceforge.net>
> Message-ID:
> <CAESLx0JkDwwjNbS5LmshCVDNkOSpckEUSB68Dmo=q0***Q@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi Shamih.
>
> Interesting. Are you sure it's passing through? Remember UDP is
> connectionless, so the sending machine can send to it's heart content,
> however the packets shouldn't be passing through.
> I'll do some tests to make sure.
>
> Tim
>
> On Wed, Aug 15, 2012 at 4:30 PM, Shamih Sami <sa***m@me.com> wrote:
>> Dear Tim,
>>
>> I have down little bit experiment myself on fusion with Ubuntu 12.04 x64 LTS
>> and two XP machine one behind Grase, the other one using Grase dhcp.
>> I use 4GB voucher, did UDP follow from jperf between XP machine behind
>> Grase. when it uses 4GB, account expires. but traffic still pass-through,
>> and i notice UDP traffic pass-through even not logged in.
>>
>> Shamih
>> 7944442
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Grase-hotspot mailing list
>> Gr***t@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/grase-hotspot
>>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 18 Aug 2012 07:26:05 +1000
> From: Timothy White <ti***8@gmail.com>
> Subject: Re: [GRASE-Hotspot] Define dhcp range
> To: GRASE Hotspot General Discussions
> <gr***t@lists.sourceforge.net>
> Message-ID:
> <CAESLx0+=J7***g@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Ideally you don't want your AP's in the same ip range as your clients.
> It's a security risk.
>
> See http://www.coova.org/node/1865 for some information on dhcpstart
> and dhcpend.
> Open a ticket at trac.grasehotspot.org and I'll implement it for the
> next release.
>
> Tim
>
>
> On Thu, Aug 16, 2012 at 9:15 AM, Johnny Solbu <so***u@solbu.net> wrote:
>> Is it possible to define which IP range the hotspot assign clients?
>>
>> We have 4 access points which we want to have an IP address on, so we can configure them from the local network.
>> Lets say we use 10.0.1.2 <-> 10.0.1.5 on the APs so we can configure them. How do we tell Grase hotspot, or dnsmasq, to limit it's dhcp range to, say 10.0.1.10 <-> 10.0.1.254?
>>
>> --
>> Johnny A. Solbu
>> web site, http://www.solbu.net
>> PGP key ID: 0xFA687324
>> ********************************
>> Kom Arbeidslyst og treng deg p?,
>> her skal du motstand finne.
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Grase-hotspot mailing list
>> Gr***t@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/grase-hotspot
>>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Sat, 18 Aug 2012 00:16:37 +0100
> From: Johnny Solbu <so***u@solbu.net>
> Subject: Re: [GRASE-Hotspot] Define dhcp range
> To: gr***t@lists.sourceforge.net
> Message-ID: <201208180116.40860.so***u@solbu.net>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Friday 17 August 2012 23:26, Timothy White wrote:
>> Ideally you don't want your AP's in the same ip range as your clients.
>> It's a security risk.
>
> Then what do you recommend?
> Idealy we'd like to use a 192.168.x.x range for managing the APs.
>
> --
> Johnny A. Solbu
> web site, http://www.solbu.net
> PGP key ID: 0xFA687324
> ********************************
> Kom Arbeidslyst og treng deg p?,
> her skal du motstand finne.
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 189 bytes
> Desc: This is a digitally signed message part.
>
> ------------------------------
>
> Message: 5
> Date: Sat, 18 Aug 2012 00:45:11 +0100
> From: Benedict Raymond <to***d@yahoo.com>
> Subject: [GRASE-Hotspot] Got stuck in v3.6.3
> To: "gr***t@lists.sourceforge.net"
> <gr***t@lists.sourceforge.net>
> Message-ID: <F5***D@yahoo.com>
> Content-Type: text/plain; charset=us-ascii
>
> Hello Tim,
> I just can't update to the latest release, the repo link seems disappear from my source.list. Please what do I do. I don't want to mess up with the cafe server now. More grease to your elbow Cheers
>
>
> ------------------------------
>
> Message: 6
> Date: Sat, 18 Aug 2012 20:25:51 +0500
> From: Shamih Sami <sa***m@me.com>
> Subject: Re: [GRASE-Hotspot] UDP traffic
> To: GRASE Hotspot General Discussions
> <gr***t@lists.sourceforge.net>
> Message-ID: <A1***1@me.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Dear Tim,
>
> Sorry my mistake. stupid not check on host side properly.
> No issue at all, any connection terminates on the spot expires or when reach the limit.
>
> Regards
>
> Shamih Sami
> sa***m@me.com
>
>
>
> On Aug 18, 2012, at 2:16 AM, Timothy White <ti***8@gmail.com> wrote:
>
>> Hi Shamih.
>>
>> Interesting. Are you sure it's passing through? Remember UDP is
>> connectionless, so the sending machine can send to it's heart content,
>> however the packets shouldn't be passing through.
>> I'll do some tests to make sure.
>>
>> Tim
>>
>> On Wed, Aug 15, 2012 at 4:30 PM, Shamih Sami <sa***m@me.com> wrote:
>>> Dear Tim,
>>>
>>> I have down little bit experiment myself on fusion with Ubuntu 12.04 x64 LTS
>>> and two XP machine one behind Grase, the other one using Grase dhcp.
>>> I use 4GB voucher, did UDP follow from jperf between XP machine behind
>>> Grase. when it uses 4GB, account expires. but traffic still pass-through,
>>> and i notice UDP traffic pass-through even not logged in.
>>>
>>> Shamih
>>> 7944442
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond. Discussions
>>> will include endpoint security, mobile security and the latest in malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> Grase-hotspot mailing list
>>> Gr***t@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/grase-hotspot
>>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Grase-hotspot mailing list
>> Gr***t@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/grase-hotspot
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 7
> Date: Tue, 21 Aug 2012 07:11:46 +1000
> From: Timothy White <ti***8@gmail.com>
> Subject: [GRASE-Hotspot] New Voucher System (Was Re: Paypal
> integration ??)
> To: GRASE Hotspot General Discussions
> <gr***t@lists.sourceforge.net>
> Message-ID:
> <CA***g@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Tue, Aug 14, 2012 at 11:35 PM, Hans van de Voorde
> <ha***s@van-de-voorde.com> wrote:
>> Hi Tim,
>> Great that you are back in bussiness with the new development system.
>> I hope that it is also getting better on the hours of sleep per night.
>> I see that things are moving again and asked my self where you are at with
>> the Paypal project.
>> I know that you had a test verion working a couple of months ago. Is there
>> any chance that it will be ported into an official release?
>
> Glad you asked!
>
> Due to a discussion with an interested 3rd party who wants to pay for
> a specific payment gateway, I've started the paypal stuff from
> scratch, and it's for the better.
> Here's a good opportunity to explain to everyone how the new system
> will work, and why.
>
> First, some history. The original system only had users, no concept of
> tickets, and the pricing system for the place it was written for, was
> linear. $X for 1Mb or $Y for 1minute. It also didn't matter from an
> accounting point of view if there was records of the $ amount sold,
> the $ amount was just a guide as all payments happened manually in
> cash.
>
> This doesn't scale so well to other organisations, for example most
> ISP's give you a discount if you purchase more quota. Hotels/Motels
> love you buying the bigger internet pack, because chances are you
> won't use it all, so even though it was cheaper per Mb, the hotel
> actually wins out in the majority of use cases. It also doesn't allow
> a $ value to be placed on other aspects of the account, for example
> high quota, but short usage time vs high quota and long usage time. Or
> bandwidth limits, etc.
>
> So the first thing I'm in the process of doing (90% done) is
> disconnecting data/time limits from $ values, and making them
> customisable however the admin wants, no more linear options, you
> choose the options!
>
> When then have groups, (which we already have implemented) that define
> a "ticket" type with it's default settings and limits. You'll still be
> able to create users manually in a group, and inherit the group
> settings are define your own settings at creation time (within a group
> still).
>
> Then we'll have "vouchers" (naming still to be worked out) that define
> a $ value, and some limits for the $ value. All vouchers will still
> fall under a group, and will be able to be purchased as ether an
> initial voucher, or a topup. i.e. you charge them $10 for the first
> 100Mb, but topups of 100Mb are only $5. Each group will define a
> voucher group, which helps define which vouchers can topup which
> vouchers. Basically, topups have to be within the same group, this
> ensures that settings like bandwidth limits are maintained, and they
> don't purchase a cheap topup in a group with less restrictive
> bandwidth, but still have all their time quota.
>
> The purchasing system will consist of selecting a voucher type,
> (group), then the initial purchase or the topup purchase. It'll then
> use a plugin system to allow different payment gateways to be used
> (including a manual Admin gateway that allows the manual issuing of
> vouchers, i.e. a cash register) and finally the creation of the
> voucher. There will probably be a way to even create vouchers that are
> tied to something, like the computer MAC address, or a phone number
> and uses SMS to authenticate the user.
>
> I hope that gives everyone a clear image of the direction I'm going.
> It should clear up the UI a bit as well, as some of the legacy stuff
> cluttered up the screen. Paypal will probably be the second public
> gateway written, with Manual being the first!
>
> Tim
>
>
>
> ------------------------------
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
> ------------------------------
>
> _______________________________________________
> Grase-hotspot mailing list
> Gr***t@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/grase-hotspot
>
>
> End of Grase-hotspot Digest, Vol 15, Issue 5
> ********************************************
--
Bob Hunt
20 Clarke Street
Wyndham
NSW 2550
Australia
Phone/fax 61 (0)2 64942030
Thread
-
Return to August 2012
-
Return to “Bob Hunt <bo***2@gmail.com>”
-
2012-08-26 (Mon, 27 Aug 2012 12:02:57 +1000) - [GRASE-Hotspot] define dhcp range probably unnecessary - Bob Hunt <bo***2@gmail.com>