Lines Matching refs:verb

12 \verb|kuznet@ms2.inr.ac.ru| \\
36 will create tunnel device with name \verb|MY-TUNNEL|. Now you may configure
41 Certainly, if you prefer name \verb|tunl1| to \verb|MY-TUNNEL|,
51 work in 2.2.0! Moreover, \verb|route| prints a funny error sort of
53 to 10.0.0.0 via \verb|tunl0| in routing table.
62 Note keyword \verb|onlink|, it is the magic key that orders kernel
74 that between \verb|route add| and \verb|route del| host 193.233.7.65 is
78 Q: In 2.0.36 I used to load \verb|tunnel| device module and \verb|ipip| module.
79 I cannot find any \verb|tunnel| in 2.2!
81 A: Linux-2.2 has single module \verb|ipip| for both directions of tunneling
85 Q: \verb|traceroute| does not work over tunnel! Well, stop... It works,
88 A: Yes. By default tunnel driver copies \verb|ttl| value from
94 tunnel loops, you may append option \verb|ttl 64|, when creating tunnel
95 with \verb|ip tunnel add|.
107 	and got set of 4 devices \verb|tunl0| ... \verb|tunl3| or,
109 	for each new tunnel. Also, module \verb|ipip| was necessary
112       {\bf 2.2} has {\em one\/} module \verb|ipip|. Loading it you get base
113 	tunnel device \verb|tunl0| and another tunnels may be created with command
114 	\verb|ip tunnel add|. These new devices may have arbitrary names.
118 	the command \verb|ifconfig| ... \verb|pointopoint A|.
124 	rather than via Internet. Actual tunnel endpoint address \verb|A|
125 	should be set with \verb|ip tunnel add ... remote A|.
134 	rather than via Internet. You still may use \verb|ip route add ... onlink|
161 This command creates new tunnel device with name \verb|<NAME>|.
162 The \verb|<NAME>| is an arbitrary string. Particularly,
163 it may be even \verb|eth0|. The rest of parameters set
169 \verb|mode <MODE>| sets tunnel mode. Three modes are available now
170 	\verb|ipip|, \verb|sit| and \verb|gre|.
173 \verb|remote <D>| sets remote endpoint of the tunnel to IP
174 	address \verb|<D>|.
176 \verb|local <S>| sets fixed local address for tunneled
183 Both \verb|remote| and \verb|local| may be omitted. In this case we
185 have the same \verb|remote| and \verb|local|. Particularly it means
190 have some not wildcard \verb|remote| address and deliver all the packets
192 which have no \verb|remote|. Particularly, base devices (f.e.\ \verb|tunl0|)
193 are NBMA, because they have neither \verb|remote| nor
194 \verb|local| addresses.
208 of another devices. You should set a protocol address with \verb|ifconfig|
209 and add routes with \verb|route| utility.
218 It is important to use option \verb|onlink|, otherwise
220 reachable over device \verb|tunl0|. With IPv6 the situation is much simpler:
221 when you start device \verb|sit0|, it automatically configures itself
223 Internet is {\em really reachable} via \verb|sit0|! Excellent, the command
227 will route \verb|3FFE::/16| via \verb|sit0|, sending all the packets
232 Command \verb|ip tunnel add| has several additional options.
235 \item \verb|ttl N| --- set fixed TTL \verb|N| on tunneled packets.
236 	\verb|N| is number in the range 1--255. 0 is special value,
238 		Default value is: \verb|inherit|.
240 \item \verb|tos T| --- set fixed tos \verb|T| on tunneled packets.
241 		Default value is: \verb|inherit|.
243 \item \verb|dev DEV| --- bind tunnel to device \verb|DEV|, so that
247 \item \verb|nopmtudisc| --- disable Path MTU Discovery on this tunnel.
253 \verb|ipip| and \verb|sit| tunnels have no more options. \verb|gre|
258 \item \verb|key K| --- use keyed GRE with key \verb|K|. \verb|K| is
261 \item \verb|csum| --- checksum tunneled packets.
263 \item \verb|seq| --- serialize packets.
276 \verb|i| or \verb|o|. F.e.\ \verb|icsum| orders to accept only
277 packets with correct checksum and \verb|ocsum| means, that
280 Command \verb|ip tunnel add| is not the only operation,
295 where \verb|Cisco| is name of tunnel device. Command
299 destroys tunnel \verb|Cisco|. And, finally,
313 as soon as you loaded module \verb|ipip|. 2.2 tries to select the best
315 received \verb|ipip| packet from host \verb|D| destined to our
316 local address \verb|S|, kernel searches for matching tunnels
320 1 & \verb|remote| is \verb|D| and \verb|local| is \verb|S| \\
321 2 & \verb|remote| is \verb|D| and \verb|local| is wildcard \\
322 3 & \verb|remote| is wildcard and \verb|local| is \verb|S| \\
323 4 & \verb|tunl0|
326 If tunnel exists, but it is not in \verb|UP| state, the tunnel is ignored.
327 Note, that if \verb|tunl0| is \verb|UP| it receives all the IPIP packets,
333 and to enable reversed path filter (\verb|rp_filter| sysctl option) on
336 \item In 2.2 you can monitor and debug tunnels with \verb|tcpdump|.
337 F.e.\ \verb|tcpdump| \verb|-i Cisco| \verb|-nvv| will dump packets,
338 which kernel output, via tunnel \verb|Cisco| and the packets received on it
372 \verb|mrouted| creates
375 tunnels, created in this way, and tunnels created by \verb|ip tunnel|.
376 I.e.\ if \verb|mrouted| created some tunnel, it may be used to
379 it will be reused by \verb|mrouted|, if it requests DVMRP
388 It is possible to set \verb|remote| for GRE tunnel to a multicast
415 level \verb|arpd| daemon, which will maintain database of hosts attached
423 hack with NBMA mode and \verb|onlink| modifier. Unfortunately,
447 to use option \verb|dev DEV| to bind tunnel to a fixed physical device.
453 Suppose that CBQ class \verb|1:ABC| has been created on device \verb|eth0| 
454 specially for tunnel \verb|Cisco| with endpoints \verb|S| and \verb|D|.
455 Now you can select IPIP packets with addresses \verb|S| and \verb|D|
456 with some classifier and map them to class \verb|1:ABC|. F.e.\ 
457 it is easy to make with \verb|rsvp| classifier:
466 rooted at \verb|1:ABC| and attach to subroot set of rules parsing