firewall is not allowing on ports

Open
#229 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reproducing the reported behavior on Debian 13 with UFW enabled and disabled, using the listed rules and Warpinator ports 42000 and 42001. Verify whether the connection succeeds with the firewall configured and document the required rule or behavior; the issue names no source files or tests to inspect.

Written by the indexing model from the issue text.

Description

Distribution

debian 13

Package version

latest build from github

Frequency

Always

Bug description

these are my firewall rules to allow warpinator to use the local network
sudo ufw allow from 192.168.0.0/24 to any port 42000 proto udp
sudo ufw allow from 192.168.2.0/24 to any port 42000 proto tcp
sudo ufw allow from 192.168.0.0/24 to any port 42001 proto udp
sudo ufw allow from 192.168.2.0/24 to any port 42001 proto tcp

sudo ufw allow from any port 42000 proto udp to 192.168.0.0/24
sudo ufw allow from any port 42000 proto tcp to 192.168.2.0/24
sudo ufw allow from any port 42001 proto udp to 192.168.0.0/24
sudo ufw allow from any port 42001 proto tcp to 192.168.2.0/24

with the firewall on it will not connect, with the firewall off it will connect.
what am i missing? warpinator does not require internet does it?

( i always have to manually connect regardless of the firewall)

Steps to reproduce

enable firewall no connect
disable firewall connect

Expected behavior

should connect with correct port open default port is 42000 and 42001

Additional information

No response

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

Contributor guide

No contributing guide indexed for this repository

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.