wikiroute

networking recipes

User Tools

Site Tools


ipv6_tunnel_at_home

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
ipv6_tunnel_at_home [2015/04/04 16:41] sameripv6_tunnel_at_home [2015/04/04 18:31] (current) – [1.1- IPv4 Configuration] samer
Line 1: Line 1:
-Start by configuring the Ethernet and the WLAN interfaces on the MR3020 in two different networks:+====== IPv6 Tunnel on OpenWrt ====== 
 + 
 +===== -- Summary===== 
 + 
 +The objective of this platform is to connect your home network to the Internet using an IPv6 tunnel provided by [[ https://www.sixxs.net | sixxs]]. A TP-Link MR3020 router is used as the tunnel endpoint: 
 +  * The Ethernet interface is connected to your home set-top box. 
 +  * The WiFi interface creates a local area network and connects the home equipment. 
 +===== -- IPv4 Configuration===== 
 +Start by configuring Ethernet and WLAN interfaces on the MR3020 in two different IP networks. As the Ethernet interface is connected to the set-top box, it is important to adapt the following configuration to your environment by choosing an appropriate subnet and gateway. The WiFi interface has an address in a subnet of your choice. 
 + 
 +<WRAP center round tip 100%> 
 +Note that in OpenWrt, the configuration uses logical names for interfaces, such as ''wan'' for ''eth0''
 +</WRAP>
  
 <file autoconf /etc/config/network> <file autoconf /etc/config/network>
Line 20: Line 32:
         option ipaddr '192.168.66.1'         option ipaddr '192.168.66.1'
         option netmask '255.255.255.0'         option netmask '255.255.255.0'
-        option ip6addr '2a01:240:fe00:80ab::1/64'+        option ip6addr '2a01:240:xxxx:yyyy::1/64'
 </file> </file>
  
Line 110: Line 122:
         option dest             wan         option dest             wan
 </file> </file>
 +==== -- IPv6 Configuration====
 <code bash> <code bash>
 opkg update && opkg install aiccu radvd opkg update && opkg install aiccu radvd
Line 117: Line 129:
 <code bash> <code bash>
 ip -6 addr add 2a01:240:fe00:80ab::1/64 dev wlan0 ip -6 addr add 2a01:240:fe00:80ab::1/64 dev wlan0
 +</code>
 +
 +<file autoconf /etc/sysctl.conf>
 +net.ipv6.conf.all.forwarding=1
 +</file>
 +
 +<file autoconf /etc/config/radvd>
 +
 +config interface
 + option interface 'wifi'
 + option AdvSendAdvert 1
 + option AdvManagedFlag 0
 + option AdvOtherConfigFlag 0
 + list client ''
 + option ignore 0
 +
 +config prefix
 + option interface 'wifi'
 + # If not specified, a non-link-local prefix of the interface is used
 + list prefix '2a01:240:fe00:80ab::/64'
 + option AdvOnLink 1
 + option AdvAutonomous 1
 + option AdvRouterAddr 0
 + option ignore 0
 +
 +config route
 + option interface 'wifi'
 + list prefix ''
 + option ignore 1
 +
 +config rdnss
 + option interface 'wifi'
 + # If not specified, the link-local address of the interface is used
 + list addr ''
 + option ignore 1
 +
 +config dnssl
 + option interface 'wifi'
 + list suffix ''
 + option ignore 1
 +</file>
 +
 +Create and edit
 +
 +<file autoconf /etc/aiccu.conf>
 +
 +# AICCU Configuration
 +
 +# Login information (defaults: none)
 +username XXXX-SIXXS
 +password XXXX
 +
 +# Protocol and server to use for setting up the tunnel (defaults: none)
 +#protocol <tic|tsp|l2tp>
 +#server <server to use>
 +
 +# Interface names to use (default: aiccu)
 +# ipv6_interface is the name of the interface that will be used as a tunnel interface.
 +# On *BSD the ipv6_interface should be set to gifX (eg gif0) for proto-41 tunnels
 +# or tunX (eg tun0) for AYIYA tunnels.
 +ipv6_interface tun0
 +
 +# The tunnel_id to use (default: none)
 +# (only required when there are multiple tunnels in the list)
 +tunnel_id T23724
 +
 +# Be verbose? (default: false)
 +verbose true
 +
 +# Daemonize? (default: true)
 +# Set to false if you want to see any output
 +# When true output goes to syslog
 +#
 +# WARNING: never run AICCU from DaemonTools or a similar automated
 +# 'restart' tool/script. When AICCU does not start, it has a reason
 +# not to start which it gives on either the stdout or in the (sys)log
 +# file. The TIC server *will* automatically disable accounts which
 +# are detected to run in this mode.
 +#
 +daemonize true
 +
 +# Automatic Login and Tunnel activation?
 +automatic true
 +
 +# Require TLS?
 +# When set to true, if TLS is not supported on the server
 +# the TIC transaction will fail.
 +# When set to false, it will try a starttls, when that is
 +# not supported it will continue.
 +# In any case if AICCU is build with TLS support it will
 +# try to do a 'starttls' to the TIC server to see if that
 +# is supported.
 +requiretls false
 +
 +# PID File
 +#pidfile /var/run/aiccu.pid
 +
 +# Add a default route (default: true)
 +#defaultroute true
 +
 +# Script to run after setting up the interfaces (default: none)
 +#setupscript /usr/local/etc/aiccu-subnets.sh
 +
 +# Make heartbeats (default true)
 +# In general you don't want to turn this off
 +# Of course only applies to AYIYA and heartbeat tunnels not to static ones
 +#makebeats true
 +
 +# Don't configure anything (default: false)
 +#noconfigure true
 +
 +# Behind NAT (default: false)
 +# Notify the user that a NAT-kind network is detected
 +behindnat true
 +
 +# Local IPv4 Override (default: none)
 +# Overrides the IPv4 parameter received from TIC
 +# This allows one to configure a NAT into "DMZ" mode and then
 +# forwarding the proto-41 packets to an internal host.
 +
 +# This is only needed for static proto-41 tunnels!
 +# AYIYA and heartbeat tunnels don't require this.
 +#local_ipv4_override
 +
 +</file>
 +
 +<code bash>
 +aiccu start
 +/etc/init.d/radvd start
 +/etc/init.d/radvd enable
 </code> </code>
ipv6_tunnel_at_home.1428158490.txt.gz · Last modified: 2015/04/04 16:41 by samer