Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

"Discovery: service is on this subnet, ignoring"

Open
#166 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
android, linux, python

Research direction

Start with server.py line 195 and trace the discovery path that emits the subnet warning. Reproduce the debug-mode discovery attempt with the Android phone, then determine why its address is rejected; done means the cause is confirmed and the behavior is fixed or clearly documented.

Written by the indexing model from the issue text.

Description

I'm running Warpinator 1.4.5 (Flatpak) on openSUSE Tumbleweed. When I run it in debug mode, my Android phone can't see it. The logs give me:

2023-03-04 16:53:05,621::warpinator::DEBUG: >>> Discovery: service is not on this subnet, ignoring: Pixel 4a (203.0.113.69) -- server.py (line 195)

I'm using the same group code and the same ports. I've unblocked everything (yes, even 5353 UDP) in my firewall. What's going on? What does this message mean?

Dominant language
C
Stars
1.6k
Forks
114
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from linuxmint/warpinator

All issues in linuxmint/warpinator

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.