Lines Matching refs:to
30 to create tunnel. It does not work in 2.2.0!
32 A: You are right, it does not work. The command written above is split to two commands.
41 Certainly, if you prefer name \verb|tunl1| to \verb|MY-TUNNEL|,
50 to tunnel net 10.0.0.0 via router 193.233.7.65. It does not
53 to 10.0.0.0 via \verb|tunl0| in routing table.
63 not to check for consistency of gateway address.
65 to cheat kernel:
72 Well, if you like such tricks, nobody may prohibit you to use them.
78 Q: In 2.0.36 I used to load \verb|tunnel| device module and \verb|ipip| module.
89 inner packet to outer one. It means that path traversed by tunneled
90 packets to another endpoint is not hidden. If you dislike this, or if you
91 are going to use some routing protocol expecting that packets
98 Q: ... Well, list of things, which 2.0 was able to do finishes.
110 to receive tunneled packets.
133 kinds and gateway is required to be directly reachable via this tunnel,
135 to override this behaviour.
173 \verb|remote <D>| sets remote endpoint of the tunnel to IP
189 Tunnels are divided to two classes: {\bf pointopoint} tunnels, which
191 to this destination, and {\bf NBMA} (i.e. Non-Broadcast Multi-Access) tunnels,
199 some features related to the fact that they work over existing Internet
212 you have to explain to driver, where it should deliver packets to.
213 The only way to make it is to create special routes with gateway
214 address pointing to desired endpoint. F.e.\
218 It is important to use option \verb|onlink|, otherwise
219 kernel will refuse request to create route via gateway not directly
222 with all IPv4 addresses mapped to IPv6 space, so that all IPv4
228 destined to this prefix to 193.233.7.65.
243 \item \verb|dev DEV| --- bind tunnel to device \verb|DEV|, so that
245 not be able to escape to another device, when route to endpoint changes.
267 even do not understand, how it is supposed to work and for what
268 purpose Cisco planned to use it.
276 \verb|i| or \verb|o|. F.e.\ \verb|icsum| orders to accept only
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
330 anyone on the Internet may inject to your network any packets with
332 to design tunnels in the way enforcing maximal route symmetry
333 and to enable reversed path filter (\verb|rp_filter| sysctl option) on
358 This command set translates to:
371 DVMRP exploits IPIP tunnels to route multicasts via Internet.
376 I.e.\ if \verb|mrouted| created some tunnel, it may be used to
388 It is possible to set \verb|remote| for GRE tunnel to a multicast
398 sent to multicast group 224.66.66.66. By default such tunnel starts
399 to resolve both IP and IPv6 addresses via ARP/NDISC, so that
408 and to add required information to ARP tables manually:
412 In this case packets sent to 10.0.0.2 will be encapsulated in GRE
413 and sent to 128.6.190.2. It is possible to facilitate address resolution
414 using methods typical for another NBMA networks f.e.\ to start user
416 to GRE virtual network or ask for information
422 it is strongly recommended to be used with GRE tunnels instead of ugly
432 applies to them. The simplest (and the most useful in practice)
438 will limit tunneled traffic to 128Kbit with maximal burst size of 4K
443 just because they have no queues. Instead, it is better to create classes
444 on real physical interfaces and to map tunneled packets to them.
447 to use option \verb|dev DEV| to bind tunnel to a fixed physical device.
449 and you need to setup corresponding classes only on it.
450 Though you have to pay for this convenience,
456 with some classifier and map them to class \verb|1:ABC|. F.e.\
457 it is easy to make with \verb|rsvp| classifier:
464 If you want to make more detailed classification of sub-flows
466 rooted at \verb|1:ABC| and attach to subroot set of rules parsing