2016-11-26 - Re: [GRASE-Hotspot] Re: Version of coova-chilli is outdated

Header Data

From: Timothy White <ti***8@gmail.com>
Message Hash: 2514c256ab9c8a4486d0139ebafd111725a2c4ee2a3ff99a02a3b3d18d25aa66
Message ID: <CAESLx0+_Nu_3htw-nLUd_8F_TKpFxUm46VDCgqK92ANQrmietw@mail.gmail.com>
Reply To: <CAESLx0+PvCU7ZBAkk+CQC-M_2KYHmEC4bOOG=XTvLZk50NhLMQ@mail.gmail.com>
UTC Datetime: 2016-11-26 13:51:01 UTC
Raw Date: Sun, 27 Nov 2016 06:51:01 +1000

Raw message 

And i386 builds have worked too! Now for the testing!

On Fri, Nov 25, 2016 at 9:49 PM, Timothy White <ti***8@gmail.com> wrote:

> ARM builds are now working. All builds are still not tested. Hopefully
> i386 will be working shortly.
>
> Regards
>
>
> Tim
>
> On Sat, Nov 19, 2016 at 4:28 AM, Hotspotuser <jo***s@algardata.pt>
> wrote:
>
>> Excelent! Monday i'll setup a machine just to check this out... and
>> report back (when i can).
>>
>> segunda-feira, 14 de Novembro de 2016 às 21:05:56 UTC, timwhite88
>> escreveu:
>>>
>>> I assumed when I made the Gitlab project public, that the builds would
>>> be public. Fixed now.
>>> If you head to https://gitlab.com/grase/coova-chilli/builds you can see
>>> the automated builds. Only AMD64 builds are working at the moment. If you
>>> then go into the trusty-amd64 build that completed, you can download the
>>> build artifacts which includes a .deb file you can manually install.
>>>
>>> Please note, that these packages have had no testing. I'll do manual
>>> testing of packages once I get i386 builds working, and once I've done
>>> basic testing of packages I'll put them in the nightly repo.
>>>
>>> Regards
>>>
>>> Tim
>>>
>>> On Tue, Nov 15, 2016 at 4:33 AM, Hotspotuser <jo***.@algardata.pt>
>>> wrote:
>>>
>>>> Tim
>>>>
>>>> When can we have a install script, to test it out?
>>>>
>>>> domingo, 13 de Novembro de 2016 às 11:53:11 UTC, timwhite88 escreveu:
>>>>>
>>>>> As a further update. I believe all the essentials to make it work are
>>>>> now in there. There are some core modifications not in that I need to test,
>>>>> however without them the things that may fail are:
>>>>>
>>>>>    - Traffic for showing the status page may be counted towards a
>>>>>    data quota instead of being excluded
>>>>>    - Some of the status window Javascript might be missing
>>>>>    information (however I believe this won't happen with the 3.8.0 version as
>>>>>    we changed all that but the patches were still in the old package)
>>>>>
>>>>> Regards
>>>>>
>>>>> Tim
>>>>>
>>>>> On Sun, Nov 13, 2016 at 9:34 PM, Timothy White <ti***.@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Slowly
>>>>>>
>>>>>> I used to compile each package by hand, which is a pain, especially
>>>>>> if I want to support Debian and Ubuntu, as sometimes there are differences
>>>>>> (or hacks for a single package).
>>>>>>
>>>>>> I'm currently working on a fork of the new Coova Chilli git repo,
>>>>>> with all our changes in a branch. This will make it easier in the future to
>>>>>> upgrade versions. It'll also show us what code changes are actually needed.
>>>>>>
>>>>>> You can view the branch on either Gitlab (
>>>>>> https://gitlab.com/grase/coova-chilli/tree/grase-1.3.2) or Github (
>>>>>> https://github.com/GraseHotspot/coova-chilli/tree/grase-1.3.2). Why
>>>>>> both? Well Gitlab CI is amazing, supporting building multiple "products" at
>>>>>> a time. Other CI's do support Matrix builds, but sometimes it's more
>>>>>> complex than that. Gitlab will mirror Github's repo, and run the builds for
>>>>>> us that we need. (Hopefully, when I get anything other than the AMD64
>>>>>> builds working).
>>>>>>
>>>>>> At the moment, I've got the bare minimum of changes in for the Grase
>>>>>> Hotspot. More changes will come shortly to bring it inline with previous
>>>>>> packages (once I read all the Changes in the new versions and only bring
>>>>>> the features we still need). Once I get enough in, I'll put the builds in
>>>>>> the nightly repo.
>>>>>>
>>>>>> To make my life easier, for those who want to test new packages, what
>>>>>> architecture and Ubuntu/Debian versions are you running?
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> Tim
>>>>>>
>>>>>>
>>>>>> On Wed, Nov 9, 2016 at 11:11 PM, Hotspotuser <jo***.@algardata.pt>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Tim
>>>>>>>
>>>>>>> Any news on the upgrading of CoovaChilli to latest version in Grase?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> domingo, 14 de Agosto de 2016 às 11:47:27 UTC+1, timwhite88 escreveu:
>>>>>>>>
>>>>>>>> Hi Jose
>>>>>>>>
>>>>>>>> Sorry for the delays. I've had a quick look at getting the latest
>>>>>>>> Coova-chilli going. The main things to look at are ensuring the config and
>>>>>>>> ipup.sh files from https://github.com/GraseH
>>>>>>>> otspot/grase-coova-chilli/tree/master/debian/extra_files are
>>>>>>>> installed. The other patches and changes I've made are less important
>>>>>>>> depending on your situation. You'll probably want
>>>>>>>> '--enable-gardenaccounting'. In theory, this should remove the need for one
>>>>>>>> of my patches, but my testing hasn't conclusively proven that yet.
>>>>>>>> Also, the debian packages built by upstream currently treat all the
>>>>>>>> files in /etc/chilli/ as config files, which while correct, lots of the
>>>>>>>> files in there aren't config files, which causes issues on each upgrade.
>>>>>>>> This just means you'll have to answer debconf questions regularly about
>>>>>>>> overwriting changed files. I do have a fix for this in my repo.
>>>>>>>> Upstream also defaults to not starting Coova Chilli, so you'll need
>>>>>>>> to edit /etc/default/coova-chilli after install to enable it.
>>>>>>>>
>>>>>>>> Now that upstream uses Git, I'm in the process of trying to take
>>>>>>>> upstream's git repo, and just create a branch for our patches, with the
>>>>>>>> hope to get some of them accepted upstream in the future.
>>>>>>>>
>>>>>>>> In theory though, right now you can build a debian package from
>>>>>>>> upstream, copy in the config and ipup.sh, and most things should work.
>>>>>>>>
>>>>>>>> Sorry for the delays.
>>>>>>>>
>>>>>>>> Tim
>>>>>>>>
>>>>>>>> On Fri, Jul 22, 2016 at 1:06 AM, Hotspotuser <jo***.@algardata.pt
>>>>>>>> > wrote:
>>>>>>>>
>>>>>>>>> Any news on this?
>>>>>>>>>
>>>>>>>>> Tim, care to share the ./configure parameters used in GRASE so
>>>>>>>>> that we can try to tackle this ourselves?
>>>>>>>>>
>>>>>>>>> Got Coova-Chilli 1.3.4 installed today, but im guessing i got the
>>>>>>>>> wrong parameters for ./configure.
>>>>>>>>>
>>>>>>>>> ./configure --enable-chilliquery --enable-coa --enable-radproxy --
>>>>>>>>> enable-dhcpradius --enable-dnslog --enable-uamdomainfile --enable-ieee8021q
>>>>>>>>> --enable-json --enable-largelimits --enable-leakybucket --enable-uamanyip
>>>>>>>>> --enable-uamuiport --enable-libjson
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> sábado, 25 de Junho de 2016 às 10:24:42 UTC+1, christopher
>>>>>>>>> escreveu:
>>>>>>>>>
>>>>>>>>>> Hello,
>>>>>>>>>>
>>>>>>>>>> The version of coova-chilli being used in grase hotspot is two
>>>>>>>>>> years
>>>>>>>>>> outdated.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> They have released another version although the numbering is not
>>>>>>>>>> what I
>>>>>>>>>> would call conventional.
>>>>>>>>>>
>>>>>>>>>> If you take a look in the system log files you will see redir.c
>>>>>>>>>> client
>>>>>>>>>> time outs and performance issues when this is happening.
>>>>>>>>>>
>>>>>>>>>> On their new mailing list one of their current development team
>>>>>>>>>> told
>>>>>>>>>> someone who brought this up to upgrade.
>>>>>>>>>>
>>>>>>>>>> As I am not sure of exactly what files are patched I am unable to
>>>>>>>>>> upgrade
>>>>>>>>>> to see if this issue has been fixed.  They claim to have fixed a
>>>>>>>>>> number of
>>>>>>>>>> errors from the old code base.
>>>>>>>>>>
>>>>>>>>>> I know that there is one patch listed on the grase wiki but is
>>>>>>>>>> this the
>>>>>>>>>> only changes that have to be made?
>>>>>>>>>>
>>>>>>>>>> It would be nice for me to be able to upgrade and forget about it
>>>>>>>>>> until
>>>>>>>>>> things change.
>>>>>>>>>>
>>>>>>>>>> Also there is an issue with Debian and Ubuntu with network
>>>>>>>>>> traffic
>>>>>>>>>> stopping if you have both ipv4 and ipv6 enabled.  You need to
>>>>>>>>>> disable ipv6
>>>>>>>>>> to prevent the network interfaces from being constantly being
>>>>>>>>>> reconfigured.
>>>>>>>>>>
>>>>>>>>>> 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/gr
>>>>>>>>> asehotspot.org/group/grase-hotspot/.
>>>>>>>>> To view this discussion on the web visit
>>>>>>>>> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-h
>>>>>>>>> otspot/6d0f774c-8763-4f07-b69a-53541133dd18%40grasehotspot.org
>>>>>>>>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/6d0f774c-8763-4f07-b69a-53541133dd18%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***.@grasehotspot.org.
>>>>>>> To post to this group, send email to gr***.@grasehotspot.org.
>>>>>>> Visit this group at https://groups.google.com/a/gr
>>>>>>> asehotspot.org/group/grase-hotspot/.
>>>>>>> To view this discussion on the web visit
>>>>>>> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-h
>>>>>>> otspot/383c2c27-6f0d-4a7b-b33b-469fc9d8781b%40grasehotspot.org
>>>>>>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/383c2c27-6f0d-4a7b-b33b-469fc9d8781b%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***.@grasehotspot.org.
>>>> To post to this group, send email to gr***.@grasehotspot.org.
>>>> Visit this group at https://groups.google.com/a/gr
>>>> asehotspot.org/group/grase-hotspot/.
>>>> To view this discussion on the web visit https://groups.google.com/a/gr
>>>> asehotspot.org/d/msgid/grase-hotspot/57780e46-8779-49fc-ab39
>>>> -a5a88476d06c%40grasehotspot.org
>>>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/57780e46-8779-49fc-ab39-a5a88476d06c%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/gr
>> asehotspot.org/group/grase-hotspot/.
>> To view this discussion on the web visit https://groups.google.com/a/gr
>> asehotspot.org/d/msgid/grase-hotspot/03e7dfaf-ad46-4d5c-
>> a842-033143e6bc81%40grasehotspot.org
>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/03e7dfaf-ad46-4d5c-a842-033143e6bc81%40grasehotspot.org?utm_medium=email&utm_source=footer>
>> .
>>
>
>

Thread