Basic engineers view-only diagnostic GUI

[hamishmb]

Okay, let's stick with the original plan then.

[Penri]

Agreed

[Penri]

Hello Hamish

Used the interface for the first time at WMT today, I like it, it worked nicely. My only gripe is that I can never remember the designations of the various part of the system, I'll have to label them all and start learning what they are!

Good job, thank you.

Penri

[TerryJC]

So how do we get to use it if we are on site? I assume that it's just a web page?

[hamishmb]

Terry, to use it, connect to the guest access point and got to http://192.168.0.25/engineer-gui.

Penri,

I can adjust the labels in the dropdown to include the site names if you like eg "Stage", "Hanham".

[TerryJC]

Terry, to use it, connect to the guest access point and got to http://192.168.0.25/engineer-gui.

If you add engineer-gui to /etc/hosts.dnsmasq (along with nasbox, which is already there), then you should be able to simply type 'engineer-gui' and still get there.

[Penri]

Hamish

If you could add Stage, etc. without loosing the designations, that would be useful for me. I know G1,2 & 3 then I hit a blank, I will learn them in time but if you can, great.

Penri

[hamishmb]

Yep, I can do that for you Penri.

Terry,

Would this be a change on the NAS box itself or on some other system. If on the NAS box I somewhat doubt if it would work because it's so weirdly configured. Also it seems quite fragile so I'm not sure I want to touch it just yet

[TerryJC]

Would this be a change on the NAS box itself or on some other system. If on the NAS box I somewhat doubt if it would work because it's so weirdly configured. Also it seems quite fragile so I'm not sure I want to touch it just yet

Hamish,

I'm sorry. My comment was a bit vague. That file is on the Webserver.

When I set up the Webserver a few years ago, it needed a DHCP Server and a DNS Server as well as nginx to serve the content. Anyone who connects to the Site WiFI is given an IP Address in the range 192.168.0.100 to 250. This applies to staff/volunteers as well as Visitors. If they open a browser and type 'WMT-Guest' they are directed to the WMT content (nodogsplash does this automatically as soon as the user connects on a phone).

When I installed the VPN, I added the file hosts.dnsmasq to contain the IP Addresses of all the devices on the network, including the NAS Box. Here it is:

Code: Select all

# Hosts in the River System network for use by the VPN Server (when installed)
192.168.0.1     WMT-Webserver
192.168.0.2     sumppi
192.168.0.3     lhbuttspi
192.168.0.4     wbuttspi
192.168.0.5     gbuttspi
192.168.0.6     sbuttspi
192.168.0.11    g1gatepi
192.168.0.12    g2gatepi
192.168.0.13    g3gatepi
192.168.0.14    g4gatepi
192.168.0.15    g5gatepi
192.168.0.16    m6gatepi
192.168.0.17    m7gatepi
192.168.0.18    m8gatepi
192.168.0.19    m9gatepi
192.168.0.20    TBD10gatepi
192.168.0.21    TBD11gatepi
192.168.0.22    g6gatepi
192.168.0.9     guipi
192.168.0.25    nasbox
192.168.0.30    VPN-Server

A short time ago I logged into the Webserver over VPN and added:

Code: Select all

192.168.0.25	engineer-gui

to that list.

With the above additions, anyone logging into the WMT Network using the Site WiFi should be able to type 'ssh pi@sumpi' instead of 'ssh [email protected]'. (When I did this, I spent quite a long time getting VPN to work, as you know, and I forgot about this additional feature. In any case, some of the hostnames are just as long winded and complicated as the IP Addresses, so it has limited benefit. This won't work remotely, unless you first log in to a Pi on site.)

Penri,

The next time you are in try connecting to the Engineer GUI by typing 'engineer-gui' into your browser instead of the IP Address. Can you let me know if it works?

BTW. I updated the Pi while I was there.

[Penri]

Hello

Popped in this afternoon but could not get ‘engineer-gui’ to do anything for me, the IP address worked ok. Will give it another go on Tuesday.

Penri