From: Romano <me+unobe@fallglow.com>
To: 9front@9front.org
Subject: Re: [9front] how to create a blackhole/null route
Date: Sat, 27 Jul 2024 19:19:18 -0700 [thread overview]
Message-ID: <6F1265385F9F18BCA2B6FB9A6C6B1236@smtp.pobox.com> (raw)
In-Reply-To: <AAC1527F472FF25144DF6476E5695BD9@gaff.inri.net>
On Sat Jul 27 18:23:42 -0700 2024, sl@stanleylieber.com wrote:
> today's commits fixed multiple kernel bugs and resolved this issue
> for me. here's how to setup a successful blackhole route:
>
> # create a null device with junk ip address
> ; ip/ipconfig null /dev/mordor 192.69.69.69 255.255.255.0
Is there a reason why /dev/mordor and not /dev/null? Is that needed
to actually return some junk to splooge over the requester?
next prev parent reply other threads:[~2024-07-28 2:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-27 5:00 Stanley Lieber
2024-07-28 1:18 ` sl
2024-07-28 2:19 ` Romano [this message]
2024-07-28 4:37 ` Stanley Lieber
2024-07-31 2:09 sl
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=6F1265385F9F18BCA2B6FB9A6C6B1236@smtp.pobox.com \
--to=me+unobe@fallglow.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).