aboutsummaryrefslogtreecommitdiffstats
path: root/package/network/config/vti
Commit message (Collapse)AuthorAgeFilesLines
* vti: add vti specific settings as nested json objectHans Dedecker2017-03-212-2/+7
| | | | | | Add vti specific settings ikey and okey as a nested data json object Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* vti: add empty install rules for vtiv4 & vtiv6Alexandru Ardelean2016-12-221-0/+8
| | | | | | Same as for grev4 & grev6 Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* vti: fix kmod dependenciesJohn Crispin2016-02-121-2/+2
| | | | | | Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> SVN-Revision: 48704
* network: add virtual tunnel interface (VTI) supportFelix Fietkau2016-01-172-0/+216
This adds support for configuring VTI interfaces within /etc/config/network. VTI interfaces are used to create IPsec tunnel interfaces. These interfaces may be used for routing and other purposes. Example config: config interface 'vti1' option proto 'vti' option mtu '1500' option tunlink 'wan' option peeraddr '192.168.5.16' option zone 'VPN' option ikey 2 option okey 2 config interface 'vti1_static' option proto 'static' option ifname '@vti1' option ipaddr '192.168.7.2/24' The options ikey and okey correspond to the fwmark value of a ipsec policy. The may be null if you do not want fwmarks. Also peeraddr may be 0.0.0 if you want all ESP packets go through the interface. Example strongswan config: conn vti left=%any leftcert=peer2.test.der leftid=@peer2.test right=192.168.5.16 rightid=@peer3.test leftsubnet=0.0.0.0/0 rightsubnet=0.0.0.0/0 mark=2 auto=route Signed-off-by: André Valentin <avalentin@marcant.net> SVN-Revision: 48274