Commit Graph

3 Commits (830413bd2e4bd523aea6ede5bd0ae50ffbf868c2)

Author SHA1 Message Date
Jo-Philipp Wich 23fdfa09c3 6rd: missing config option `ipaddr`.
This option is necessary when configuring 6rd behind NAT.

Signed-off-by: Stéphan Kochen <stephan@kochen.nl>

git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33123 3c298f89-4303-0410-b956-a3cf2f4a3e73
2012-08-11 00:25:23 +00:00
Jo-Philipp Wich f7802d7314 [package] 6rd: apply the same simplifications done in 6to4 and 6in4
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32432 3c298f89-4303-0410-b956-a3cf2f4a3e73
2012-06-18 23:08:20 +00:00
Jo-Philipp Wich d1c7ec88b3 Add new package for configuring 6rd tunnels.
This patch adds support for manually configuring 6rd tunnels. It depends on
the netifd patches I sent earlier, which add 6rd support.

A basic interface configuration looks like:

    config interface 'wan6'
      option proto '6rd'
      option peeraddr '192.0.2.1'
      option ip6prefix '2123::'
      option ip6prefixlen '16'
      option ip4prefixlen '0'

Where ip4prefixlen is optional and actually defaults to 0, which would use all
bits of the IPv4 in the calculated IPv6 subnet.

I believe it should be possible to configure a regular 6to4 tunnel using this,
and that we may want to merge the two eventually, but there are some larger

differences between the two at the moment:

 - 6rd addresses can be more difficult to calculate. My ISP, for example, has
   a setup with a v6 mask of 43 bits, and a v4 mask of 19.

 - 6to4 has support for configuring radvd. This is something we want, of
   course, but it seems best to deal with this in a separate patch.

Just creating a new package looked like the quickest way to get this in.

This work is based on the 6in4 package, and work by Stijn Tintel.

Signed-off-by: Stéphan Kochen <stephan@kochen.nl>

git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32431 3c298f89-4303-0410-b956-a3cf2f4a3e73
2012-06-18 23:08:18 +00:00