From: william@thinktankworkspaces.com
To: 9front@9front.org
Subject: Re: [9front] dns tools
Date: Sun, 29 Jan 2023 20:11:27 -0800 [thread overview]
Message-ID: <870753E8408F0CA0264BF2A8C015D350@thinktankworkspaces.com> (raw)
In-Reply-To: <A48D39B9-50FE-4A5E-AAA6-18098FB5C618@stanleylieber.com>
Do we have any firewall tools? I would like to block some connections.
I know you can tweak routing by messing with /net/ipifc/clone
Just wanted to know if we have any other ways to block conncetions?
Quoth Stanley Lieber <sl@stanleylieber.com>:
> check out iwhois (documented in the tel man page).
>
> also: lookman dns.
>
> the existing tools are fairly manual and rudimentary.
>
> sl
>
next prev parent reply other threads:[~2023-01-30 4:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 1:52 william
2023-01-30 2:10 ` Stanley Lieber
2023-01-30 4:11 ` william [this message]
2023-01-30 4:59 ` Stanley Lieber
2023-01-30 5:27 ` Jacob Moody
2023-01-31 6:41 ` william
2023-01-31 7:58 ` Steve Simon
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=870753E8408F0CA0264BF2A8C015D350@thinktankworkspaces.com \
--to=william@thinktankworkspaces.com \
--cc=9front@9front.org \
/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.
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 NNTP newsgroup(s).