Lines Matching refs:tunnel
30 to create tunnel. It does not work in 2.2.0!
34 ip tunnel add MY-TUNNEL mode ipip remote 193.233.7.65
36 will create tunnel device with name \verb|MY-TUNNEL|. Now you may configure
50 to tunnel net 10.0.0.0 via router 193.233.7.65. It does not
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!
82 and for all IPIP tunnel devices.
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|.
106 \item {\bf In 2.0} you could compile tunnel device into kernel
109 for each new tunnel. Also, module \verb|ipip| was necessary
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.
117 \item {\bf In 2.0} you set remote tunnel endpoint address with
121 the interfaces, namely it sets not tunnel endpoint,
123 via this tunnel,
124 rather than via Internet. Actual tunnel endpoint address \verb|A|
125 should be set with \verb|ip tunnel add ... remote A|.
127 \item {\bf In 2.0} you create tunnel routes with the command:
133 kinds and gateway is required to be directly reachable via this tunnel,
158 ip tunnel add <NAME> mode <MODE> [ local <S> ] [ remote <D> ]
161 This command creates new tunnel device with name \verb|<NAME>|.
164 different tunnel characteristics.
169 \verb|mode <MODE>| sets tunnel mode. Three modes are available now
173 \verb|remote <D>| sets remote endpoint of the tunnel to IP
186 that base device or fallback tunnel cannot be replicated.\footnote{
197 After tunnel device is created you should configure it as you did
202 tunnel setup will result in formation of tunnel loops,
211 NBMA tunnels are different. To route something via NBMA tunnel
232 Command \verb|ip tunnel add| has several additional options.
243 \item \verb|dev DEV| --- bind tunnel to device \verb|DEV|, so that
247 \item \verb|nopmtudisc| --- disable Path MTU Discovery on this tunnel.
280 Command \verb|ip tunnel add| is not the only operation,
284 ip tunnel help
289 ip tunnel ls
293 ip -s tunnel ls Cisco
295 where \verb|Cisco| is name of tunnel device. Command
297 ip tunnel del Cisco
299 destroys tunnel \verb|Cisco|. And, finally,
301 ip tunnel change Cisco mode sit local ME remote HE ttl 32
314 tunnel device and packet looks as received on this. F.e.\ if host
326 If tunnel exists, but it is not in \verb|UP| state, the tunnel is ignored.
334 tunnel devices.
338 which kernel output, via tunnel \verb|Cisco| and the packets received on it
352 tunnel mode gre ip
353 tunnel source 10.10.14.1
354 tunnel destination 10.10.13.2
361 ip tunnel add Tunnel0 \
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
378 And vice versa, if administrator has already created a tunnel,
380 tunnel with the same local and remote addresses.
382 Do not wonder, if your manually configured tunnel is
388 It is possible to set \verb|remote| for GRE tunnel to a multicast
389 address. Such tunnel becomes {\bf broadcast} tunnel (though word
390 tunnel is not quite appropriate in this case, it is rather virtual network).
392 ip tunnel add Universe local 193.233.7.65 \
397 This tunnel is true broadcast network and broadcast packets are
398 sent to multicast group 224.66.66.66. By default such tunnel starts
403 but not fatal flaw. The tunnel becomes NBMA rather than broadcast network.
433 example is limiting tunnel bandwidth. The following command:
447 to use option \verb|dev DEV| to bind tunnel to a fixed physical device.
451 if routing will change, your tunnel will fail.
454 specially for tunnel \verb|Cisco| with endpoints \verb|S| and \verb|D|.
465 transmitted via tunnel, you can build CBQ subtree,