Skip to content

Releases

Arteria 2.1.0

Choose a tag to compare

@github-actions github-actions released this 15 Nov 23:00
c6c4a04

Fixes for what the SNBForums thread reported after 2.0.0: AiMesh nodes that crashed while Arteria read them, a page that took seconds to go live, a menu that stopped updating, and ports out of order on the RT-AX88U. Also a page that follows ROG and TUF routers' colours, room for more nodes than the map has zones, and four devices drawn anew. Arteria is now in amtm (7.2 and later) as ar. Thanks to everyone in the thread who tested development versions and posted their output.

Fixes

  • The page is live about a second after it opens. 2.0.0 spaced samples by how long each took, so the first sample, which does the most work (reading the ports, starting the node sessions), held the second one back by 3 to 6 seconds, and the page waited on Connecting… for it. The second sample now comes a second after the first, the names are written alongside instead of before it, and the page checks for samples every second until it is live.
  • AiMesh nodes where reading crashed ("Segmentation fault") — reported on GT6, XD6, RT-AX56U, RT-AX58U, RT-AX86S and RT-BE9700 nodes:
    • Arteria no longer reads a node's uplink. On a node with a Wi-Fi backhaul, the radio's own interface is a client of the router, and the node's devices are on wl0.1-style interfaces; Arteria read the uplink as if devices were on it.
    • A node on an Ethernet backhaul still names its radios as possible uplinks in its settings, but its devices are on them, so Arteria reads them while they work as access points.
    • The node's login shell now runs Arteria's script, as it would run it typed in a terminal there, instead of sh -s.
    • The trace nodes test and doctor save when something crashes no longer needs sh -x, which those nodes' shells refuse (that is why node-trace.txt held only "invalid option -- 'x'"). It names the command that crashed and the node's shell.
    • doctor checks a node the way nodes test does. It said a node was fine when the script had never run there.
  • A node's part of Flow adds up. The bar of a node on a Wi-Fi backhaul could be taller than the ribbons to its devices, for a few seconds after traffic changed. The router counts the backhaul every sample, but the node counts its devices once a round, and those figures reach the page a round later. In the expanded view the minimum width of each quiet device's ribbon hid the gap. The node now also counts its own uplink in the same round, and its part of Flow and the map use that figure. A node on a wired backhaul keeps the router's. A node that joins its radios' uplinks into one interface (dpsta, as on the RP-AX56) counts that interface alone, since it counts every packet its radios do.
  • No phantom node. An old entry in AiMesh's own list with an address outside the router's LAN (often 192.168.50.x, ASUS's default) showed as a node that's down. Such entries are ignored.
  • Ports are numbered as printed on the router. Arteria takes the numbers from the firmware's own port map, where it has one. On the RT-AX88U, LAN 1 to 4 showed in reverse, and LAN 5 to 8, which sit behind one link to a second switch chip, showed as a device on LAN 5 even with nothing plugged in, at that link's speed. They now show as the port that's in use (LAN 7), at its own speed, and nothing shows when none of them is.
  • The menu is updated when it's mounted twice. Every addon with a page mounts the menu copy addons share (/tmp/menuTree.js) over the router's own. An addon that mounts it again without unmounting it first leaves two mounts, one over the other. The router's pages still show the menu, but the copy can then no longer be replaced, so Arteria's update failed ("mv: can't rename … Device or resource busy"). The menu stayed as it was without a word, and a temporary copy was left in /tmp/arteria. Arteria now takes the extra mounts off, replaces the copy, and mounts it once; if even that fails, it leaves the menu as it was and says so. doctor reports a menu mounted more than once, and doctor fix mounts it once.
  • update says when it replaces a development version with the release of the same number (Updating 2.0.0 (development version: … ) -> 2.0.0, the release). It said Updating 2.0.0 -> 2.0.0.
  • "Weak backhaul" only when it is. The verdict is now based on the backhaul link that carries the node's traffic. While the node is quiet, it's based on its fastest link that isn't 2.4 GHz. The speed of an idle link's last packets is no longer counted: they are control frames, sent slowly on purpose. A 6 GHz link is allowed a weaker signal (-78 dBm), as it reads lower for the same quality.
  • Network names instead of "guest". A device on one of the router's guest networks, or on another of Guest Network Pro's networks, shows that network's name. Devices on a main network show none, even when the router serves it on a wl0.1-style interface: Arteria used to call every such device a guest.
  • The page's requests reach Arteria first. The router runs the lines in /jffs/scripts/service-event in order, so a line before Arteria's that ended the script, or waited, kept the page's requests out: the page said Connecting… for ever. Arteria's lines in service-event and services-start now come first, right after #!/bin/sh. They only start Arteria in the background, for its own events, so they never hold up the lines after them. Installing or updating moves them.

Safer on the router

  • nodes test and doctor take at most about 1 MB from a node, as the page's own node sessions already did: a node that sent output without end could fill the router's RAM.
  • The menu copy addons share is edited only when it is root's own file with a single name. A hard link to another file in /tmp passed the old checks, so that file's content could end up readable as the menu. Such a copy is now replaced with the firmware's menu.
  • What doctor and debug show of other programs: another program's line in service-event by the name of the program it runs only (the rest of the line can hold a password or a token), the program holding the sampler's lock by its name only, and the system log only from root's own files.
  • Arteria's lines in service-event and services-start are added and removed safely. The new file is made and checked in full first, and the old one is put back if writing it doesn't come out whole, so a full JFFS can't cut it short and lose other addons' lines.
  • The port map leaves out the AiMesh nodes' ports, which the firmware lists after the router's own: a node's port can't light up one of the router's.

Doctor and debug

  • nodes test explains a node that reads 0 devices. It lists the node's interfaces it reads and the ones it skips as the node's uplink, with the devices on each, and doctor does the same. Devices on a skipped interface mean Arteria took the wrong interface for the uplink on that node.
  • doctor tests what the page does when it opens. It sends the same request as the page, start_arteria, and says whether it reached Arteria and how long it took, and whether samples followed. It then stops sampling again. When something goes wrong it shows:
    • the router's system log lines about requests it delayed or dropped while busy with another one;
    • the sampler's own errors, which used to go nowhere;
    • the other lines in service-event that wait for their program on every request.
  • doctor also finds and fixes a hook file saved with Windows line endings, which the router can't run at all, Arteria's line not being first, and a process left holding the sampler's lock (every sampler the page starts would give up at once).
  • debug shows more, still without names or addresses:
    • each Wi-Fi interface's band setting and channel, mode and bridge, and whether its network is a main one;
    • the firmware's port map;
    • each node's backhaul links (band, signal, the speed of the last packets each way);
    • which sections the router's AiMesh client list has;
    • the sampler's last errors;
    • the system log's lines about the page's requests.

The page

  • Labels stay off other devices on a crowded map. With many devices, in the expanded view especially, the last labels to be placed found every spot near their device taken, and one could end up over another device's drawing or over the zoom buttons. Once all labels are placed, a label still covering a device now moves to a free spot further out, with a longer line.

  • More AiMesh nodes than the map has room for. The map has a zone for two nodes, three in the expanded view. With more, the first ones in the list got the zones, and the others weren't drawn at all, without a word. Now the busiest nodes get the zones, and keep them unless a node without one gets much busier. The tray names the nodes without a zone (+1 node), and its list says their devices are in it. Flow shows every node, as before.

  • Colours that follow the router's theme. On ROG and TUF routers, whose pages are black with red or amber, Arteria's controls, highlights and room turn black with red or amber too. The traffic's colours stay as they are everywhere.

  • Less motion. When the device asks for less motion (Windows' animation effects off, macOS's Reduce motion, Android's Remove animations), the packets stand still. That used to happen without a word; now the map's legend says so, with an Animate button, which the browser remembers.

  • Four devices drawn anew:

    • the VR headset: a curved glass visor with a soft band;
    • the car: a smooth electric saloon with a glass roof;
    • the washing machine and dryer: round porthole doors;
    • the smart plug: a round plug in a wall socket.

    Their icons match.

Install or update

Over SSH on the router:

d=/tmp/arteria-install; rm -rf "$d" && mkdir -m 700 "$d" && curl -fsL --retry 3 "https://github.com/IfSugar/arteria/releases/download/2.1.0/arteria.sh" -o "$d/arteria.sh" && sh "$d/arteria.sh"...
Read more

Arteria 2.0.0

Choose a tag to compare

@github-actions github-actions released this 13 Nov 15:33
f91378e

Arteria's second release: rename devices right from the map, zoom into the expanded map, 24 more kinds of device, and a router that's left alone when it's struggling. Thanks to everyone in the SNBForums thread for the reports that shaped it.

New

  • Rename devices from Arteria. A pencil after a device's name in the live readout (or the name itself) opens a name field; while you type, the icon shows what the device will be drawn as. Enter or the check saves it in the router's own client list, so the router shows it too, with a matching icon where the router has one; Escape or the cross keeps the old name, and an empty name brings the router's own back. Offline devices can be renamed too. Each rename starts from the router's client list as it is at that moment, so it never undoes another rename or a change made in the router's own client editor, and nothing is saved when that list can't be read. Names Arteria would ignore (ones routers fill in themselves, like ESP-…) are refused. Each rename leaves two lines in the system log, with how many names the list holds before and after (no names or addresses).
  • Zoom and pan the expanded map, like a whiteboard: the mouse wheel or a trackpad pinch zooms around the pointer, dragging or a two-finger scroll moves around, and − / 100% / + in the corner zoom in steps or show the whole map again. It never shows empty space past the map's edges, opens on the whole map each time, and a label reached with Tab comes into view. The map zooms its drawing, not a picture of it, and its animations wait while it moves, so it stays sharp and smooth even at 400% with a device traced.
  • doctor (also d in the menu) looks for the known problems and says what fixes each; doctor fix fixes the ones it can: a hook line left by an older version or by going back to 1.0.0, files older versions left, page files any program could change, a client list copy or a node session left after the page closed. On each node it checks key login and runs Arteria's script once, traced, to name any command that crashes there. Nothing in its output names a device or an address.
  • Dual WAN: the second WAN counts as internet too, instead of as local traffic, and the Internet readout shows what each WAN carries.
  • Guest Network Pro: wired devices on a Guest Network Pro network (a LAN port in a VLAN profile) are placed on their port.
  • Short rates show their unit: 47k, 2.1m and 1.25g in bits, 47K, 2.1M and 1.25G in bytes. Megabits used to show as a bare number.

Safer on the router

  • Arteria keeps out of the way of a struggling router. While it samples it watches the load and the memory available. On a busy router (a load of 2 per CPU core, or under 48 MB available) it samples a third as often and opens no new node sessions; on an overloaded one (4 per core, or under 24 MB, when the page opens or for three samples in a row), or one that needs over 15 s for two samples in a row, it stops for 2 minutes. The page says why, the system log gets a line, and status shows the load, the memory and the last pause. A router that's slow to sample is sampled less often, up to every 10 seconds.
  • A quieter system log. The page keeps sampling going with a request every so often, and the router writes two lines to its system log for each. The page now asks every 45 seconds instead of every 8 (every 8 until the first sample comes, and again right away if samples stop): about 160 lines an hour instead of 900. The map and Flow still update every 2 seconds. Closing or pausing the page still stops sampling at once; a hidden tab stops it after 2 minutes instead of 20 seconds (IDLE_STOP, now at least 120).
  • The page stops asking after a minute without samples, says what to check, and its Stopped button tries again. It used to ask every 8 seconds for as long as it was open.
  • The service-event hook starts Arteria for its own events only. It used to start the script for every service event on the router. Installing or updating replaces the old line.
  • Only root can change the page's files. The router starts Arteria with nothing masked, so its data files and their folder were writable by any program on the router.
  • The README explains how to get a struggling router back without a factory reset: turn off JFFS custom scripts and configs, reboot, then uninstall over SSH.

AiMesh nodes

  • Routers already set up for passwordless logins to their nodes work as they are. If root on the router has a key that opens the nodes (~/.ssh/id_dropbear, as the forum's guide and the Wireless Report addon set up), Arteria uses it and trusts each node as root's known_hosts does: no nodekey, no password. nodekey still sends a password only to a node whose identity you confirmed there.
  • Slow nodes count as answering: a node is judged by its own pace (up to a round every 30 seconds), not by 3 rounds of 2 seconds.
  • A node where something crashes says so (Segmentation fault), instead of "isn't answering".
  • nodes test shows whether the page can read each node: besides key login, it runs one round of the page's script there and reports how many devices it read and how long that took, or why it failed (addresses and user names taken out), and which key works. It, nodekey and doctor answer sooner: they look every 0.2 seconds, not every second.
  • nodekey changes only what it must: it adds Arteria's key to the router's list only for nodes no key reaches yet, and warns when the list already has other keys (nodes with ASUS's own firmware take only the first). With Allow Password Login off it no longer tries a password: the key goes into the router's list, and it says to reboot the node, which is when a node loads that list. It no longer leaves node_key.new.pub behind.
  • debug shows each node's pace, how fresh its output is, how many stations it reports and its last SSH message, plus which keys the router has for its nodes. It no longer lists nodes as down while the page is closed.

Devices

  • 24 more kinds, 51 in all, each with its own drawing and icon: LED strip (Govee, WLED, TV backlights), boiler (and boiler gateways: EMS-ESP, ebusd, Vitoconnect), air purifier or humidifier, smart switch, door sensor, washing machine, dryer, dishwasher, Raspberry Pi, streaming stick, smart speaker (Echo, HomePod, Nest Audio), smart display (Echo Show, Nest Hub), projector, VR headset, 3D printer, car, EV charger, solar inverter or home battery, robot mower, sprinkler, garage door, smart blinds, pet device and fitness equipment.
  • Words run together are recognised: JohnsNas, KidsTV, nas01 and office_printer are read like John's NAS, so the same rules work for everyone's names.
  • A nickname wins over the icon the router guessed: when the router's icon is just its own guess, or a computer, phone, tablet, watch or console icon on a device named after a home device, the name decides (Lounge Daikin AC is an air conditioner, not the console the router guessed). Icons you picked still come first. A nickname the router saved by itself ("dhcpcd-6 8 2…", the maker's name) isn't used as a name.
  • Many more names and makers, including the names devices give themselves: Tapo and Kasa model numbers (L630, P110, C200), Govee (ihoment_H6159_…), Bosch, Siemens and Neff machines by model, printers (NPI…, BRW…, hpenvy-…), Ring cameras, Echo speakers (amazon-…), Daikin's Wi-Fi adapters, Sony and Samsung TVs by model number, and many phones, tablets, TVs, speakers, locks, lights, hubs and vacuums.

The page

  • Labels never sit on one another or on another device's drawing: on a crowded floor a label moves further out, beside the floor if need be.
  • Tap a device's drawing to trace it, as with its label. Anything cut short with "…" shows in full when you point at it.
  • Flow rows stay put: a row keeps the room its traffic needed lately instead of resizing with every sample. The expanded Flow view fits the window even during a speed test.
  • A calmer tab bar: the totals keep their width as the numbers change, the buttons and switches match, and the line of text under the title is gone, leaving more room for the map.

Fixes

  • check no longer warns when the router has no Wi-Fi clients of its own (all of them on a node, say): it notes that the counters will be checked once one connects.

Install or update

Over SSH on the router:

d=/tmp/arteria-install; rm -rf "$d" && mkdir -m 700 "$d" && curl -fsL --retry 3 "https://github.com/IfSugar/arteria/releases/download/2.0.0/arteria.sh" -o "$d/arteria.sh" && sh "$d/arteria.sh" install; rm -rf "$d"

Already installed? Run /jffs/addons/arteria/arteria.sh update. Your settings and node access are kept.

Full diff: 1.0.0...2.0.0

Arteria 1.0.0

Choose a tag to compare

@github-actions github-actions released this 12 Nov 12:26
38b3fd1

The first release: a live, animated map of how traffic flows between the internet, your router, its AiMesh nodes and every device.

  • Map: an isometric view of your network. Cables are pipes and Wi-Fi links are arcs; each packet is traffic in motion, and packets grow and bunch up as throughput rises while moving at the same calm speed. Blue is download (toward the device), orange is upload (toward the internet), violet is the AiMesh backhaul. Devices behind a node stand in its zone. On a busy network the smallest devices are grouped into a +N more tray.
  • Flow: a Sankey "river" from the internet (and local traffic) through the router, each band, port and node, to every device. Ribbon width follows throughput, with Download and Upload views. Rows keep a fixed order, so nothing jumps around while you watch.
  • Tap any device to trace its path: everything else dims, and the readout shows its download and upload, its share of the total, signal, link rate and the path its traffic takes. Details shows its IP and MAC address, host name, maker, system, Wi-Fi standard and channel width (or port and speed), connection time, IPv6 and DHCP lease.
  • 27 kinds of device, each with its own drawing and icon: desktop PCs, Mac desktops, laptops, phones, tablets, watches, TVs, streaming boxes, speakers, soundbars, game consoles, printers, NAS, cameras, doorbells, smart locks, thermostats, lights, smart-home hubs, air conditioners, robot vacuums, appliances, smart plugs, sensors and more. The icon you choose in the router's client list always wins; otherwise the device's name, what the router detected, and its maker decide.
  • AiMesh nodes and the router drawn as what they are: plug-in extenders, towers, cubes, pucks, gaming routers and classic routers, by model.
  • The +N more tray opens a list: tap it to see the grouped devices, busiest first, and tap any of them to trace it.
  • Private Wi-Fi addresses are marked as such, and a device whose private address changed is recognised by its host name when that's unambiguous, so it keeps its name and icon.
  • Expanded view: a button opens a bigger view that fills the window (or the screen), with a stand for every device on a typical home network, a third line on each label, Flow rows with address, signal and link rate, and the readout's traffic and details together.
  • A Device report (at the bottom of the page) shows how each device was recognised, without names or addresses, for issues about a device drawn as the wrong thing.
  • AiMesh nodes, per device. The router reads each node's own clients over a single SSH session per node, with a key only the router holds (arteria.sh nodekey sets it up, shows a node's fingerprint before trusting it, and keeps the key on the nodes across AiMesh syncs). Without the key, the map still shows each node's backhaul total.
  • Only while the page is open. Sampling starts when you open the page and stops about 20 seconds after you close it or switch to another tab. Nothing runs in the background, there are no cron jobs, and samples stay in RAM.
  • Mb/s or MB/s: a switch at the top shows every rate in megabits or megabytes per second, and the page remembers your choice.
  • The Whole network readout splits each total into internet and local traffic (between your devices, or to the router itself), so it's clear why it's higher than the Internet figures.
  • Notices for a weak or offline backhaul and for nodes that can't be read.
  • A terminal menu, ready for amtm, with amtmupdate, update dev [branch] for trying unreleased changes, and a debug report with no names or addresses.

Install or update

Over SSH on the router:

d=/tmp/arteria-install; rm -rf "$d" && mkdir -m 700 "$d" && curl -fsL --retry 3 "https://github.com/IfSugar/arteria/releases/download/1.0.0/arteria.sh" -o "$d/arteria.sh" && sh "$d/arteria.sh" install; rm -rf "$d"

Already installed? Run /jffs/addons/arteria/arteria.sh update. Your settings and node access are kept.