Welcome to Hurricane Electric's Tunnelbroker.net forums!
Started by bearice, June 23, 2010, 10:52:13 AM
Quotepptpsetup --create IPv6VPN --server tserv3.fmt2.ipv6.he.net --username bearice%63106 --password ***
persistmaxfail 0pty "pptp tserv3.fmt2.ipv6.he.net --nolaunchpppd"locknoauthnobsdcompnodeflatename bearice%63106remotename IPv6VPNipparam IPv6VPNupdetach
auto he-vpniface he-vpn inet ppp provider IPv6VPNauto he-ipv6iface he-ipv6 inet6 v4tunnel endpoint 220.127.116.11 local 18.104.22.168 address 2001:470:1f04:cab::2 netmask 64 gateway 2001:470:1f04:cab::1 mtu 1420 ttl 255
QuoteBoth the PPTP server and the 6in4 server have the same IPv4 address, Since routing normally only pays attention to destination addresses, and because the PPTP software puts a host route into the main routing table for the HE server so that the PPTP traffic doesn't try to use the ppp0 interface itself, a "special case" route is put in so that when the source IPv4 matches the PPTP assigned IP, it uses a different routing tabled (called "pptp" in this case), which has the default route pointing through the ppp0 interface. This way, "normal" traffic uses your standard default route, and traffic originating from the PPTP IPv4 (such as your 6in4 tunnel's traffic) takes the PPTP tunnel.
echo "1 pptp" >> /etc/iproute2/rt_tables
#!/bin/sh -eip route add default dev $PPP_IFACE table pptpip rule add from $PPP_LOCAL table pptpexit 0
#!/bin/sh -eip route del default dev $PPP_IFACE table pptpip rule del from $PPP_LOCAL table pptpexit 0