htrgouvea/nipe

Conflicting iptables rules

Open

#88 opened on Jan 24, 2020

 (2 comments) (2 reactions) (2 assignees)Perl (340 forks)batch import
help wantedrecommendation

Repository metrics

Stars
 (2,385 stars)
PR merge metrics
 (Avg merge 5h 52m) (2 merged PRs in 30d)

Description

It seems some startup services may add conflicting rules to the system against Nipe:

$ ./nipe.pl start
...
$ ./nipe.pl status
[!] ERROR: sorry, it was not possible to establish a connection to the server.
$ curl https://check.torproject.org/api/ip
curl: (6) Could not resolve host: check.torproject.org

A solution I found was to completely flush iptables rules before nipe set its own rules:

$ ./nipe.pl stop
# iptables -F
$ ./nipe.pl start
...
$ curl https://check.torproject.org/api/ip
{"IsTor":true,"IP":"46.165.245.154"}
$ ./nipe.pl status
[+] Status: activated. 
[+] Ip: 87.118.116.103

One problem with this solution is the possible future conflicts we may have against other apps on the system. I'm don't really know how iptables works, so any help is welcome!

Contributor guide