Skip to content

Firmware v3.0.25-beta.13 — safer web access, DNS fixes, mobile data limit

Pre-release
Pre-release

Choose a tag to compare

@Mattboxx Mattboxx released this 17 Nov 17:39

Firmware v3.0.25-beta.13 — safer web access, DNS fixes, mobile data limit

Beta for testing. USB modems, sticks, adapters and phones are still not
tested with real devices; please report your board and device (the Network
page shows it as vendor:product). Everything below is off by default unless
it says otherwise.

Changes since beta.8

Fixed

  • Large DNS answers no longer reach devices cut. The gateway's DNS relay
    used to pass answers above 1 KB on cut and cache them (present since its
    first version). It now asks resolvers for at most 1 KB, turns a longer
    answer into a proper "truncated" reply, never caches truncated answers, and
    also answers DNS over TCP (answers up to 16 KB), asking the resolver over
    UDP with room for 4 KB first. Note: many home routers answer DNS with at most 512 bytes and refuse
    TCP; with such a router, large answers (long TXT records, some services)
    cannot be resolved by any device, with or without the gateway. Setting a
    resolver that supports TCP in the DNS relay settings solves it.
  • USB network sessions: sending a frame while the USB device was
    unplugged could write into memory already freed. Fixed.
  • PPP over a USB modem no longer blocks the gateway's network core while
    the modem is slow: frames are queued instead of waited for.

Security

  • Web sessions are bound to the device that logged in. The web page uses
    plain HTTP; a session cookie copied off the local network or the access
    point no longer works from another device. Changing network asks for the
    password again.
  • Administration can be limited to the tailnet and the access point
    (System → Access, off by default). While the gateway is not connected to the
    tailnet, the local network keeps access, so you cannot lock yourself out.
  • The SNMP community is no longer shown by the web page or API (an empty
    field keeps the saved one), and the card warns while it is still "public".
  • A security event is recorded when the plain-TCP remote console listens on
    the local network or the access point.

Added

  • Monthly mobile data limit (Network → Cellular uplink): counts mobile
    data, warns at a chosen percentage and at the limit, and can stop using
    mobile data until the next month. The month can start on any day 1–28.
    Nothing is counted or written while it is off.
  • Traffic per access-point device (Network → Clients): what each device
    sent and received through the gateway.
  • Events when mobile data starts or stops carrying the Internet traffic
    (a warning in failover mode, where it means Wi-Fi and Ethernet are down).
  • Signal and operator for Huawei HiLink 4G sticks in USB network mode
    (experimental, not tested with a real stick).
  • DNS diagnostics show queries over TCP and oversized answers.

Changed

  • Health & resources moved to Diagnostics → Hardware.
  • Telegram and ntfy remote commands are laid out the same way, with the
    command reference at the end of each card; command options look inactive
    while commands are off.
  • The settings search finds the new functions, also by synonyms and in every
    language.
  • The DNS cache keeps two entries per slot, so busy names evict each other
    less.

Tested

  • Offline: the full validation campaign (host tests of the actual firmware
    code, browser tests of the web page, build and image provenance).
  • On the maintainer's ESP32-S3 over Tailscale: install with saved settings
    unchanged, the new settings and API fields, the access limit (the local
    address refused while the tailnet address works), DNS answers over UDP and
    TCP (TCP through a resolver that supports it), the web page answering for
    3 minutes. Settings changed for the tests were restored.
  • Not tested: real USB modems, sticks, adapters and phones; HiLink signal.

Install

Use System → Updates with "Include beta / pre-release updates", or
System → Firmware with firmware.bin below. The stable release stays
v3.0.24.