86 lines
3.3 KiB
XML
86 lines
3.3 KiB
XML
<?xml version="1.0" encoding="UTF-8" ?>
|
|
<heIPv6 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
|
|
xmlns="https://tunnelbroker.net/"
|
|
xsi:schemaLocation="https://tunnelbroker.net/ http://schema.xml.r00t2.io/projects/he_ipv6.xsd">
|
|
<!--
|
|
This is a sample XML configuration file to use with he_ipv6.py.
|
|
If you do not yet have an IPv6 Tunnelbroker.net allocation, you can get one (for free!) at:
|
|
https://www.tunnelbroker.net/tunnel_detail.php?tid=584532
|
|
I highly recommend their (free) certification as well if you're brand-new to IPv6:
|
|
https://ipv6.he.net/certification/
|
|
-->
|
|
<creds>
|
|
<!--
|
|
Credentials are kept separate from tunnel configuration because you can have multiple (up to 5) tunnels per user.
|
|
The updateKey is *not* your password! You can find it in the "Advanced" tab of your tunnel's configuration on
|
|
your tunnelbroker.net panel.
|
|
-->
|
|
<cred id="ipv6user">
|
|
<user>ipv6user</user>
|
|
<updateKey>xXxXxXxXxXxXxXXX</updateKey>
|
|
</cred>
|
|
<cred id="anotheruser">
|
|
<user>someotheruser</user>
|
|
<updateKey>0000000000000000</updateKey>
|
|
</cred>
|
|
</creds>
|
|
<tunnels>
|
|
<!--
|
|
Each tunnel MUST have an "id" and a "creds" attribute. The "creds" attribute should reference an "id" of a
|
|
creds/cred object.
|
|
The tunnel ID can be found by logging into your tunnelbroker.net pannel, clicking on the tunnel you wish to use, and
|
|
looking at the URL in your browser.
|
|
It is in the format of https://www.tunnelbroker.net/tunnel_detail.php?tid=[TUNNEL ID]
|
|
So if it takes you to e.g. https://www.tunnelbroker.net/tunnel_detail.php?tid=12345, your tunnel ID would
|
|
be "12345".
|
|
The below directives give you a Section and Value Name. This refers to the tunnelbroker.net panel page for the
|
|
specific tunnel you're configuring. e.g. To use the above example, this information is found at
|
|
https://www.tunnelbroker.net/tunnel_detail.php?tid=12345
|
|
-->
|
|
<tunnel id="12345" creds="ipv6user">
|
|
<!--
|
|
The "server" element is the remote SIT endpoint.
|
|
Section: IPv6 Tunnel Endpoints
|
|
Value Name: Server IPv4 Address
|
|
-->
|
|
<server>192.0.2.1</server>
|
|
<!--
|
|
Allocations that are handed to your tunnel.
|
|
-->
|
|
<!--
|
|
Section: Routed IPv6 Prefixes
|
|
-->
|
|
<allocs>
|
|
<!--
|
|
Each alloc has (in addition to a "prefix" attribute) an "iface" attribute. This is the network interface on
|
|
this machine that the allocation should be added to.
|
|
Value Name: Routed /64
|
|
-->
|
|
<alloc prefix="64" iface="eth0">2001:DB8:1:2::</alloc>
|
|
<!--
|
|
You may not have a /48 as it's opt-in.
|
|
Value Name: Routed /48
|
|
-->
|
|
<alloc prefix="48" iface="eth0">2001:DB8:2::</alloc>
|
|
</allocs>
|
|
<!--
|
|
The "client" element is the local SIT endpoint.
|
|
Section: IPv6 Tunnel Endpoints
|
|
Value Name: Client IPv6 Address
|
|
-->
|
|
<client prefix="64">2001:DB8:3::2</client>
|
|
</tunnel>
|
|
<!--
|
|
And you can, of course, specify multiple tunnels.
|
|
-->
|
|
<tunnel id="54321" creds="ipv6user">
|
|
<server>192.0.2.1</server>
|
|
<allocs>
|
|
<alloc prefix="64" iface="eth1">2001:DB8:4:2:</alloc>
|
|
<alloc prefix="48" iface="eth1">2001:DB8:5::</alloc>
|
|
</allocs>
|
|
<client prefix="64">2001:DB8:6::2</client>
|
|
</tunnel>
|
|
</tunnels>
|
|
</heIPv6>
|