From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] first ping
Date: Wed, 16 May 2007 08:46:33 +0100 [thread overview]
Message-ID: <1c2da8b76f38d36af39b42c360a59358@terzarima.net> (raw)
In-Reply-To: <13426df10705151708i4e295464ib7e527c8b61b2ad2@mail.gmail.com>
>echo bind treenet /dev/vc0 ip 12.0.0.2 255.255.255.255 > /net/ipifc/clone
>echo add 12.0.0.2 255.255.255.255 12.0.0.1 > /net/ipifc/1/ctl
yes, sorry, it turns out for my funny device i'd been using something closer to
{echo bind medium device; echo add ip-parameters...} >/net/ipifc/clone
which explains why the text "ip" ... things didn't produce an error earlier;
as jmk says they are interpreted by the medium's bind. makes sense.
> So I am adding host links for now, but I feel I ought to be able to do
> this via commands to /net/iproute.
adding the addresses to the interface by writing to the ctl file for the ipifc interface is right.
routes (shared by all interfaces on the stack) are added by writing to /net/iproute
echo add target mask gateway >/net/iproute
so
echo add 0 0 1.2.3.4 >/net/iproute
sets the default route ipgw to 1.2.3.4
in order for incoming packets not for the current node
to be forwarded by a given interface you would use
echo iprouting 1 >/net/ipifc/NNN/ctl
BUT in this case, since every node is receiving every packet, you probably
don't really want to do that, and probably don't need it. without it,
packets not for the current node are discarded, which seems right.
next prev parent reply other threads:[~2007-05-16 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 0:08 ron minnich
2007-05-16 7:46 ` Charles Forsyth [this message]
2007-05-16 14:49 ` Eric Van Hensbergen
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=1c2da8b76f38d36af39b42c360a59358@terzarima.net \
--to=forsyth@terzarima.net \
--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).