Tag Archives: ROOter

February 2024 Autobuild Statistics

ZBT-Z8102AX is the top of the list this month, but with a caveat – there’s a lot of fixing going on with this router. The manufacturer has released an early version and a late version, with very different bootloaders. The image currently on the site works with the early bootloader. Dairyman has been working with a few folks this month trying to get an image working with the second bootloader, which has a completely different flash layout.

Autobuild report for 2024-02
Compiled Fri 01 Mar 2024 08:00:01 AM UTC
Includes downloads from 2024-02-01 to 2024-02-29

Total router system downloads: 1598 by 845 unique users.

Top performing routers:
  117  ZBT-Z8102AX
   61  Arcadyan-AW1000
   42  ZBT-WG1608-16
   42  Beeline-SmartBox_TurboPlus
   41  x86-64
   33  ZBT-WG1608-32M
   32  Alwaylink-MK01K21
   30  RaspberryPi-4-SD
   29  ZBT-WE826T
   28  ZBT-Z8102AX-V2
   25  ZBT-WG3526
   24  Mikrotik-RBM33G
   22  ZBT-WE2802D
   20  Beeline-SmartBox_TurboModPlus
   18  ZBT-WR8305RT

Downloads by build system:
   78  AB_1800
  382  AB19
  588  AB21
  290  AB22
   64  AB23
   10  AB_BPIR4
   18  ABGL
   20  AB_RPI5
  148  ABSM

Routers with no downloads:
   GliNet_MT6000
   Linksys-EA9500v1
   Mikrotik-RBSXTR
   Mikrotik-RBwAPR-2nD
   Netgear-R6220
   Netgear-R7500-V1
   Netgear-R8000
   SamKnows-WhiteBox-V8
   TP-Link-Archer-WR1045ND
   TP-Link-WDR4300
   TP-Link-WDR4310
   TP-Link-WR703N-16meg
   UniElec-U7621-06

Lowest performing routers with downloads:
    1  Netgear-R6300-V2
    1  NanoPi-NEO-Plus2
    1  MYNET-N600
    1  Mikrotik-RBD52U
    1  Mikrotik-RB922UAGS
    1  Mikrotik-RB912UAG-5HPnD
    1  Mikrotik-RB750GR3
    1  Mikrotik-LHG-HB
    1  Mikrotik-LHG-2nD
    1  Linksys-EA8300
    1  Lenovo-Y1-V1
    1  IRZ-MT00
    1  GL-S1300
    1  Cudy-WR1300
    1  Asus-RT-AC56U

Highest individual downloaders (hashed):
  388  0d58b5d9c89b
   15  df443cf6a0cc
   15  805c760b077d
   14  801a97a16785
    8  76c38d950909
    8  47d593a83839
    8  44559ae5f771
    8  06135a944cba
    7  b13dcfcce625
    7  81feb3df44a9

Downloads by router name:
   10  Alfa-R36A
    3  Alfa-R36M-E4G
    3  Alfa-TUBE-E4G
    3  ALIX-2D13
   32  Alwaylink-MK01K21
    3  APU2C4
   61  Arcadyan-AW1000
    3  Archer-A7-V5
    3  Archer-C20-V1
    5  Archer-C2600
    3  Archer-C2-V1
    2  Archer-C5-V1
   14  Archer-C6Uv1
    7  Archer-C7-V2
    4  Archer-C7-V4
   12  Archer-C7-V5
    9  Asus-RT-AC51U
    1  Asus-RT-AC56U
   15  Asus-RT-AC58U
    4  Asus-RT-AC65P
   11  Asus-RT-AC68U
    3  Asus-RT-AC85P
    6  Asus-RT-AC87U
   10  Asus-RT-AX53U
    4  Asus-RT-N14U
    7  Asus-RT-N16
    9  Asus-RT-N56U
   13  Asus-RT-N66U
   10  Banana-Pi4
   11  BananaPi-BPi-R3
    6  Beeline-SmartBox_Pro
   20  Beeline-SmartBox_TurboModPlus
   42  Beeline-SmartBox_TurboPlus
    3  BT-HomeHub-5
    3  CheckPoint-L-50
    2  Comfast-CF-E3
    3  Comfast-CF-E5
    2  Compex-WPJ428
    1  Cudy-WR1300
    6  DIR505A1
    3  D-Link-DGL-5500-A1
    3  D-Link-DIR-825-C1
    3  D-Link-DIR-835-A1
    2  Dlink-DIR853-R1
    3  D-Link-DIR-860L-B1
    2  D-Link-DIR-882-A1
    3  D-Link-DIR-882-R1
    6  DualQ-H721-1907
    3  DualQ-H721-2102
    3  DualQ-H721-2203
    2  DualQ-H721AX
    4  Dynalink-DL-WRX36
    3  GL-AP1300
    6  GL-AR150
    6  GL-AR300M-16
    2  GL-AR300M-Lite
    8  GL-AR300M-nand
    2  GL-AR750
    3  GL-B1300
    9  GL-E750
    7  GLi-AR750S
    6  GL-iNet-AX1800
   11  GL-iNet-AXT1800
    3  Gl.iNet-GL6416
    8  Gl.iNet-MT1300
   12  GliNet_MT3000
    7  Gl.iNet-MV1000
    6  GliNet_X3000
    3  GL-MIFI
    4  GL-MT300A
    3  GL-MT300N-V1
   12  GL-MT300N-V2
    4  Globalscale-MOCHAbin
    1  GL-S1300
    4  GL-X1200
    8  GL-X750
    2  GL-XE300
   13  HiLink-HLK-7621a
    5  HiWiFi-HC5962
    6  Huasifei-WS1208V1
    4  Huasifei-WS1208v2-32
    4  Huasifei-WS1208V2
    3  Huasifei-WS1218
    6  Huasifei-WS1688AX-16
    4  Huasifei-WS1688AX-32
   13  Huasifei-WS1698AX
    3  Huasifei-WS7915AX
    4  Huastlink-HC851-HC841
    3  Huastlink-HC952
    8  Huawei-HG553
    7  Huawei-HG556a-A
    7  Huawei-HG556a-B
   11  Huawei-HG556a-C
    1  IRZ-MT00
    2  Lenovo-Y1S-V1
    1  Lenovo-Y1-V1
    4  Linksys-E4200-V2
    7  Linksys-E8450-UBI
    2  Linksys-EA3500
    2  Linksys-EA4500-V1
    3  Linksys-EA6350v3
    4  Linksys-EA7300
    3  Linksys-EA7500v1
    4  Linksys-EA7500v2
    3  Linksys-EA8100v1
    1  Linksys-EA8300
    2  Linksys-EA8500
    5  Linksys-MR8300
    4  Linksys-WRT1200AC
    8  Linksys-WRT1900ACS
    4  Linksys-WRT1900AC-V1
    4  Linksys-WRT1900AC-V2
   14  Linksys-WRT3200ACM
    9  Linksys-WRT32x
   17  M01K21
    3  Mediatek-MT7628-EVB
    3  Mercury-MW4530R
    1  Mikrotik-LHG-2nD
    1  Mikrotik-LHG-HB
    3  Mikrotik-RB433AH
    1  Mikrotik-RB750GR3
    2  Mikrotik-RB760iGS
    2  Mikrotik-RB912UAG-2HPnD
    1  Mikrotik-RB912UAG-5HPnD
    1  Mikrotik-RB922UAGS
    2  Mikrotik-RB951Ui-2nD
    1  Mikrotik-RBD52U
    8  Mikrotik-RBM11G
   24  Mikrotik-RBM33G
    3  Mofi-4500
    1  MYNET-N600
    4  MYNET-N750
    1  NanoPi-NEO-Plus2
    2  NanoPi-R2S
    5  NanoPi-R4S
    1  Netgear-R6300-V2
    1  Netgear-R7000
    1  Netgear-R7500-V2
    3  Netgear-R7800
    2  Netgear-WNDR3700-V1
   10  Netgear-WNDR3700-V2
    1  Netgear-WNDR3700-V4
    2  Netgear-WNDR3800
    5  Netgear-WNDR4300v1
    9  Newifi-D2
    3  Nexx-WT3020-16
    5  Nexx-WT3020-8
    3  O2-Box-6431
    6  OrangePi-PC
    3  OrangePi-Plus
    6  OrangePi-Zero-Plus
    5  P2W-R619AC
    9  RaspberryPi-1
   14  RaspberryPi-2
    8  RaspberryPi-3-SD
    1  RaspberryPi-3-USB
   30  RaspberryPi-4-SD
    9  RaspberryPi-4-USB
   15  RaspberryPi-5-SD
    5  RaspberryPi-5-USB
    6  RaspberryPi-CM4-SD
    1  RaspberryPi-CM4-USB
    1  Sanlinking-D240
    2  Seagate-Dockstar
   18  SmartBox_Giga
   13  SmartBox_ModGiga
    1  TP-Link-Archer-C59v1
    3  TP-Link-Archer-C59v2
    3  TP-Link-Archer-C6-V2
    4  TP-Link-Archer-C7v1
   12  TP-Link-MR3020v3
   12  TP-Link-MR3420v5
    4  TP-Link-WDR3500
    3  TP-Link-WDR3600
    1  TP-Link-WDR4900
    2  TP-Link-WR1043NDv2
    3  TP-Link-WR1043NDv3
    1  TP-Link-WR1043ND-V4
    1  TP-Link-WR1043N-V5
    4  TP-Link-WR842-V3
    1  TP-Link-WR902ACv1
    5  TP-Link-WR902ACv3
    6  TP-Link-WR942N
    3  Turris-Omnia-2102
    3  Turris-Omnia-2305
    1  UniElec-U7621-01
    1  UniElec-U7628-01
    3  WiFiX-NEXQ6GO
   41  x86-64
    4  x86-Generic
   13  x86-UEFI-64
   12  x86-UEFI-Generic
   10  Xiaomi-Mifi3G
    7  Xiaomi-Mifi3Pro
   11  Xiaomi-Mifi-Mini
    1  YouHua-WR1200JS
    6  YOUKU-YK1
   12  ZBT-WE1026-5G
   10  ZBT-WE1326
   22  ZBT-WE2802D
   13  ZBT-WE826-Q
   29  ZBT-WE826T
   11  ZBT-WE826-T-32meg
   10  ZBT-WE826WD
    8  ZBT-WG1602-16
    7  ZBT-WG1602-32
    3  ZBT-WG1602-32M-2102
   42  ZBT-WG1608-16
   33  ZBT-WG1608-32M
    4  ZBT-WG209
    3  ZBT-WG259
   25  ZBT-WG3526
    3  ZBT-WG827
   18  ZBT-WR8305RT
    9  ZBT-Z2101AX
    5  ZBT-Z2105AX
  117  ZBT-Z8102AX
   28  ZBT-Z8102AX-V2
    3  ZyXEL-Keenetic-Extra-II
   10  ZyXEL-Keenetic-Omni
    1  ZyXEL-NBG6817
    3  ZyZEL-NR7101

January 2024 Autobuild Statistics

The autobuild report is ready for last month. The new AW1000 has made it up to most popular router of the month already! We’re not seeing a lot of issue reports on the forum yet either, so with that many downloads, I have to think it’s working pretty well for folks so far.

Autobuild report for 2024-01
Compiled Fri 02 Feb 2024 01:07:32 PM UTC
Includes downloads from 2024-01-01 to 2024-01-31

Total router system downloads: 2315 by 1292 unique users.

Top performing routers:
  206  Arcadyan-AW1000
  127  ZBT-Z8102AX
   80  ZBT-WG3526
   71  x86-64
   57  Linksys-WRT1900ACS
   41  Alwaylink-MK01K21
   37  ZBT-WG1608-32M
   36  RaspberryPi-4-SD
   35  ZBT-WG1608-16
   35  x86-UEFI-64
   35  Archer-C7-V4
   34  Archer-C6Uv1
   32  Archer-C5-V1
   31  x86-UEFI-Generic
   30  Mikrotik-RB922UAGS

Downloads by build system:
  242  AB_1800
  452  AB19
  951  AB21
  398  AB22
   86  AB23
    4  AB_BPIR4
    4  ABGL
   24  AB_RPI5
  154  ABSM

Routers with no downloads:
   ALIX-2D13
   Archer-C2600
   Asus-RT-AC56U
   Asus-RT-N56U
   BT-HomeHub-5
   CheckPoint-L-50
   Comfast-CF-E5
   Compex-WPJ428
   D-Link-DIR-825-C1
   D-Link-DIR-860L-B1
   D-Link-DIR-882-R1
   DualQ-H721-1907
   GL-AP1300
   GL-AR300M-Lite
   GL-AR750
   Gl.iNet-GL6416
   Gl.iNet-MV1000
   GL-MT300A
   Globalscale-MOCHAbin
   GL-S1300
   GL-X1200
   Huasifei-WS1218
   IRZ-MT00
   Linksys-E4200-V2
   Linksys-EA3500
   Linksys-EA7500v1
   Linksys-EA7500v2
   Linksys-EA9500v1
   Linksys-MR8300
   Mercury-MW4530R
   Mikrotik-RB433AH
   Mikrotik-RB750GR3
   Mikrotik-RB912UAG-5HPnD
   Mikrotik-RB951Ui-2nD
   Mikrotik-RBwAPR-2nD
   Mofi-4500
   MYNET-N600
   MYNET-N750
   NanoPi-NEO-Plus2
   Netgear-R7500-V2
   Netgear-WNDR3700-V2
   Netgear-WNDR3700-V4
   Netgear-WNDR3800
   RaspberryPi-CM4-USB
   Sanlinking-D240
   Seagate-Dockstar
   TP-Link-Archer-C59v1
   TP-Link-Archer-C6-V2
   TP-Link-WDR4900
   TP-Link-WR1043ND-V4
   TP-Link-WR1043N-V5
   TP-Link-WR703N-16meg
   UniElec-U7621-06
   ZBT-WE826WD

Lowest performing routers with downloads:
    1  Linksys-EA8500
    1  Linksys-EA8300
    1  Linksys-EA8100v1
    1  Lenovo-Y1-V1
    1  Huastlink-HC952
    1  Huasifei-WS1688AX-16
    1  GliNet_X3000
    1  GLi-AR750S
    1  GL-AR300M-nand
    1  Dynalink-DL-WRX36
    1  D-Link-DIR-835-A1
    1  D-Link-DGL-5500-A1
    1  Asus-RT-AC85P
    1  Asus-RT-AC65P
    1  APU2C4

Highest individual downloaders (hashed):
   50  90b824fe9caf
   49  a72c06701e16
   49  7664df2981e9
   30  916219eddd8c
   29  7f37a96a8e33
   29  5212e2aba7c6
   28  162e4e63d161
   27  54543106c83d
   24  c0b6d9ef22da
   24  b48bd016f375

Downloads by router name:
    7  Alfa-R36A
    3  Alfa-R36M-E4G
    3  Alfa-TUBE-E4G
   41  Alwaylink-MK01K21
    1  APU2C4
  206  Arcadyan-AW1000
   25  Archer-A7-V5
   25  Archer-C20-V1
    2  Archer-C2-V1
   32  Archer-C5-V1
   34  Archer-C6Uv1
    6  Archer-C7-V2
   35  Archer-C7-V4
    9  Archer-C7-V5
    9  Asus-RT-AC51U
   10  Asus-RT-AC58U
    1  Asus-RT-AC65P
    4  Asus-RT-AC68U
    1  Asus-RT-AC85P
   15  Asus-RT-AC87U
   23  Asus-RT-AX53U
    3  Asus-RT-N14U
    2  Asus-RT-N16
    2  Asus-RT-N66U
    4  Banana-Pi4
    3  BananaPi-BPi-R3
    5  Beeline-SmartBox_Pro
   14  Beeline-SmartBox_TurboModPlus
   30  Beeline-SmartBox_TurboPlus
   23  Comfast-CF-E3
    2  Cudy-WR1300
    3  DIR505A1
    1  D-Link-DGL-5500-A1
    1  D-Link-DIR-835-A1
    3  Dlink-DIR853-R1
    3  D-Link-DIR-882-A1
    3  DualQ-H721-2102
   22  DualQ-H721
    5  DualQ-H721-2203
   13  DualQ-H721AX
    1  Dynalink-DL-WRX36
    5  GL-AR150
    5  GL-AR300M-16
    1  GL-AR300M-nand
    2  GL-B1300
    8  GL-E750
    1  GLi-AR750S
   19  GL-iNet-AX1800
   20  GL-iNet-AXT1800
   10  Gl.iNet-MT1300
   21  GliNet_MT3000
    1  GliNet_X3000
    3  GL-MIFI
   17  GL-MT300N-V1
   10  GL-MT300N-V2
    3  GL-X750
    2  GL-XE300
    7  HiLink-HLK-7621a
   26  HiWiFi-HC5962
    4  Huasifei-WS1208V1
   19  Huasifei-WS1208V2
    4  Huasifei-WS1208v2-32
    1  Huasifei-WS1688AX-16
    2  Huasifei-WS1688AX-32
    6  Huasifei-WS1698AX
    5  Huasifei-WS7915AX
   18  Huastlink-HC851-HC841
    1  Huastlink-HC952
    6  Huawei-HG553
    2  Huawei-HG556a-A
    2  Huawei-HG556a-B
    5  Huawei-HG556a-C
   18  Lenovo-Y1S-V1
    1  Lenovo-Y1-V1
    2  Linksys-E8450-UBI
    2  Linksys-EA4500-V1
    2  Linksys-EA6350v3
   15  Linksys-EA7300
    1  Linksys-EA8100v1
    1  Linksys-EA8300
    1  Linksys-EA8500
    7  Linksys-WRT1200AC
   57  Linksys-WRT1900ACS
   24  Linksys-WRT1900AC-V1
    1  Linksys-WRT1900AC-V2
   10  Linksys-WRT3200ACM
    3  Linksys-WRT32x
   23  M01K21
    2  Mediatek-MT7628-EVB
    1  Mikrotik-LHG-2nD
   28  Mikrotik-LHG-HB
   16  Mikrotik-RB760iGS
   17  Mikrotik-RB912UAG-2HPnD
   30  Mikrotik-RB922UAGS
    4  Mikrotik-RBD52U
    6  Mikrotik-RBM11G
    7  Mikrotik-RBM33G
    1  Mikrotik-RBSXTR
    4  NanoPi-R2S
    2  NanoPi-R4S
    2  Netgear-R6220
   16  Netgear-R6300-V2
    1  Netgear-R7000
   20  Netgear-R7500-V1
    1  Netgear-R7800
    2  Netgear-R8000
    1  Netgear-WNDR3700-V1
    2  Netgear-WNDR4300v1
   10  Newifi-D2
   22  Nexx-WT3020-16
    3  Nexx-WT3020-8
    3  O2-Box-6431
    3  OrangePi-PC
    3  OrangePi-Plus
   18  OrangePi-Zero-Plus
    2  P2W-R619AC
    2  RaspberryPi-1
    9  RaspberryPi-2
   26  RaspberryPi-3-SD
    2  RaspberryPi-3-USB
   36  RaspberryPi-4-SD
    5  RaspberryPi-4-USB
   19  RaspberryPi-5-SD
    5  RaspberryPi-5-USB
    1  RaspberryPi-CM4-SD
   17  SamKnows-WhiteBox-V8
   21  SmartBox_Giga
   22  SmartBox_ModGiga
   27  TP-Link-Archer-C59v2
   13  TP-Link-Archer-C7v1
    2  TP-Link-Archer-WR1045ND
   19  TP-Link-MR3020v3
   21  TP-Link-MR3420v5
    2  TP-Link-WDR3500
    5  TP-Link-WDR3600
    3  TP-Link-WDR4300
    1  TP-Link-WDR4310
    6  TP-Link-WR1043NDv2
    1  TP-Link-WR1043NDv3
   24  TP-Link-WR842-V3
   17  TP-Link-WR902ACv1
   21  TP-Link-WR902ACv3
   11  TP-Link-WR942N
    1  Turris-Omnia-2102
   17  Turris-Omnia-2305
   21  UniElec-U7621-01
    1  UniElec-U7628-01
   18  WiFiX-NEXQ6GO
   71  x86-64
   10  x86-Generic
   35  x86-UEFI-64
   31  x86-UEFI-Generic
   23  Xiaomi-Mifi3G
    6  Xiaomi-Mifi3Pro
   12  Xiaomi-Mifi-Mini
   26  YouHua-WR1200JS
    2  YOUKU-YK1
   18  ZBT-WE1026-5G
   12  ZBT-WE1326
   22  ZBT-WE2802D
   25  ZBT-WE826-Q
   27  ZBT-WE826T
    5  ZBT-WE826-T-32meg
   18  ZBT-WG1602-16
    2  ZBT-WG1602-32
    1  ZBT-WG1602-32M-2102
   35  ZBT-WG1608-16
   37  ZBT-WG1608-32M
    7  ZBT-WG209
    1  ZBT-WG259
   80  ZBT-WG3526
    1  ZBT-WG827
   12  ZBT-WR8305RT
    3  ZBT-Z2101AX
    2  ZBT-Z2105AX
  127  ZBT-Z8102AX
   11  ZBT-Z8102AX-V2
    4  ZyXEL-Keenetic-Extra-II
    3  ZyXEL-Keenetic-Omni
   15  ZyXEL-NBG6817
    2  ZyZEL-NR7101

December 2023 Autobuild statistics

And this is the new feature I just mentioned in the update. I’ve wanted to set up some log analysis for a year to see which routers were popular and how many images were being downloaded, but didn’t have the time. This weekend was rainy and I had a some mental energy and time, so I got it done. This analysis is automated, so I plan to post these up monthly, though there might not always be time to do it on the first of the month.

Some words on methodology – these are all based on my apache logs. This first report only covers from December 9 to the end of the month, because those were all I still had in my log rotation. My scripts are now grabbing the logs daily at the end of the day, and processing that one day immediately. Identifying info is not getting kept long term, that was a priorty for me – as soon as I process the raw log, I’m saving the first digits of a hash of the downloading IP address only. That’s enough to tell different downloaders apart, but can’t be reversed to an actual single address even by brute force methods thanks to only keeping part of the hash.

A few quirks this month. For one, you’ll see a couple of images noted under “unknown” build systems, that’s because one of the new systems wasn’t spitting out its proper “-ABxx” file tag on the initial test run. You’ll also see that there are only a handful of routers listed with zero downloads, but some of those are because the script also checks against routers available when the script is run (since routers that aren’t downloaded don’t show up in the log either, and I can’t check to see what files were available a month ago). So if a router is released on 1/1 and you run the report for December, that router will show up on this list as a December router with no downloads. Not a big deal, but it’s a thing.

The other one is that there are more routers with no real downloads than indicated. A handful of folks do full scrapes of the site every month (which is fine by me), so you see “false” downloads associated with those scrapes. I saw three full scrapes in the logs in this report period, and one partial. It’s easy to get an idea by looking at the list of top user hashes, when you see someone has 400+ downloads that’s an obvious candidate. So, a router that shows only 3 downloads has good odds of not being used by anyone that month.

Without further ado,

The results:

Autobuild report for 2023-12
Compiled Mon 08 Jan 2024 03:51:02 PM UTC
Includes downloads from 2023-12-09 to 2023-12-31

Total router system downloads: 2673 by 576 unique users.

Top performing routers:
   65  Mikrotik-RBM33G
   61  ZBT-WG1608
   56  ZBT-Z8102AX
   55  Huasifei-WS1208
   53  DualQ-H721
   44  ZBT-WG1602
   37  x86-64
   33  Alwaylink-MK01K21
   32  Beeline-SmartBox_TurboPlus
   30  TP-Link-MR3020v3
   29  Huasifei-WS1208V2
   28  ZBT-WG1608-32M
   28  RaspberryPi-4-SD
   27  Arcadyan-AW1000
   26  ZBT-WG1608-16

Downloads by build system:
    5  AB18
    3  AB_1800
  655  AB19
 1321  AB21
  488  AB22
  106  AB23
   34  ABGL
   57  ABSM
    4  unknown

Routers with no downloads:
   Banana-Pi4
   GL-iNet-AX1800
   GL-iNet-AXT1800
   GliNet_MT3000
   RaspberryPi-5-SD
   RaspberryPi-5-USB

Lowest performing routers with downloads:
    5  Huasifei-WS1698AX
    5  DualQ-H721AX
    5  Asus-RT-AC56U
    4  Netgear-R8000
    4  Linksys-EA9500v1
    4  Huastlink-HC841
    4  GliNet_X3000
    3  WiFiX-NEXQ6GO
    3  TP-Link-WR902ACv1
    3  TP-Link-Archer-C6-V2
    3  Mikrotik-LHG-HB
    3  Mikrotik-LHG-2nD
    3  Linksys-EA8300
    3  Huasifei-WS1208V2-32
    3  Dlink-DIR-853-R1

Highest individual downloaders (hashed):
  493  09a87510be6e
  488  6a199cc49538
  484  bb46aef0d4b2
  377  0d58b5d9c89b
   16  151a3d90824e
   12  a6396bc71c58
   11  4b4e08145894
   10  db803b2880f2
    8  a9f7c6baf2b0
    8  44559ae5f771

Downloads by router name:
   11  Alfa-R36A
    8  Alfa-R36M-E4G
    8  Alfa-TUBE-E4G
    8  ALIX-2D13
   33  Alwaylink-MK01K21
   10  APU2C4
   27  Arcadyan-AW1000
    9  Archer-A7-V5
    8  Archer-C20-V1
    9  Archer-C2600
    8  Archer-C2-V1
    8  Archer-C5-V1
   17  Archer-C6Uv1
   13  Archer-C7-V2
    9  Archer-C7-V4
   18  Archer-C7-V5
   10  Asus-RT-AC51U
    5  Asus-RT-AC56U
   13  Asus-RT-AC58U
    8  Asus-RT-AC65P
   16  Asus-RT-AC68U
    8  Asus-RT-AC85P
   10  Asus-RT-AC87U
   10  Asus-RT-AX53U
    8  Asus-RT-N14U
   10  Asus-RT-N16
    9  Asus-RT-N56U
   13  Asus-RT-N66U
   12  BananaPi-BPi-R3
   16  Beeline-SmartBox_Pro
   16  Beeline-SmartBox_TurboModPlus
   32  Beeline-SmartBox_TurboPlus
    8  BT-HomeHub-5
    8  CheckPoint-L-50
   10  Comfast-CF-E3
   11  Comfast-CF-E5
    8  Compex-WPJ428
    9  Cudy-WR1300
    9  DIR505A1
    7  D-Link-DGL-5500-A1
    8  D-Link-DIR-825-C1
    7  D-Link-DIR-835-A1
   11  Dlink-DIR853-R1
    3  Dlink-DIR-853-R1
    7  D-Link-DIR-860L-B1
   10  D-Link-DIR-882-A1
    8  D-Link-DIR-882-R1
   12  DualQ-H721-1907
   12  DualQ-H721-2102
   11  DualQ-H721-2203
   53  DualQ-H721
    5  DualQ-H721AX
    7  Dynalink-DL-WRX36
    7  GL-AP1300
    7  GL-AR150
    7  GL-AR300M-16
    7  GL-AR300M-Lite
    7  GL-AR300M-nand
   10  GL-AR750
    8  GL-B1300
   17  GL-E750
    8  GLi-AR750S
    8  Gl.iNet-GL6416
   19  Gl.iNet-MT1300
   15  Gl.iNet-MV1000
    4  GliNet_X3000
    9  GL-MIFI
    8  GL-MT300A
    8  GL-MT300N-V1
   20  GL-MT300N-V2
    7  Globalscale-MOCHAbin
   12  GL-S1300
    8  GL-X1200
   22  GL-X750
    9  GL-XE300
   18  HiLink-HLK-7621a
    8  HiWiFi-HC5962
   55  Huasifei-WS1208
   12  Huasifei-WS1208V1
   29  Huasifei-WS1208V2
    3  Huasifei-WS1208V2-32
    8  Huasifei-WS1208v2-32
    6  Huasifei-WS1218
    7  Huasifei-WS1688AX-16
    8  Huasifei-WS1688AX-32
    5  Huasifei-WS1698AX
   10  Huasifei-WS7915AX
    4  Huastlink-HC841
    9  Huastlink-HC851-HC841
    7  Huastlink-HC952
   17  Huawei-HG553
    8  Huawei-HG556a-A
   11  Huawei-HG556a-B
    7  Huawei-HG556a-C
    7  IRZ-MT00
    8  Lenovo-Y1S-V1
    9  Lenovo-Y1-V1
    7  Linksys-E4200-V2
   10  Linksys-E8450
    7  Linksys-E8450-UBI
    9  Linksys-EA3500
    9  Linksys-EA4500-V1
    8  Linksys-EA6350v3
    8  Linksys-EA7300
    7  Linksys-EA7500v1
    8  Linksys-EA7500v2
   10  Linksys-EA8100v1
    3  Linksys-EA8300
    7  Linksys-EA8500
    4  Linksys-EA9500v1
    9  Linksys-MR8300
   13  Linksys-WRT1200AC
   17  Linksys-WRT1900ACS
   19  Linksys-WRT1900AC-V1
   16  Linksys-WRT1900AC-V2
   17  Linksys-WRT3200ACM
   16  Linksys-WRT32x
   18  M01K21
    6  Mediatek-MT7628-EVB
    7  Mercury-MW4530R
    3  Mikrotik-LHG-2nD
    3  Mikrotik-LHG-HB
    6  Mikrotik-RB433AH
    7  Mikrotik-RB750GR3
    8  Mikrotik-RB760iGS
    7  Mikrotik-RB912UAG-2HPnD
    9  Mikrotik-RB912UAG-5HPnD
    7  Mikrotik-RB922UAGS
    6  Mikrotik-RB951Ui-2nD
    8  Mikrotik-RBD52U
   15  Mikrotik-RBM11G
   65  Mikrotik-RBM33G
    9  Mikrotik-RBSXTR
    9  Mikrotik-RBwAPR-2nD
   10  Mofi-4500
    8  MYNET-N600
    9  MYNET-N750
    8  NanoPi-NEO-Plus2
    9  NanoPi-R2S
   14  NanoPi-R4S
    8  Netgear-R6220
    7  Netgear-R6300-V2
   10  Netgear-R7000
    8  Netgear-R7500-V1
    8  Netgear-R7500-V2
   10  Netgear-R7800
    4  Netgear-R8000
    9  Netgear-WNDR3700-V1
    7  Netgear-WNDR3700-V2
    7  Netgear-WNDR3700-V4
    7  Netgear-WNDR3800
   18  Netgear-WNDR4300v1
   19  Newifi-D2
    8  Nexx-WT3020-16
    8  Nexx-WT3020-8
    7  O2-Box-6431
    9  OrangePi-PC
   10  OrangePi-Plus
    8  OrangePi-Zero-Plus
    8  P2W-R619AC
   22  RaspberryPi-1
   17  RaspberryPi-2
   21  RaspberryPi-3-SD
   16  RaspberryPi-3-USB
   28  RaspberryPi-4-SD
   23  RaspberryPi-4-USB
   22  RaspberryPi-CM4-SD
   17  RaspberryPi-CM4-USB
    9  SamKnows-WhiteBox-V8
    8  Sanlinking-D240
    7  Seagate-Dockstar
   23  SmartBox_Giga
   20  SmartBox_ModGiga
    8  TP-Link-Archer-C59v1
    7  TP-Link-Archer-C59v2
    3  TP-Link-Archer-C6-V2
    7  TP-Link-Archer-C7v1
    5  TP-Link-Archer-WR1045ND
   30  TP-Link-MR3020v3
   14  TP-Link-MR3420v5
   10  TP-Link-WDR3500
    9  TP-Link-WDR3600
    8  TP-Link-WDR4300
    8  TP-Link-WDR4310
    7  TP-Link-WDR4900
   10  TP-Link-WR1043NDv2
    8  TP-Link-WR1043NDv3
   10  TP-Link-WR1043ND-V4
    8  TP-Link-WR1043N-V5
    5  TP-Link-WR703N-16meg
   10  TP-Link-WR842-V3
    3  TP-Link-WR902ACv1
    9  TP-Link-WR902ACv3
   14  TP-Link-WR942N
   20  Turris-Omnia
    7  Turris-Omnia-2102
    7  Turris-Omnia-2305
    9  UniElec-U7621-01
    7  UniElec-U7621-06
    7  UniElec-U7628-01
    3  WiFiX-NEXQ6GO
   21  WS1688AX
   11  WS1688AX-32
   37  x86-64
   22  x86-Generic
   14  x86-UEFI-64
   21  x86-UEFI-Generic
   13  Xiaomi-Mifi3G
   10  Xiaomi-Mifi3Pro
   20  Xiaomi-Mifi-Mini
    9  YouHua-WR1200JS
   16  YOUKU-YK1
   13  Z2101AX
   10  ZBT-WE1026-5G
   18  ZBT-WE1326
    8  ZBT-WE2802D
   22  ZBT-WE826-Q
   23  ZBT-WE826T
   12  ZBT-WE826-T-32meg
   15  ZBT-WE826WD
   21  ZBT-WG1602-16
   19  ZBT-WG1602-32
   11  ZBT-WG1602-32M
    8  ZBT-WG1602-32M-2102
   44  ZBT-WG1602
   26  ZBT-WG1608-16
   28  ZBT-WG1608-32M
   61  ZBT-WG1608
    9  ZBT-WG209
    8  ZBT-WG259
   23  ZBT-WG3526
    8  ZBT-WG827
   11  ZBT-WR8305RT
   10  ZBT-Z2101AX
   13  ZBT-Z2105AX
   56  ZBT-Z8102AX
   12  ZyXEL-Keenetic-Extra-II
    7  ZyXEL-Keenetic-Omni
    7  ZyXEL-NBG6817
   10  ZyZEL-NR7101

January 2024 ROOter updates

Only a handful of news on my end right now, thanks to busy jobs on my part taking away from router fun. Here are the updates on the parts that I’m involved with:

New ROOter build systems

Dairyman has released four new build systems since my September update. All four are “special purpose” systems meant to cover a handful of routers. They are:

  • SourceMaster (link) to cover MT3000, WS1698, X3000, and Z8102. This is a fork off of the OpenWRT master as of roughly 27 Nov 2023.
  • SourceBPIR4 (link) to cover BPI4, the Banana Pi R4. Currently a single image system.
  • SourceRPI5 (link) to cover RASPPI5 and RASPPI5USB, which should be the Raspberry Pi 5 board with either the usual SD card or with USB mounted root file systems.
  • Source1800 (link) to cover AW1000, AX1800, and AXT1800. These are the Arcadyan AW1000 and two GL-iNet variants, all with ipq chipsets.

None of these are currently expected to become major build systems, but they will be used where necessary to support new systems not yet covered by one of our main systems. I’m still hearing 21.02 is likely to stay our primary system for a while, as 22.03 and 23.05 are producing much larger images that aren’t going to work on a lot of routers we currently support. Kernel growth has been a big issue in particular for several years now.

Build machine upgrades

The autobuild machine has also gotten an upgrade around New Years. With the current number of router images, the main system SSD was staying around 80-90% full. The build machine now has a second SSD of the same size, so we’re set for quite a bit of future growth.

This laptop has been running the autobuild systems for almost two years now. Not bad for a total investment of roughly $250 US – all this is done off of a salvaged Dell e6410 laptop with a 2 core (4 virtual) i7 chip and 8GB of RAM, with two 1TB SSD’s. It has cranked out roughly 250 images per week in recent builds, usually in 55h or less. Never underestimate the value of ancient hardware to do real work, as these laptops were released in 2010. With weekly builds only taking roughly 1/3 of the laptop’s possible duty cycle (in hours of the week), I expect this little guy should be up for the task for a lot longer barring catastropic failure.

One point of interest is that the CPU load is shown on the build system status page here the same as it is on a ROOter status page (which is the number given by the uptime command). In the first part of the build, it’s not unusual to see utilizations hovering in the upper 20’s. Since this is a two core machine, with hyperthreading, it can handle a load of roughly 1.4 per core depending on the type of load, so for anything over about 2.8, the CPU is 100% utilized. Something to remember when people tell you to tune your builds so that your CPU load stays under your core count – that’s absolute BS. For best builds, you want your load ABOVE your core count. The lower recommendations are to make sure your system stays responsive, but it’s much, much better to handle that using the nice command when you start your build. Despite my CPU being overloaded by an order of magnitude, the machine is still perfectly responsive, and the only way to tell how hard it’s working is by hearing the fan spun up or seeing that load number.

Docker Autobuild Image updates

The base image for the autobuild containers has been updated to Debian 11.8 from 11.7. This is because one of the new build systems needed a pair of new build tools added. This can be done directly within the container for testing, but really any change in the toolchain is work updating the base image instead. This keeps the resulting images a lot more consistent.

The new base image has been applied to all 9 build systems (which took half an evening), tested, gone through a week of full builds, and all of the build system changes have been pushed to github with the new images already pushed to Docker Hub.

Bonus: there’s one more feature announcement coming (which the folks on the forum today will have already seen), but it warrants its own post.

September 2023 ROOter updates

I’ve had a few chances over the last few weeks to make minor updates to the autobuild systems. Nothing major. This month’s news:

  • The autobuild status system has been reconfigured to update every minute, with an approximately one minute lag.
  • The status has also been added to a new Autobuilds headline page, easily accessible from the top menu. This is probably the quickest way to see the current system status. It doesn’t auto update, though, you’ll have to refresh occasionally.
  • A while back we were able to finish uploading all of the old autobuild images to carp4’s Autobuild archive space. Everything should be there, from just after the first runs, sorted by router name. You may find a few routers that are split into several folders due to name changes over time, but everything seems to be where it belongs. This archive also updates with new images within a day or so of them being built.
  • The old 18.06.7 system was retired about a week ago. For at least a year or more it had only been building the WR703N, which barely fit an image with the older kernel. New images no longer fit, so this one is finally wound down.

I have a few more tweaks on my wish list, but everything gets fit between the two real jobs, both of which have been hopping this year. Maybe more time will appear as things go on.

ROOter Autobuilds Archive

This has already been linked from the forum and the autobuilds page, but still great news. We only have space on the server to host the most recent two images for each router. However, user carp4 has donated a significant amount of space on a Google Drive to host all of the older images. Without further ado:

ROOter Autobuild Archive

It will take two to three months to upload all of the older images – there are almost half of a terabyte worth already. They’re all on a local drive now, so will trickle online during off-peak hours overnight. I rough estimate would be end of June, 2023 to have them all online, if all goes well.

Quick and Dirty Live View of rsyslog Output

I mentioned in a post yesterday that I was watching the syslog of my router to see when it sent a boot image over tftp. However, OpenWRT does not have a “live updating” syslog view – so how was I doing that, just clicking refresh over and over with my third hand, while holding down a reset button with the other two? No, there’s a really easy way to do this with a stupidly simple bash script.

My routers use remote logging to an internal rsyslog server on my LAN, and you’ll see my script is set up to support that. However, this is very easy to modify to support OpenWRT’s default logging, as well.

Without further ado, here’s the script, which lives in my log folder:

#!/bin/sh

# Live log display

while true; do
        tail -n 52 $1
        sleep 5
done

My various consoles I log into this from have anywhere from a 40 to 50 line display set up, hence the “52” – it’s reading and displaying the last 52 lines of the log every five seconds. If you always use shorter consoles, you can easily trim this down.

By passing the name of the script you want to read, this script has also been made “universal” in that it can be used to monitor any log on your machine. I also use it on a couple of my other servers, with no modifications. If you want to monitor “hexenbiest.log” you simply cd into the appropriate log folder, and run:

./loglive hexenbiest.log

Stock OpenWRT doesn’t write the log to a real file, it uses a ring buffer in memory that may be accessed using the command logread. To modify this script to run on a stock OpenWRT router, place it in the home folder (/root/) instead, and modify it to read accordingly:

#!/bin/sh

# Live log display

while true; do
        logread | tail -n 52
        sleep 5
done

This way, instead of reading the last 52 lines of a file every five seconds, it’s reading the last 52 lines of the logread output instead.

You might think it would make sense to clear the terminal before each output, but I didn’t personally find that helpful. In fact, it resulted in a visible flicker every time the log updated. Helpful if you need to know each time it reads, but I didn’t find that useful myself.

Using dnsmasq under OpenWRT as a TFTP boot server

Update (2022-03-13): this past year, Mikrotik did something that broke their ability to netboot over DHCP (affecting any RouterOS version newer than 6.46.6), which makes flashing these routers using most people’s usual methods (often tftp32, which is distributed with ROOter images, for example) much more difficult. The method in this article is unaffected, and still works fine. Using this method, dnsmasq is actually transparently handling the Mikrotik using BOOTP which is not broken, and is Mikrotik’s default netboot mode. I didn’t even realize this when first writing the article, because at the time it didn’t matter. However, I just flashed a new hEX yesterday using these instructions, and it was on RouterOS 6.47.9.

Lots of routers now offer a nice little web interface you can use to upload firmware. However, there are still a lot of routers that are easiest to flash using netboot methods like tftp. There are plenty of tutorials on doing this, but most focus on using a server installed on your computer. If this is a second router and you already have a working OpenWRT main router, it’s often actually much easier to just use your main router to TFTP boot, which is something dnsmasq (the default DHCP and DNS server) can do out of the box.

In my case, I already have a primary router with external USB storage up and running. This brief tutorial gives the bare bones steps on what you need to do to use this to flash a second router that supports netboot. I’ll be flashing a Mikrotik hEX RB750Gr3 in this example, since I had one I needed to do anyway. If you don’t already have some external storage set up on your main router, take care of that first – the existing tutorials for that are pretty good, so I won’t duplicate that here.

First, boot up your new router at least once and get its MAC address. For some reason things will go more smoothly if you assign it a static IP when it first boots up as a DHCP client.

Configure /etc/config/dhcp (which controls dnsmasq) on your main router. First, turn on the tftp server, and point it to your USB storage:

config dnsmasq
     ...
     option enable_tftp '1'
     option tftp_root '/mnt/stor/tftp'

Make sure that second line you added points to the correct folder on your USB storage.

Add a static IP for the box you’ll flash:

config host
      option mac 'B8:27:EB:2B:08:85'
      option name 'somehost'
      option ip '192.168.1.240'

Change that MAC to your new router, and give it whatever name and address on its WAN you can remember. You won’t actually need it once it boots up, and you can delete this section once your new router is flashed.

Now, drop the file in the appropriate folder. For TFTP booted routers, you usually need two firmware images: one it can netboot off of from TFTP (which usually has “factory” in the name), and the real copy that gets flashed to the flash memory (usually has “upgrade”). This is a two step process – the netbooted image will not actually be saved to the router, and this is actually a great way to test an OpenWRT build before you flash. You then use the netbooted “factory” image to flash the router using the permanent “upgrade” image. If you don’t do that second step, when you reboot the router, it’ll go straight back to its original OS and settings from memory.

Now, the critical part – take that netboot image in your folder (mine is “openwrt-RB750gr3-GO2021-02-03-factory.bin” for the OpenWRT ROOter fork), and rename it “vmlinux”.

Some router manufacturers also need to find your TFTP server at a specific address, as well. Mikrotik apparently expects 192.168.1.10. If your LAN is already at 192.168.1.0 and the .10 address is free, it is trivial to add .10 as a second address for your main router (this will not affect anything else of significance). From your main router’s command line, simply run:

ip addr add 192.168.1.10 dev eth0.5

Change the bit after “dev” to match whichever interface or port connects to your LAN. In my case, my LAN is on a VLAN port of my router, hence eth0.5.

Now, it’s time to netboot. Shut down your new router if it isn’t already, and plug is WAN port into your existing network.

For the Mikrotik hEX, to trigger a netboot, you plug in the power jack with the reset button already held down. The button does several things depending on how long you hold it down; it comes on lit steady, then starts flashing, then goes off completely. Once it’s off completely you can release the button, as it will be looking for a netboot. If you’re watching your log on your main DHCP router, it’ll post up a log line when it sends the boot image to a DHCP client.

Give it time to boot up, and then try connecting from a client plugged into the LAN side of the new router. One advantage of doing it this way is that you don’t tie up your main computer as both the boot tftp server and the tool you need to log into the new router with. If your OpenWRT image netbooted successfully, you should find your new router at 192.168.1.1 from your test computer.

Now, for the last important part – flash the permanent image! You need to go to System -> Backup / Flash Firmware on the new router and flash that upgrade image, or what you’ve just done won’t stay permanent.

ROOter GoldenOrb Hosting

We’re helping provide overflow hosting space for the wonderful team that keeps this OpenWRT fork going! However, during this morning’s transition, I hear a few people are having cache problems that have redirected them here to the blog front page, instead of the upload and build folders.

If that’s you, here are your direct links to the new folder locations:

http://www.aturnofthenut.com/upload/

http://www.aturnofthenut.com/builds/

Hopefully the redirect issues will clear up quickly. However, if you ever land on my front page accidentally, there will also always be a link at the top of the page with direct links.

Thanks for your patience!

Remote Logging from OpenWRT to Rsyslog

This one is brief and simple. I have six routers going right now (and a ridiculously long article still in draft explaining why), all running OpenWRT. I had them set to save logs to local thumb drives, which, frankly, was a pain in the butt. I concluded that I wanted them all logging to a single remote system for simplicity – the old EEE PC netbook that I use as a network terminal for basic maintenance. It has a good old fashioned spinning disk hard drive, and won’t suffer from a ton of log writes like the thumb drives (or heavens forbid the internal storage) on the routers would.

After going through several tutorials that were either a bit complicated or a bit incomplete for my specific use, it turned out to be obnoxiously simple to implement. I could’ve gotten it all done in under half an hour if I’d already known exactly what I was doing, and most of that time was repetitively ssh-ing into six different routers.

That said, here it is: quick, dirty, with no missing or extra steps!

Set up your log server first

My logserver is running Debian Buster, which already came with rsyslog configured with very sensible basic settings (logging to file in /var/log/, and rotation already set up). All I had to do was enable listening on TCP or UDP 514 (I’ve opened both but am using TCP), then set up some very basic filtering to sort the remote messages the way I wanted.

All changes can be accomplished quickly in /etc/rsyslog.conf. Starting at the top, we uncomment the lines that start the server listening:

# provides UDP syslog reception
module(load="imudp")
input(type="imudp" port="514")

# provides TCP syslog reception
module(load="imtcp")
input(type="imtcp" port="514")

# List of sub networks authorized to connect :
$AllowedSender UDP, 127.0.0.1, 192.168.0.0/16
$AllowedSender TCP, 127.0.0.1, 192.168.0.0/16

The last group there was added based on the recommendations of a tutorial, and restricts senders to localhost and my local network (I have hosts on five subnets, most people could be using 192.168.1.0/24 or whichever single subnet they’ve configured).

Next, near the bottom of the file, you need to decide how you want your messages stored. If you don’t change anything, they’ll be mixed into your other logs from your localhost. You can do a lot of more complicated things, but I wanted one subdirectory per remote host, with all messages in a single syslog.log. Here’s how you get that, in the rules section and above your rules for normal localhost messages:

###############
#### RULES ####
###############

#
# ADDED BY CHUCK
# Redirect all messages received from the network to subfolders first
# From example on stackexchange saved in notes.
#

$template uzzellnet,"/var/log/%HOSTNAME%/syslog.log"

if $fromhost-ip startswith "192.168." then -?uzzellnet
& stop

The template can be named anything. This test checks all log messages to see if they are from remote hosts in my local net – if so, it sends them all to a single file based on the remote hostname. The template statement must be before the test, and “& stop” tells it that any logs meeting this test should not be further processed below with localhost messages.

Obviously your log server will need a static IP to do this job. If you haven’t set one already, you can either set it manually from the server, or (my recommendation) just configure your DHCP router to automatically provision that machine with a static IP.

That’s it for configuring the server! It really is that simple. Just restart rsyslog on your server:

chuck@raul:/etc$ sudo systemctl restart rsyslog

Now, set up each remote OpenWRT host

All settings for logging are stored in /etc/config/system. By default, everything is logged to a ring buffer in memory, and lost on reboot. Not useful if something happens that causes a lockup, etc., but it is awfully handy to read from the command line when you’re already logged in via ssh, so we want to keep that functionality – messages should both be stored in the ring buffer and sent to the remote server.

In /etc/config/system, add or change the following three lines (using the static IP address you’ve provisioned for your log server):

        option log_ip '192.168.1.209'
        option log_port '514'
        option log_proto 'tcp'

You can leave it the default UDP if you prefer – there’s less network overhead, but most of us aren’t really hurting for network capacity. TCP is generally worth it for logging unless you really don’t care if you miss the occasional message.

Now, just restart your logs so the new settings are picked up:

/etc/init.d/log restart
/etc/init.d/system restart

Next, log a test message. It can say anything. This was the one from the last of my six routers to configure, a test machine I’m still setting up to replace one of my production routers soon:

root@FASTer2:~# logger "First test message from Faster2!"

That should produce a log line both locally and remotely. Check the ring buffer:

root@FASTer2:~# logread
Thu Dec 17 20:22:07 2020 daemon.info logread[424]: Logread connected to 192.168.1.209:514
Thu Dec 17 20:22:21 2020 user.notice root: First test message from Faster2!

Now, on your log server, you should see a new directory for your host created in your log folder (probably /var/log/ if you’re using Debian defaults). We said in rsyslog.conf earlier that the file should be in that subfolder and named syslog.log, so let’s test receipt:

chuck@raul:~$ sudo cat /var/log/FASTer2/syslog.log
[sudo] password for chuck:
Dec 17 20:22:07 FASTer2 logread[424]: Logread connected to 192.168.1.209:514
Dec 17 20:22:21 FASTer2 root: First test message from Faster2!

That’s it! We’re all set to go. You can obviously get way more elaborate than this, but a simple 1:1 replacement of OpenWRT’s default ring buffer with a neatly sorted single log file will probably cover most users’ needs.

Enjoy!