From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: [9front] how to create a blackhole/null route
Date: Sat, 27 Jul 2024 01:00:08 -0400 [thread overview]
Message-ID: <1D8B5A71-C555-487D-A493-E891F4127530@stanleylieber.com> (raw)
the following did not work as intended:
; { echo bind null; echo add 192.69.69.69 255.255.255.0 } >/net/ipifc/clone
; echo 'add 47.128.0.0 255.255.0.0 192.69.69.69' >/net/iproute
this resulted in:
; cat /net/iproute
0.0.0.0 /96 168.235.82.1 4 none 0 168.235.82.0 /120
0.0.0.0 /96 168.235.82.1 4 none 0 168.235.82.67 /128
224.0.0.1 /128 224.0.0.1 4m ifc 0 168.235.82.67 /128
224.0.0.1 /128 224.0.0.1 4m ifc 1 192.69.69.69 /128
192.69.69.0 /120 192.69.69.0 4i ifc 1 0.0.0.0 /96
192.69.69.0 /120 192.69.69.0 4i ifc 1 192.69.69.69 /128
192.69.69.0 /128 192.69.69.0 4b ifc 1 192.69.69.69 /128
192.69.69.69 /128 192.69.69.69 4u ifc 1 0.0.0.0 /96
192.69.69.255 /128 192.69.69.255 4b ifc 1 192.69.69.69 /128
168.235.0.0 /128 168.235.0.0 4b ifc 0 168.235.82.67 /128
168.235.82.0 /120 168.235.82.0 4i ifc 0 0.0.0.0 /96
168.235.82.0 /120 168.235.82.0 4i ifc 0 168.235.82.67 /128
168.235.82.0 /128 168.235.82.0 4b ifc 0 168.235.82.67 /128
168.235.82.67 /128 168.235.82.67 4u ifc 0 0.0.0.0 /96
168.235.82.255 /128 168.235.82.255 4b ifc 0 168.235.82.67 /128
168.235.255.255 /128 168.235.255.255 4b ifc 0 168.235.82.67 /128
47.128.0.0 /112 192.69.69.69 4 none 1 0.0.0.0 /96
255.255.255.255 /128 255.255.255.255 4b ifc 0 168.235.82.67 /128
255.255.255.255 /128 255.255.255.255 4b ifc 1 192.69.69.69 /128
fe80:: /64 fe80:: 6i ifc 0 fe80::f816:3eff:fe07:480d /128
fe80::f816:3eff:fe07:480d /128 fe80::f816:3eff:fe07:480d 6u ifc 0 fe80::f816:3eff:fe07:480d /128
ff02:: /16 ff02::1 6m ifc 0 fe80::f816:3eff:fe07:480d /128
ff02::1 /128 ff02::1 6m ifc 0 fe80::f816:3eff:fe07:480d /128
ff02::1:ff07:480d /128 ff02::1:ff07:480d 6m ifc 0 fe80::f816:3eff:fe07:480d /128
but:
1.) traffic from 47.128.0.0/16 still reached 168.235.82.67.
2.) after a few minutes the normal 168.235.82 routes disappeared from iproute, leaving only the new 192.69.69 lines, rendering the machine entirely inaccessible.
what am i doing wrong?
sl
next reply other threads:[~2024-07-27 5:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-27 5:00 Stanley Lieber [this message]
2024-07-28 1:18 ` sl
2024-07-28 2:19 ` Romano
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=1D8B5A71-C555-487D-A493-E891F4127530@stanleylieber.com \
--to=sl@stanleylieber.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).