Location: NodeLuckyLabNW
Date and Time: Wednesday, August 10, 2022, 6:30pm-8:00pm
Scribe: You
Roll Call: Them

Agenda

• Pick location for next weekly
• Node notes:

  • NodeAlhambra -- initial gateway plugged in, 4 programmed Meraki MR24's exchanged with the node host, cable runs in progress, outdoor APs on the way.

    • Realtek-based switch, Engenius EWS2910P (v1 and v3) were flashed, one discovered to be new to OpenWrt and some reverse-engineering ensued to support PoE.

  • NodeMississippi:

    • intermittent uptime on ubiquiti bullet-ac (10.11.104.19)
    • bad connectivity to metrix ballroom (10.11.104.2)
    • no connectivity to unifi-ac-mesh on Commons (10.11.104.6) need building access to fix.

    • lost connectivity to moose (at NodeFreshPot)

  • NodeFreshPot -- down since July 30, needs a visit to investigate

  • NodeSuzette -- down since closure of restaurant, need to reach out to see about gear or new tenant

  • NodeKlickitat -- a couple of the ground-level mesh nodes are down, Russell needs to reach out to see about rebooting/repowering

  • NodeC3PO -- since it is shutdown now, we should see about decommissioning the backhaul radio on host's roof, or maybe repurposing it (in which case, a beefier radio is probably warranted, it is memory constrained)?
• Russell spent Monday afternoon refining the MerakiMR24 flashing instructions and also paving over 4 different versions of the Recovery firmware built into (38 of 40) the MR24's in the reserve inventory. There are additional MR24s in the field, which perhaps should have their Recovery firmware updated as well, including:

  • ap1 and ap2 at NodeBrunner;

  • ap1 through ap5 at NodeBuffaloGap;

  • ap1 and ap2 at NodeEcotrust;

  • ap1 through ap3 at NodeGooseHollow;

  • ap1 and ap2 at NodeGriswold;

  • ap1 and ap2 at NodeLuckyLab;

  • ap1 and ap2 at NodeLuckyLabSW;

  • ap1 and ap2 at NodeStreetRoots;

  • ap1 at NodeTibbetts;

  • NodeAnnaBannanas;

  • NodeBergie;

  • NodeBerneis;

  • NodeCommunitecture;

  • NodeEleven;

  • NodeHayduke;

  • NodeLionsEye;

  • NodeLuckyLabNW;

  • NodeLutz;

  • NodeMisdemeanor;

  • NodeMoby;

  • NodeRerun;

  The 5 variants are:
  1. kernel 4.4.21 : Sat Sep 17 19:43:29 2016 -- LEDE (old u-boot-env variables);
  2. kernel 4.9.20 : Tue Apr 04 13:06:14 2017 -- LEDE (old u-boot-env variables);

  3. kernel 4.14.20 : Thu Feb 22 22:40:16 2018 -- OpenWrt (old u-boot-env variables);

  4. kernel 4.19.72 : Sat Sep 14 17:38:48 2019 -- OpenWrt (SSID: OpenWrt currrent u-boot-env variables, includes a firewall which makes it unreachable from ethernet side);

  5. kernel 5.10.134 : Tue Aug 02 08:23:52 2022 -- OpenWrt (SSID: RECOVERY, no firewall, no password)

  Observed 6 variants still in the deployed devices (hash, timestamp of kernel, size of ubi volume, respectively):
  1. 7d41197c ; 20160917-194329 ; 331 LEBs
  2. 94f85921 ; 20160925-073055 ; 331 LEBs
  3. fef78d95 ; 20170404-130614 ; 331 LEBs
  4. eaed259b ; 20180222-224016 ; 331 LEBs
  5. 44f2e744 ; 20180222-224016 ; 331 LEBs
  6. a46e503a ; 20190914-173848 ; 267 LEBs
• Checked in on the 5 remaining Ubiquiti ER-X gateways in the field, and none of them are showing squashfs NAND errors we were seeing previously, so it might be whatever the bug we saw earlier was magically corrected when we weren't looking
• Wiline needs a query about our machine there

• Your Item Here

Notes

• None Yet

[CategoryMeetingNotes]