From: "Eric Brown" <ecbrown@ericcbrown.com>
To: "Arun Isaac" <arunisaac@systemreboot.net>, 48753-done@debbugs.gnu.org
Subject: [bug#48753] iptables example update
Date: Sun, 06 Jun 2021 13:52:57 -0500 [thread overview]
Message-ID: <ec96f332-8c7c-475d-8671-3fa023f9c38f@www.fastmail.com> (raw)
In-Reply-To: <87im2uwzty.fsf@systemreboot.net>
On Thu, Jun 3, 2021, at 1:46 PM, Arun Isaac wrote:
>
> Hi Eric,
>
> I wrote the iptables service and documentation. So, the mistake is
> entirely due to my poor grasp of iptables! :-)
>
> I have applied your patch, and pushed to master. Thanks!
>
> Cheers,
> Arun
>
> Attachments:
> * signature.asc
Hi Arun,
Thank you for applying the patch, I think it’s much better. Truthfully i am relieved that you are an iptables newbie and so am I!
I think there could still be some work done to this recommendation. For example, when I use this updated iptables firewall selection, I am unable to telnet into ports open on localhost. An example is that I am a heavy user of VNC/SSH tunnel connections and it doesn’t let me do that, it blocks e.g. port 5902. (A similar naive rule in nftables does let this work!!!)
But so many examples are given in iptables (esp. WireGuard stuff) and so if you have no objections, I would like to take a further look and maybe even ask around as to what the ‘ufw allow ssh’ behavior vis-a-vis iptables best practices.
Best regards,
Eric
next prev parent reply other threads:[~2021-06-06 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-30 21:07 [bug#48753] iptables example update Eric Brown
2021-06-03 18:46 ` bug#48753: " Arun Isaac
2021-06-06 18:52 ` Eric Brown [this message]
2021-06-16 7:18 ` [bug#48753] " Arun Isaac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ec96f332-8c7c-475d-8671-3fa023f9c38f@www.fastmail.com \
--to=ecbrown@ericcbrown.com \
--cc=48753-done@debbugs.gnu.org \
--cc=arunisaac@systemreboot.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).