Difference between revisions of "Bering-uClibc 4.x - User Guide - IPv6 Networking - External Network Connections"
Davidmbrooke (Talk | contribs) (Added brief summary for SixXS) |
(→SixXS) |
||
Line 15: | Line 15: | ||
==Tunnel from IPv6 Tunnelbroker== | ==Tunnel from IPv6 Tunnelbroker== | ||
===SixXS=== | ===SixXS=== | ||
− | If you use [http://www.sixxs.net/ SixXS] as your IPv6 tunnelbroker the procedure to configure [[Bering-uClibc 4.x]] is as follows: | + | If you use [http://www.sixxs.net/ SixXS] as your IPv6 tunnelbroker, you'll want to install the <code class="filename">aiccu.lrp</code> Package, which provides AICCU, the Automatic IPv6 Connectivity Client Utility. |
− | * Make sure you have the <tt>tun</tt> kernel Module loaded. Note that this relies on the <tt>crc32</tt> kernel Module. | + | |
+ | AICCU makes it easy for users to get IPv6 connectivity. After having requested an account, tunnel and optionally a subnet, AICCU can be used to automatically configure the tunnel. AICCU supports TIC (Tunnel Information & Control protocol), which it uses for retrieving the tunnel configuration information, AYIYA, which allows tunnels to be created even behind firewalls and NAT's. | ||
+ | |||
+ | The procedure to configure [[Bering-uClibc 4.x]] is as follows: | ||
+ | * Make sure you have the <tt>tun</tt> kernel Module loaded. Note that this relies on the <tt>crc32</tt> kernel Module, which should be automatically loaded in most setups anyway. | ||
* Configure Shorewall to accept the SixXS tunnel traffic. Add the following to <code class="filename">/etc/shorewall/rules</code>: | * Configure Shorewall to accept the SixXS tunnel traffic. Add the following to <code class="filename">/etc/shorewall/rules</code>: | ||
SixXS(ACCEPT) fw net | SixXS(ACCEPT) fw net | ||
Line 30: | Line 34: | ||
* In the event of problems you may find the "<tt>test</tt>" mode of the "<tt>aiccu</tt>" command useful. | * In the event of problems you may find the "<tt>test</tt>" mode of the "<tt>aiccu</tt>" command useful. | ||
+ | Although AICCU supports tunnels via non-static IP-adresses, we've found that tunnels via DSL-providers (like T-DSL connections in Germany), that change the ip address in an 24-hour-intervall, doesn't work reliably. | ||
+ | A workaround is to add the script below, named as <code class="filename">0aiccu</code>, to <code class=filename">/etc/ppp/ip-up-d</code>. It restarts <code class="filename">aiccu</code> after ppp has reestablished the pppoe connection. | ||
+ | |||
+ | #!/bin/sh | ||
+ | if pidof aiccu | ||
+ | then /etc/init.d/aiccu stop | ||
+ | fi | ||
+ | while pidof aiccu ; do | ||
+ | sleep 15; | ||
+ | pidof aiccu; | ||
+ | done | ||
+ | /etc/init.d/aiccu start | ||
===Hurricane Electric=== | ===Hurricane Electric=== |
Revision as of 22:14, 31 December 2010
IPv6 Networking - External Network Connections | ||
---|---|---|
Bering-uClibc 4.x - User Guide | Next |
Native IPv6
TODO
Tunnel from IPv6 Tunnelbroker
SixXS
If you use SixXS as your IPv6 tunnelbroker, you'll want to install the aiccu.lrp
Package, which provides AICCU, the Automatic IPv6 Connectivity Client Utility.
AICCU makes it easy for users to get IPv6 connectivity. After having requested an account, tunnel and optionally a subnet, AICCU can be used to automatically configure the tunnel. AICCU supports TIC (Tunnel Information & Control protocol), which it uses for retrieving the tunnel configuration information, AYIYA, which allows tunnels to be created even behind firewalls and NAT's.
The procedure to configure Bering-uClibc 4.x is as follows:
- Make sure you have the tun kernel Module loaded. Note that this relies on the crc32 kernel Module, which should be automatically loaded in most setups anyway.
- Configure Shorewall to accept the SixXS tunnel traffic. Add the following to
/etc/shorewall/rules
:
SixXS(ACCEPT) fw net
- Install the
aiccu.lrp
Package and configure it using lrcfg.- Specify your own username and password.
- Specify the relevant protocol and server. For example:
protocol tic server tic.sixxs.net
- Start the aiccu daemon:
svi aiccu start
- Check for error messages in
/var/log/syslog
- If all is well, you should have a new network interface called "sixxs" which is effectively the IPv6 equivalent of your external IPv4 interface (e.g. eth0 or ppp0).
- In the event of problems you may find the "test" mode of the "aiccu" command useful.
Although AICCU supports tunnels via non-static IP-adresses, we've found that tunnels via DSL-providers (like T-DSL connections in Germany), that change the ip address in an 24-hour-intervall, doesn't work reliably.
A workaround is to add the script below, named as 0aiccu
, to /etc/ppp/ip-up-d
. It restarts aiccu
after ppp has reestablished the pppoe connection.
#!/bin/sh if pidof aiccu then /etc/init.d/aiccu stop fi while pidof aiccu ; do sleep 15; pidof aiccu; done /etc/init.d/aiccu start
Hurricane Electric
TODO
Up | Next |