1 .\" $NetBSD: strip.4,v 1.13 2004/12/05 13:24:10 peter Exp $
3 .\" Copyright 1996 The Board of Trustees of The Leland Stanford
4 .\" Junior University. All Rights Reserved.
6 .\" Author: Jonathan Stone
8 .\" Permission to use, copy, modify, and distribute this
9 .\" software and its documentation for any purpose and without
10 .\" fee is hereby granted, provided that the above copyright
11 .\" notice and the above authorship notice appear in all copies.
12 .\" Stanford University makes no representations about the suitability
13 .\" of this software for any purpose. It is provided "as is" without
14 .\" express or implied warranty.
20 .Nd Metricom Ricochet packet radio wireless network device
22 .Cd pseudo-device strip
26 driver takes outbound network packets, encapsulates them using the
29 framing, and sends the packets out an
35 Packets arriving from the packet radio via the serial link are decapsulated
36 and then passed up to the local host's networking stack.
46 interfaces can be created by using the
52 interface is a pseudo-device driver for the
55 packet radio, operating in peer-to-peer packet mode.
60 driver is very much like the
62 SLIP pseudo-device driver.
65 device is attached to a tty line with
67 Once attached, the interface is configured via
69 The major difference between the
71 SLIP pseudo-device driver and the
73 driver is that SLIP works only between two hosts over
74 a dedicated point-to-point connection.
78 sends packets to a frequency-hopping packet radio, which can address
82 packet radio, rather than just to a single host at the other end
83 of a point-to-point line.
86 pseudo-device is usually sufficient for any kernel.
90 interface is rather like an
93 Packets are individually addressed, and subsequent packets can
94 be sent independently to different MAC addresses.
97 framing and MAC addressing are not in any way compatible with
99 Broadcast or multicast to more than one packet radio is not possible,
100 due to the independent frequency-hopping operation of the packet radios.
105 are not supported on the
111 implements a multiple-access, non-broadcast device, accessed via
112 an RS-232 serial line, using a proprietary packet framing scheme.
121 packet radio addresses using statically configured entries in the
122 normal routing table.
125 addresses of peer packet radios to the MAC-level addresses.
126 The exact syntax of this mapping and an example are discussed below.
127 The Internet Assigned Numbers Authority
131 type code for use with STRIP.
132 A future version of this driver will support
136 address of reachable peer packet radios dynamically.
137 .Sh ADDRESS CONFIGURATION
138 This version of the STRIP driver requires static pre-configuration of
141 addresses to packet radio MAC addresses.
144 command should be used to bind a peer STRIP host's packet radio
146 address to the peer's link-level packet radio address.
148 Radio addresses are encoded using the hex equivalent of the packet
152 For example, the following route command will configure a routing
153 entry to a packet radio with a MAC address of 1234-5678, and an
155 address 10.11.12.13, reachable via the
159 .Bd -literal -offset indent
160 .Ic route add -host 10.11.12.13 -link strip0:1:2:3:4:5:6:7:8
163 Generalising from this example to other
165 addresses and to other 8-digit MAC addresses should be clear.
166 .Sh RADIO CONFIGURATION
170 packet radios can auto-baud at speeds up to 38.4K baud.
171 At higher speeds -- 57600 or 115200 -- the packet radio cannot autobaud.
172 When running at high speeds, the packet radio's serial port should be
173 manually configured to permanently run at the desired speed.
174 Use a terminal emulator and the Hayes command
176 to set the serial baudrate to the specified number (or 0 for autobaud).
179 will then save the current packet radio state in non-volatile memory.
183 packet radios can operate in either
185 mode or in packet mode (i.e.
189 driver automatically detects if the packet radio has fallen out of
191 and resets it back into
193 if the baud rate was set correctly by
205 was originally developed for the
207 kernel by Stuart Cheshire of Stanford's Operating Systems and
208 Networking group, as part of Mary Baker's MosquitoNet
209 .Sy http://mosquitonet.stanford.edu/mosquitonet.html
216 by Jonathan Stone at Stanford's Distributed Systems Group and first
227 have been defined, but are not yet implemented in this driver.
230 has not been widely tested on a variety of lower-level serial drivers.
232 The detection and resetting of packet radios that crash out of
234 does not always work in this version of the driver.
235 One workaround is to kill the
241 interface down, and then start a new slattach and rerun ifconfig
242 to enable the interface again.