openwrt / openwrt/packages

watchcat: ping responses not acknowledged over mesh network on 25.12.0

Open
#28,667 21 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug help wanted release/25.12
Dominant language
Makefile
Stars
4.6k
Forks
4k
Avg merge
3d 12h
Merged PRs (30d)
134

Description

Package Name

watchcat

Maintainer

@roger-

OpenWrt Version

25.12.0-rc5

OpenWrt Target/Subtarget

ipq40xx/generic

Steps to Reproduce

Watchcat is not recognizing ping responses if the ping transverses through a mesh network.

Using the diagnostic tool on the same router, ping responses are coming in normally. When Watchcat pings the same address, Watchcat sees no response. This issue was not present with 25.10.X and prior.

Actual Behaviour

Diagnostic Ping response from 192.168.1.1 to 192.168.1.12 over a mesh:
64 bytes from 192.168.1.12: seq=2 ttl=64 time=1.353 ms

Watchcat Ping response missing from 192.168.1.1 to 192.168.1.12 over a mesh::
watchcat[4123]: Could not reach 192.168.1.12 for 1500. Rebooting after reaching 3600

Confirmation Checklist

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the watchcat package entry point and compare its ping-response handling between 25.12.0-rc5 and 25.10.X. Reproduce the issue by pinging 192.168.1.12 over the mesh, then verify that watchcat acknowledges the response instead of reporting the host as unreachable.

Written by the indexing model from the issue text.

Assessment

Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.