Difference between revisions of "tun/tap driver"
From Noah.org
Jump to navigationJump to searchm |
|||
| Line 19: | Line 19: | ||
# cat /proc/sys/net/ipv4/ip_forward | # cat /proc/sys/net/ipv4/ip_forward | ||
0 | 0 | ||
| + | # sysctl net.ipv4.ip_forward | ||
| + | net.ipv4.ip_forward = 0 | ||
# echo 1 > /proc/sys/net/ipv4/ip_forward | # echo 1 > /proc/sys/net/ipv4/ip_forward | ||
# cat /proc/sys/net/ipv4/ip_forward | # cat /proc/sys/net/ipv4/ip_forward | ||
Revision as of 19:34, 30 January 2013
# ip tuntap del tap0 mode tap # ip tuntap add tun0 mode tun ip tuntap add tap0 mode tap ip link set tap0 up ip addr add 192.168.0.2/24 dev tap0 brctl addbr br0 ip link set br0 up brctl addif br0 eth0 brctl addif br0 tap0
enable routing in Linux
The kernel needs to be told to forward IP packets.
# cat /proc/sys/net/ipv4/ip_forward 0 # sysctl net.ipv4.ip_forward net.ipv4.ip_forward = 0 # echo 1 > /proc/sys/net/ipv4/ip_forward # cat /proc/sys/net/ipv4/ip_forward 1
IPTables needs to be setup to do the actual routing between interfaces.
iptables -A INPUT -i tap0 -j ACCEPT iptables -A INPUT -i br0 -j ACCEPT iptables -A FORWARD -i br0 -j ACCEPT
