aboutsummaryrefslogtreecommitdiffstats
path: root/package/network/config/gre/files
Commit message (Collapse)AuthorAgeFilesLines
* gre: use alternative way to check if kernel support is enabledAlin Nastac2021-03-131-4/+2
| | | | | | | When necessary support is built in kernel, gre protocol support is not enabled in netifd. Signed-off-by: Alin Nastac <alin.nastac@gmail.com>
* gre: add ipv6 parameter to gre interfacesAlin Nastac2019-12-021-2/+4
| | | | | | | | | IPv6 protocol is enabled on all gre interfaces, but gre(v6)tap interfaces are usually added to a bridge interface, in which case IPv6 should be enabled only on the bridge interface. Signed-off-by: Alin Nastac <alin.nastac@gmail.com> Signed-off-by: Hans Dedecker <dedeckeh@gmail.com> [PKG_RELEASE increase]
* gre: introduce 'nohostroute' optionFabian Bläse2019-05-311-4/+10
| | | | | | | | | | | It is not always necessary to add a host route for the gre peer address. This introduces a new config option 'nohostroute' (similar to the option introduced for wireguard in d8e2e19) to allow to disable the creation of those routes explicitely. Signed-off-by: Fabian Bläse <fabian@blaese.de> Signed-off-by: Hans Dedecker <dedeckeh@gmail.com> [PKG_RELEASE increase]
* gre: remove setting default firewall zone to wanFlorian Eckert2019-02-071-1/+0
| | | | | | | | | | | | | | | | | | | | | | There are two problems with this behaviour that the zone is set to wan if no zone config option is defined in the interface section. * The zone for the interface is "normally" specified in the firewall config file. So if we have defined "no" zone for this interface zone option is set now to "wan" additonaly if we add the interface in the firewall config section to the "lan" zone, the interface is added to lan and wan at once. iptables-save | grep <iface> This is not what I expect. * If I do not want to set a zone to this interface it is not possible. Remove the default assigment to wan if no zone option is defined. If some one need the option it stil possible to define this option. Signed-off-by: Florian Eckert <fe@dev.tdt.de> Signed-off-by: Hans Dedecker <dedeckeh@gmail.com> [PKG_RELEASE increase]
* gre: make encaplimit support configurableHans Dedecker2018-10-171-1/+3
| | | | | | | | | | | Make inclusion of the destination option header containing the tunnel encapsulation limit configurable for IPv6 GRE packets. Setting the uci parameter encaplimit to ignore; allows to disable the insertion of the destination option header in the IPv6 GRE packets. Otherwise the tunnel encapsulation limit value can be set to a value from 0 till 255 by setting the encaplimit uci parameter accordingly. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* treewide: fix shellscript syntax errors/typosLorenzo Santina2017-09-131-1/+1
| | | | | | | | | Fix multiple syntax errors in shelscripts (of packages only) These errors were causing many conditions to not working properly Signed-off-by: Lorenzo Santina <lorenzo.santina@edu.unito.it> [increase PKG_RELEASE, drop command substitution from directip.sh] Signed-off-by: Mathias Kresin <dev@kresin.em>
* gre: add gre specific settings as nested json objectHans Dedecker2017-03-211-1/+10
| | | | | | | 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-6/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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: Support fqdn as remote tunnel endpointHans Dedecker2016-10-041-2/+28
| | | | Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* gre: Support multicast configurable gre interfacesFelix Fietkau2016-02-011-2/+5
| | | | | | | | | | | UCI paramater multicast is added which allows to toggle multicast support on gre interfaces. By default multicast support is enabled as gre tunnels are often used in combination with routing protocols using multicast. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com> Signed-off-by: Nick Podolak <nicholas.podolak@dtechlabs.com> SVN-Revision: 48596
* GRE: Tos supportSteven Barth2014-09-291-2/+4
| | | | | | | | | | 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-2/+2
| | | | | | | | | 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/+235
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
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-23 02:28:48 +0000