From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: [9fans] cat /net/iproute
Date: Thu, 3 Apr 2003 21:39:16 -0500 [thread overview]
Message-ID: <d7a002f4af281aff27c5b347960b51e3@plan9.bell-labs.com> (raw)
geoff found that cat #I/iproute could give bad doodoo, for example:
; cat /net.alt/iproute
0.0.0.0 /96 63.192.14.225 4 none 0
€>%[$\x17\x7f€€JX€p€€QMs€p\x1e€DE€Ԟ€€€
€j\x1d-€wKf€€-€€ս€\x16\x14[2€€€\x16€j€€mmï€P€f€€€fx#\x14€€€T\a€v€n€€Yqz)-,g€€\x0263.0.0.0 /128 63.0.0.0 4b ifc -
€\aO€.:€€W^€€\x0e\x7f6.T€\x13t€€uT€€€€€_"€\x03\x16gt€€€x€\x18€€€€€Ai^[H€rН€q€;\x19€W€\x16€0€€€q€€q€^[a€\x1f[;€32€€\x13j€W$€€€#€€63.192.14.224 /124 63.192.14.224 4i ifc 0
€€\x1eh€€€€€\x1eP\x1f [€€9k€€€€\x0e€$€5€€€Qx[#<€ӍÇ€I€€iՕ€€€€Ԛ€\x19\x1al€1(%x;\x1cm€€€!V€€D[\x16€(€j€€G€63.192.14.224 /128 63.192.14.224 4b ifc -
€ɐB€\x1d€q€f'1+€ E€\x1fG\x03€y€€€'€N€|€\x10€d€p{1€€./@\x1f¹€€€6L€C3€voPS€€€€Jõ€€p€ /€ܫݯ<6 /128 6363.192.14.226 /128 63.192.14.226 4u ifc 0
man /sys/man
bind -c63.192.14.224 /124 63.192.14.224 4i ifc 0
63.192.14.239 /128 6363.192.14.239 /128 63.192.14.239 4b ifc -
n/other/mail/box /ma63.192.14.224 /128 63.192.14.224 4b ifc -
63.255.255.255 /128 663.255.255.255 /128 63.255.255.255 4b ifc -
s
bind -c /usr/inf63.192.14.226 /128 63.192.14.226 4u ifc 0
255.255.255.255 /128 255.255.255.255 /128 255.255.255.255 4b ifc -
/kfs /n/kfs
moun63.192.14.239 /128 63.192.14.239 4b ifc -
It was a problem with the eipfmt in the kernel. I fixed it by copying in
the libip one. Also, I fixed the formating to not have to be fixed length
strings. For IPv6 the required length was way too long for screens.
Rigorously tested, i.e., I tried it once and the kernel didn't crash.
reply other threads:[~2003-04-04 2:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d7a002f4af281aff27c5b347960b51e3@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--cc=9fans@cse.psu.edu \
/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).