From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <1c2da8b76f38d36af39b42c360a59358@terzarima.net> To: 9fans@cse.psu.edu Subject: Re: [9fans] first ping From: Charles Forsyth Date: Wed, 16 May 2007 08:46:33 +0100 In-Reply-To: <13426df10705151708i4e295464ib7e527c8b61b2ad2@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 684d234c-ead2-11e9-9d60-3106f5b1d025 >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.