From: Arun Isaac <arunisaac@systemreboot.net>
To: Eric Brown <ecbrown@ericcbrown.com>, 48753-done@debbugs.gnu.org
Subject: [bug#48753] iptables example update
Date: Wed, 16 Jun 2021 12:48:41 +0530 [thread overview]
Message-ID: <87tulyp99q.fsf@systemreboot.net> (raw)
In-Reply-To: <ec96f332-8c7c-475d-8671-3fa023f9c38f@www.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]
Hi Eric,
> 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!
:-P
> 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!!!)
I'm not able to reproduce this. I built and started a container with an
ssh server on port 5902. And, I was able to connect fine with
telnet. Could you describe the precise steps, configuration, etc. to
reproduce this issue?
> 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.
Sure, please do! You don't need my permission for that! :-)
Regards,
Arun
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 524 bytes --]
prev parent reply other threads:[~2021-06-16 7:19 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 ` [bug#48753] " Eric Brown
2021-06-16 7:18 ` Arun Isaac [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tulyp99q.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=48753-done@debbugs.gnu.org \
--cc=ecbrown@ericcbrown.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.