Repository navigation
Releases
v6watch 0.4.0
v6watch finally has a face. Until now it was the quiet type: it lived in
cron, did its job every five minutes and only ever spoke through log files,
like a night guard who leaves notes on the fridge. Now type v6watch over
SSH and it greets you with a banner, tells you how your prefix is doing and
lets you poke at it with a single key. Same watchdog underneath, just with
better manners. Editing the settings from the menu is coming in 0.5.0.
Added
- Interactive menu:
v6watchover SSH shows whether the watchdog is running,
the LAN address, the result of the last check and the last event, and lets
you check the prefix, read the log (colored by event), see the changed
settings and pause or resume the monitoring. Colors only on a terminal and
never withNO_COLOR. - The
v6watchcommand, added by the installer to
/jffs/configs/profile.add(and removed by the uninstaller). v6watch.sh menu; with no command,v6watch.shopens the menu when started
from a terminal and does a run otherwise, as before.- Every run, and every
check, records its result in/tmp/v6watch.status
for the menu.
v6watch 0.4.0-beta.1
Added
- Interactive menu:
v6watchover SSH shows whether the watchdog is running,
the LAN address, the result of the last check and the last event, and lets
you check the prefix, read the log (colored by event), see the changed
settings and pause or resume the monitoring. Colors only on a terminal and
never withNO_COLOR. - The
v6watchcommand, added by the installer to
/jffs/configs/profile.add(and removed by the uninstaller). v6watch.sh menu; with no command,v6watch.shopens the menu when started
from a terminal and does a run otherwise, as before.- Every run records its result in
/tmp/v6watch.statusfor the menu.
v6watch 0.3.0
Added
- Automated scenario tests (
tests/run.sh) with stub router commands, run in
GitHub Actions under BusyBoxsh,dashandbash --posix. - Invalid settings in
v6watch.conf(a letter in a number, a zero threshold,
a wrongDAILY_CHECKtime...) are reported in syslog, and bycheck, and
replaced by their defaults instead of breaking the run. - Pre-releases: tags like
v0.3.0-beta.1are published as GitHub
pre-releases, which the README install never picks up. - Issue templates for bug reports and for routers where v6watch works.
Changed
- Outage durations and the WAN restart rate limit are measured on the router
uptime instead of the clock, which is wrong until NTP syncs and can jump. - The daily check is written at the first good check from
DAILY_CHECKon,
once a day, instead of only when a run falls exactly on that minute, and is
skipped while the clock is not set yet.
Fixed
- A run could be skipped for as long as another process reused the PID of a
run that had died holding the lock: a lock older than any run can last is
now taken over.
v6watch 0.3.0-beta.1
Added
- Automated scenario tests (
tests/run.sh) with stub router commands, run in
GitHub Actions under BusyBoxsh,dashandbash --posix. - Invalid settings in
v6watch.conf(a letter in a number, a zero threshold,
a wrongDAILY_CHECKtime...) are reported in syslog, and bycheck, and
replaced by their defaults instead of breaking the run. - Pre-releases: tags like
v0.3.0-beta.1are published as GitHub
pre-releases, which the README install never picks up. - Issue templates for bug reports and for routers where v6watch works.
Changed
- Outage durations and the WAN restart rate limit are measured on the router
uptime instead of the clock, which is wrong until NTP syncs and can jump. - The daily check is written at the first good check from
DAILY_CHECKon,
once a day, instead of only when a run falls exactly on that minute, and is
skipped while the clock is not set yet.
Fixed
- A run could be skipped for as long as another process reused the PID of a
run that had died holding the lock: a lock older than any run can last is
now taken over.
v6watch 0.2.0
Added
- The installer warns when Dual WAN is enabled; the README explains why
v6watch and Dual WAN (e.g. the WAN Failover add-on) get in each other's way. - Every release comes with a
v6watch.tar.gzarchive, built and attached by
GitHub Actions when a version tag is pushed. RESTART_MAX_INTERVAL(default one day): while WAN restarts do not bring
the prefix back, the wait between them doubles after each one up to this
value, instead of restarting every hour for the whole outage.RESTART_ON_WAN_FAIL: set it to0to skip the WAN restart when the WAN
address fails too. The default keeps restarting.- A LAN left with no usable global address while
odhcp6cis running is now
logged and recovered like a prefix that is not routed; before, v6watch did
nothing.
Changed
- The WAN is restarted after
FAIL_THRESHOLDconsecutive failed checks
(default 2) instead of at the first one, so a short IPv6 glitch no longer
drops IPv4 too. The DHCPv6 renew is still tried at the first failure.
FAIL_THRESHOLD=1gives the previous behaviour. - The README installs the latest release instead of the
mainbranch, so
unreleased changes no longer reach users.
v6watch 0.1.0
First public version of v6watch, an IPv6 prefix delegation watchdog for Asuswrt-Merlin.
Some ISPs silently stop routing the delegated IPv6 prefix while its DHCPv6 lease is still valid: devices keep a "valid" but orphaned address and new connections hang. v6watch pings out from the delegated prefix every 5 minutes and, when it is not routed, asks odhcp6c for a DHCPv6 renew and, if needed, restarts the WAN (at most once per hour).
Highlights
- Routing check with
ping6 -Ifrom the delegated prefix, plus a WAN address test to tell a dead prefix apart from a general IPv6 outage - DHCPv6 renew first, rate-limited WAN restart as a last resort
- Persistent log of prefix changes (with router uptime), outages and their duration, with minimal flash writes
checkcommand for a quick diagnosis without side effects- Idempotent installer that only appends its own line to
services-start, and a clean uninstaller - No Entware dependencies
Install
See the README. Tested on an ASUS RT-BE88U with Asuswrt-Merlin 3006.102.9.
Full changelog: CHANGELOG.md