aboutsummaryrefslogtreecommitdiffstats
path: root/package/network/config/gre/Makefile
Commit message (Collapse)AuthorAgeFilesLines
* gre: add gre specific settings as nested json objectHans Dedecker2017-03-211-1/+1
| | | | | | | Add gre specific settings ikey, okey, iseqno, oseqno, icsum and ocsum as a nested data json object Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* gre: add different per-protocol prefixes to GRE-TAP IPv4/6 tunnel interfaces.Roger Pueyo Centelles2017-01-031-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit modifies the /lib/netifd/proto/gre.sh script so that, when GRE-TAP tunnels are created, either IPv4 or IPv6, the prefix before the chosen interface name contains the "tap" substring, to differentiate them from non-TAP GRE tunnels. Right now, both GRE and GRE-TAP tunnel (either IPv4 or IPv6) interfaces defined in /etc/config/network are named equally ("gre-"+$ifname or "grev6"+$ifname) upon creation. For instance, the following tunnels: config interface 'tuna' option peeraddr '172.30.22.1' option proto 'gre' config interface 'tunb' option peeraddr '192.168.233.4' option proto 'gretap' config interface 'tunc' option peer6addr 'fdc5:7c9e:e93d:45af::1' option proto 'grev6' config interface 'tund' option peer6addr 'fdc0:6071:1348:31ff::2' option proto 'grev6tap' are named, respectively, "gre-tuna", "gre-tunb", "grev6-tunc" and "grev6-tund". The current change makes that each GRE tunnel interface of the four different types available (gre, gretap, grev6 and grev6tap) gets a different prefix. Therefore, the abovementioned tunnels will be named, respectively: "gre4-tuna", "gre4t-tunb", "gre6-tunc" and "gre6t-tund". This is coherent with other types of virtual interfaces (i.e. PPP, PPPoE, PPPoA) where the whole protocol name is used. For instance, a PPPoA interface named "p1" and a PPPoE interface named "p2" will respectively appear as "pppoa-p1" and "pppoe-p2", not as "ppp-p1" and "ppp-p2"). Since Linux interfaces names are limited to 15 characters, these prefixes leave, for the worst case (TAP tunnels), 9 characters for the actual name. Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
* gre: Remove ttl default value assignment (FS#312)Hans Dedecker2016-12-251-1/+1
| | | | | | | Don't assign a default ttl of 64 for gre tunnels as netifd takes care of the default ttl assignment Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* gre: add empty install rules for grev4 & grev6Alexandru Ardelean2016-12-221-0/+8
| | | | | | | | | | | | | | | Build seems to fail with: ``` Collected errors: * satisfy_dependencies_for: Cannot satisfy the following dependencies for X: * grev4 * * opkg_install_cmd: Cannot install package X ``` After adding an empty install rule, the failure goes away. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* gre: Support fqdn as remote tunnel endpointHans Dedecker2016-10-041-3/+3
| | | | Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* package/network/config/gre: ipv6 gre kmod package name was wrongFelix Fietkau2016-01-031-1/+1
| | | | | | | | | | Source package gre was depending on kmod-ip6-gre, however the actual kernel module package that is created is kmod-gre6. Therefore update (source) package gre for ipv6 gre support. Signed-off-by: Daniel Dickinson <openwrt@daniel.thecshore.com> SVN-Revision: 48100
* package: Remove dependencies to kmod-ipv6Steven Barth2015-09-211-1/+1
| | | | | | | | | Since r46834, IPv6 support is builtin if selected. Therefor, dependencies on kmod-ipv6 can no longer be fulfilled, since it is not a module anymore. Signed-off-by: Arjen de Korte <arjen+openwrt@de-korte.org> SVN-Revision: 47022
* Add a few SPDX tagsSteven Barth2014-11-021-0/+1
| | | | | | Signed-off-by: Steven Barth <steven@midlink.org> SVN-Revision: 43151
* GRE: Tos supportSteven Barth2014-09-291-1/+1
| | | | | | | | | | Tos support is added as a generic grev4/grev6 parameter which can have the following values : -inherit (outer header inherits the tos value of the inner header) -hex value Signed-off-by: Hans Dedecker <dedeckeh@gmail.com> SVN-Revision: 42700
* gre: Change hostdependcy to remote endpoint tunnel addressSteven Barth2014-08-051-1/+1
| | | | | | | | | Depend on the GRE tunnel peeraddr to trigger setup of the tunnel interface. Addresses the issue reported in https://lists.openwrt.org/pipermail/openwrt-devel/2014-August/027201.html Signed-off-by: Hans Dedecker <dedeckeh@gmail.com> SVN-Revision: 41998
* gre: Generic Routing Encapsulation package supportSteven Barth2014-07-301-0/+64
The package supports Generic Routing Encapsulation support by registering following protocol kinds: -gre -gretap -grev6 -grev6tap Following options are valid for gre and gretap kinds: -ipaddr -peeraddr -df -mtu -ttl -tunlink -zone -ikey -okey -icsum -ocsum -iseqno -oseqno The gretap kind supports additionally the network option Following options are valid for grev6 and grev6tap kinds: -ip6addr -peer6addr -weakif -mtu -ttl -tunlink -zone -ikey -okey -icsum -ocsum -iseqno -oseqno The grev6tap kind supports additionally the network option Typical network config for a GREv4 tunnel : config interface 'gre' option peeraddr '172.16.18.240' option mtu '1400' option proto 'gre' option tunlink 'wan' option zone 'tunnel' Typical network config for a GREv4 tap tunnel : config interface 'gretap' option peeraddr '195.207.5.79' option mtu '1400' option proto 'gretap' option zone 'tunnel' option tunlink 'wan' option network 'wlan_ap' I added myself as maintainer for the moment; feel free to change. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com> SVN-Revision: 41897