routerbox/utils/he_ipv6/example.tunnelbroker.xml

81 lines
3.8 KiB
XML
Raw Normal View History

2020-05-11 16:23:34 -04:00
<?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">
2020-05-12 01:21:52 -04:00
<!--
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/
-->
2020-05-11 16:23:34 -04:00
<creds>
2020-05-12 01:21:52 -04:00
<!--
Credentials are kept separate from tunnel configuration because you can have multiple (up to 5) tunnels per user.
You can find the updateKey in the "Advanced" tab of your tunnel's configuration on your tunnelbroker.net panel.
2020-05-12 01:21:52 -04:00
-->
2020-05-11 16:23:34 -04:00
<cred id="ipv6user">
<user>ipv6user</user>
<password>someSecretPassword</password>
2020-05-11 16:23:34 -04:00
<updateKey>xXxXxXxXxXxXxXXX</updateKey>
</cred>
<cred id="anotheruser">
<user>someotheruser</user>
<password>anotherPassword</password>
2020-05-11 16:23:34 -04:00
<updateKey>0000000000000000</updateKey>
</cred>
</creds>
<tunnels>
2020-05-12 01:21:52 -04:00
<!--
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 panel, clicking on the tunnel you wish to use, and
2020-05-12 01:21:52 -04:00
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".
-->
2020-05-11 16:23:34 -04:00
<tunnel id="12345" creds="ipv6user">
2020-05-12 01:21:52 -04:00
<!--
2020-05-14 04:05:32 -04:00
Where to assign your allocations. The default allocation prefix is a /64 (prefix="64"), since that's what SLAAC
recommends.
It has two optional attributes:
* "radvd" - a boolean; if true, /etc/radvd.conf will be automatically.
* "radvdDns" - a boolean, only used if radvd is true; if true, will specify the server's IP as an RDSS.
generated and restarted.
2020-05-12 01:21:52 -04:00
-->
<assignments radvd="true" radvdDns="true">
<!--
Each assignment has the following required attributes:
2020-05-14 04:05:32 -04:00
* "prefix" - the size of the subnet to assign to an interface, "64" (/64) by default since that's what SLAAC
recommends. Note that if you use your /64 allocation and don't specify a longer prefix, you can
only have one assignment for that allocation.
* "alloc" - this should match the prefix of the allocation. Hurricane Electric only allows you one /64 and,
optionally, one /48. Use "alloc" to reference which allocation you want to use. Uses "64" (/64)
by default.
* "iface" - which network interface on this machine the allocation should be added to.
Make sure you don't exceed your allocation size! (A /48 has 65536 /64s in it.)
The interface will be assigned :1 (the first host in the subnet) as well, so it is recommended that you do not
2020-05-14 04:05:32 -04:00
assign a /128 prefix.
-->
2020-05-14 04:05:32 -04:00
<assign prefix="64" alloc="64" iface="eth0"/>
<assign prefix="64" alloc="48" iface="eth0"/>
<assign prefix="64" alloc="48" iface="eth1"/>
<assign prefix="64" alloc="48" iface="eth2"/>
</assignments>
2020-05-11 16:23:34 -04:00
</tunnel>
2020-05-12 01:21:52 -04:00
<!--
And you can, of course, specify multiple tunnels.
-->
2020-05-14 04:05:32 -04:00
<tunnel id="54321" creds="anotheruser">
<assignments>
2020-05-14 04:05:32 -04:00
<!--
Uses the default prefix of /64 from your standard /64 allocation from Hurricane Electric.
Most users probably want this unless they're running an IPv6 router.
-->
<assign iface="eth0"/>
</assignments>
2020-05-11 16:23:34 -04:00
</tunnel>
</tunnels>
</heIPv6>