aboutsummaryrefslogtreecommitdiffstats
path: root/package/6rd
Commit message (Collapse)AuthorAgeFilesLines
* packages: sort network related packages into package/network/Felix Fietkau2012-10-104-266/+0
| | | | SVN-Revision: 33688
* 6rd: missing config option `ipaddr`.Jo-Philipp Wich2012-08-111-0/+1
| | | | | | | | This option is necessary when configuring 6rd behind NAT. Signed-off-by: Stéphan Kochen <stephan@kochen.nl> SVN-Revision: 33123
* 6rd: apply the same simplifications done in 6to4 and 6in4Jo-Philipp Wich2012-06-183-41/+6
| | | | SVN-Revision: 32432
* Add new package for configuring 6rd tunnels.Jo-Philipp Wich2012-06-185-0/+300
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> SVN-Revision: 32431