Revision as of 12:29, 31 December 2012 (view source) CecilWard (talk \| contribs) m (→‎Update your subnet to include:: clarify mtu) ← Older edit		Revision as of 12:34, 31 December 2012 (view source) CecilWard (talk \| contribs) m (Caps) Newer edit →
==Create a route:== <syntaxhighlight> <route ip="::/0" gateway="81.187.81.6" comment="IPv6 Default route using IPv4 ~~Tunnel~~tunnel"/> </syntaxhighlight> Here, 81.187.81.187 is the AAISP side ~~Tunnel~~tunnel endpoint, and we've created an IPv6 default route to it - if you are using someone else for the ~~Tunnel~~tunnel, then use their endpoint. ==Update your subnet to include:== The smaller MTU is required due to the IPv6 packets being placed inside IPv4 packets. Once saved, machines on your LAN should be given IPv6 addresses, and they will use the FireBrick as their IPv6 gateway, which in turn will use the ~~Tunnel~~tunnel endpoint. ==Add a firewall rule to allow the tunnel in== ==Hurricane Electric tunnelbroker.net tunnel== It's also really easy to set up an IPv6 tunnel from http://tunnelbroker.net if you are using a FB2700 on an ISP which doesn't already support IPv6. If the details for your tunnel on your control panel say your ~~Server~~server IPv4 address is 192.0.2.26 and your ~~Client~~client IPv6 is 2001:DB8:ABCD:123E::2 then you would put the following in your config: <syntaxhighlight>

FireBrick IPv6 Tunnel (view source)