2020-05-11 - Re: [GRASE-Hotspot] Re: Initial installable Dev packages for V4

Header Data

From: Tim <ti***8@gmail.com>
Message Hash: a9e02c7ac30efffd6ad1d8ecd40c9ca497a66db5d70292a9087cec3b9af97748
Message ID: <CAESLx0KBE8HWX68YC2_7yy19wbDx9HEMR2wZh934VVgnuch-MQ@mail.gmail.com>
Reply To: <f3e64abc-a8a0-ac08-941f-ec3db817da6a@gmail.com>
UTC Datetime: 2020-05-11 14:38:01 UTC
Raw Date: Tue, 12 May 2020 05:38:01 +0800

Raw message 

So far I've only tested it on 18.04 Server, not a desktop environment. I
expect because you've used the XFCE version that it's pulled in
systemd-resolved which is preventing dnsmasq from running.

Currently, you'll need to complete the last steps of accessing the admin
interface from the "WAN" interface. Once you have done this and CoovaChilli
can start with the correct LAN NIC, then you'll be able to access it from
the LAN.

I will attempt to work out steps for the GUI Ubuntu 18.04, it'll have extra
steps to disable systemd-resolved and possibly network manager again.

Due to the huge jump in versions of everything, it was easier to not try
and do upgrades with apt/deb packages and expect the database upgrades to
work (especially as the previous version had 2 databases managed by 2
different packages). Instead, there is a tool provided to take a V3
database dump and load it and convert it to V4.

It does sound like the initial configuration is a bit of an issue, and I
know part of that is currently the LAN interface can't come up until you
configure it correctly. In V3 we tried to guess it, but that was done
poorly and so if you never went into the admin interface and "resaved" the
settings page, it could randomly change at reboot. I've debated putting a
"first run" wizard in to help configure the initial settings. This may help
with getting systems running, but it sounds like getting to the web
interface is a bit of an issue initially? What if the first run wizard was
run through the command line instead?

Regards

Tim

On Thu, 7 May 2020 at 23:42, Charles Chambers <cc***2@gmail.com> wrote:

> Now I can start.  I have time.
>
> I'm confused:
>
> *I've updated the instructions a little after testing from a clean 18.04
> install*
>
> My original  install was 12.04, Ubuntu Server.  No GUI.  I still have it
> as a recovery image.
>
> *1. Clean install Ubuntu 18.04*
>
> I've tried Ubuntu Server 18.04 six times.  The first one vanilla, refusing
> updates (IIRC), the rest in varying forms going forwards and backwards.
> The install is unstable under 18.04 server.  The only package not specified
> that I add is openssh-server, so that I can remote into the box.  I
> generally run the hot spot server *without* a GUI, which is why 18.04
> server.  That's also why the concern over not having my second NIC come
> alive after install was complete (step 5).
>
> The last step was confusing at first - on Ubuntu 18.04 server, there is no
> GUI, so no browser to bring up, and thus no place to supply an address.
>
> As I'm now installling 18.04 (xfce desktop), the "clean install" fresh off
> the media is short 147 updates, of which 102 of them security updates.  As
> a last attempt, I'm not fixing this first, but I would usually.  The Xfce
> install included formatting the installed partitions, so no previous crud
> left behind.
>
> *2. Point to new Grase development apt repo*
>
> *$ echo deb **https://apt.grasehotspot.org/dev
> <https://apt.grasehotspot.org/dev> bionic main | sudo tee
> /etc/apt/sources.list.d/grase.list*
>
> No error messages.
>
> The first install (grase-www-portal) triggers something like 60 packages
> to bring in along with grase-www-portal.  The assumption is that this is
> expected.
>
> The second install brings in another 40 packages.  Again, the assumption
> is that this is expected.
>
> *3. Get the repo key*
>
> *$ sudo wget **https://github.com/GraseHotspot/grase-repo/raw/master/key/grase.hotspot.2020.gpg
> <https://github.com/GraseHotspot/grase-repo/raw/master/key/grase.hotspot.2020.gpg>
> -O /etc/apt/trusted.gpg.d/grase.hotspot.2020.gpg*
>
> No error messages.
>
> *4. Update your apt information*
>
> *$ sudo apt update*
>
> No error messages.
>
>
> *Under xfce build, 147 updates.  See #1, above.  List attached. *
>
> *5. Install the required Grase packages. As part of the install, there are
> a few database questions, just accept the defaults*
>
> *$ sudo apt install grase-www-portal*
>
> List continues.  Xfce build to provide GUI
>
> *$ sudo apt install grase-conf-freeradius grase-conf-dnsmasq coova-chilli*
>
> List continues.  Xfce build to provide GUI
>
> Done and done.  The upgrade routine for Grase with grase-www-portal is
> unexpected, but you do have admins who will want to upgrade.  I'm still
> pre-deployment, so no *real* user accounts.
> *6. You should now have a Grase install accessible. e.g. **http://127.0.0.1/grase/
> <http://127.0.0.1/grase/>*
>
> Installed on Ubuntu 18.04 server, and browsing from a different computer
> on the LAN (browsing to 192.68.0.200/grase), I got to a web page on the
> first build, never after that on subsequent builds.
>
> Xfce build, no network customizing prior to this step.  Browser returns
> "The requested URL is not found on this server" when it's done from
> Firefox/Xfce desktop.
>
>
>
>
>
>
>
>
>
>
>
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/f3e64abc-a8a0-ac08-941f-ec3db817da6a%40gmail.com
> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/f3e64abc-a8a0-ac08-941f-ec3db817da6a%40gmail.com?utm_medium=email&utm_source=footer>
> .
>

Thread