X-Git-Url: https://tinc-vpn.org/git/browse?p=tinc;a=blobdiff_plain;f=doc%2Ftinc.texi;h=dd7bc6250013289f6a43a54b1900f2da10c9447b;hp=4e99ba87872afa9403441c47ca826fb2c3834910;hb=74653beb5bc510e60579058ee15c0f66350f5137;hpb=ee64b8ef33b709fabfc1ed56762d5f52fc026e52 diff --git a/doc/tinc.texi b/doc/tinc.texi index 4e99ba87..dd7bc625 100644 --- a/doc/tinc.texi +++ b/doc/tinc.texi @@ -819,14 +819,14 @@ to start with an Ethernet header. @end table @cindex DirectOnly -@item DirectOnly = (no) +@item DirectOnly = (no) [experimental] When this option is enabled, packets that cannot be sent directly to the destination node, but which would have to be forwarded by an intermediate node, are dropped instead. When combined with the IndirectData option, packets for nodes for which we do not have a meta connection with are also dropped. @cindex Forwarding -@item Forwarding = (internal) +@item Forwarding = (internal) [experimental] This option selects the way indirect packets are forwarded. @table @asis @@ -1348,7 +1348,7 @@ Address = 1.2.3.4 Note that the IP addresses of eth0 and tap0 are the same. This is quite possible, if you make sure that the netmasks of the interfaces are different. -It is in fact recommended to give give both real internal network interfaces and tap interfaces the same IP address, +It is in fact recommended to give both real internal network interfaces and tap interfaces the same IP address, since that will make things a lot easier to remember and set up.