X-Git-Url: https://www.tinc-vpn.org/git/browse?a=blobdiff_plain;f=examples%2Fbridging.mdwn;h=8d4342761f9942781835206d07dde2dc08452660;hb=0e785f06f39116771060269debf80ce9ec249757;hp=ca5e6ec85b016607db18c9440ca42798f665ef25;hpb=7c74a57cd95cfc0358fdd5980d9170ea16751dfb;p=wiki

diff --git a/examples/bridging.mdwn b/examples/bridging.mdwn
index ca5e6ec..8d43427 100644
--- a/examples/bridging.mdwn
+++ b/examples/bridging.mdwn
@@ -84,7 +84,7 @@ required if tinc was replaced with an actual switch or hub.
 
 ### Configuration of tinc
 
-Note that switch' and hub' mode do not utilize the Subnet variable in the host
+Note that switch and hub mode do not utilize the Subnet variable in the host
 files. Instead, any packet received by the bridge interface will be passed to
 the TUN/TAP device for processing. If your tinc instance is running in hub
 mode, all packets are forwarded to the remote tinc instance. In switch mode,
@@ -93,16 +93,15 @@ forwarded to the remote tinc instance.
 
 >     host# cat /etc/tinc/vpn/tinc.conf
 >     Name = segment1
->     Device = /dev/tun
 >     Mode = switch
 >     ConnectTo = segment2
 >     
 >     host# cat /etc/tinc/vpn/tinc-up
 >     #!/bin/sh
 >     
->     ifconfig vpn 0.0.0.0
->     brctl addif bridge vpn
->     ifconfig vpn up
+>     ifconfig $INTERFACE 0.0.0.0
+>     brctl addif bridge $INTERFACE
+>     ifconfig $INTERFACE up
 >     
 >     host# ls /etc/tinc/vpn/hosts
 >     segment1  segment2  ...