aboutsummaryrefslogtreecommitdiffstats
path: root/package/network/ipv6/map
Commit message (Collapse)AuthorAgeFilesLines
* map: rename type to maptype (FS#3287)Remi NGUYEN VAN2020-08-192-14/+19
| | | | | | | | | | | | | | | | "type" is already used as a common option for all protocols types, so using the same option name for the map type makes the configuration ambiguous. Luci in particular adds controls for both options and sees errors when reading the resulting configuration. Use "maptype" instead, but still fallback to "type" if "maptype" is not set. This allows configurations to migrate without breaking old configurations. This addresses FS#3287. Signed-off-by: Remi NGUYEN VAN <remi.nguyenvan+openwrt@gmail.com> Signed-off-by: Hans Dedecker <dedeckeh@gmail.com> [PKG_RELEASE increase]
* map: add a legacymap optionRemi NGUYEN VAN2020-08-152-8/+6
| | | | | | | | | | | | | | The legacy map version based on the IPv6 Interface Identifier in draft-ietf-softwire-map-03 was typically used by uncommenting the LEGACY variable in the map.sh file, which is not ideal. A proper configuration option is needed instead. The IPv6 Interface Identifier format described in the draft was eventually changed in RFC7597, but is still used by some major ISPs, including in Japan. Signed-off-by: Remi NGUYEN VAN <remi.nguyenvan+openwrt@gmail.com> Signed-off-by: Hans Dedecker <dedeckeh@gmail.com> [PKG_RELEASE increase]
* package: drop PKG_VERSION for purely local packagesAdrian Schmutzler2020-07-151-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the package guidelines, PKG_VERSION is supposed to be used as "The upstream version number that we're downloading", while PKG_RELEASE is referred to as "The version of this package Makefile". Thus, the variables in a strict interpretation provide a clear distinction between "their" (upstream) version in PKG_VERSION and "our" (local OpenWrt trunk) version in PKG_RELEASE. For local (OpenWrt-only) packages, this implies that those will only need PKG_RELEASE defined, while PKG_VERSION does not apply following a strict interpretation. While the majority of "our" packages actually follow that scheme, there are also some that mix both variables or have one of them defined but keep them at "1". This is misleading and confusing, which can be observed by the fact that there typically either one of the variables is never bumped or the choice of the variable to increase depends on the person doing the change. Consequently, this patch aims at clarifying the situation by consistently using only PKG_RELEASE for "our" packages. To achieve that, PKG_VERSION is removed there, bumping PKG_RELEASE where necessary to ensure the resulting package version string is bigger than before. During adjustment, one has to make sure that the new resulting composite package version will not be considered "older" than the previous one. A useful tool for evaluating that is 'opkg compare-versions'. In principle, there are the following cases: 1. Sole PKG_VERSION replaced by sole PKG_RELEASE: In this case, the resulting version string does not change, it's just the value of the variable put in the file. Consequently, we do not bump the number in these cases so nobody is tempted to install the same package again. 2. PKG_VERSION and PKG_RELEASE replaced by sole PKG_RELEASE: In this case, the resulting version string has been "version-release", e.g. 1-3 or 1.0-3. For this case, the new PKG_RELEASE will just need to be higher than the previous PKG_VERSION. For the cases where PKG_VERSION has always sticked to "1", and PKG_RELEASE has been incremented, we take the most recent value of PKG_RELEASE. Apart from that, a few packages appear to have developed their own complex versioning scheme, e.g. using x.y.z number for PKG_VERSION _and_ a PKG_RELEASE (qos-scripts) or using dates for PKG_VERSION (adb-enablemodem, wwan). I didn't touch these few in this patch. Cc: Hans Dedecker <dedeckeh@gmail.com> Cc: Felix Fietkau <nbd@nbd.name> Cc: Andre Valentin <avalentin@marcant.net> Cc: Matthias Schiffer <mschiffer@universe-factory.net> Cc: Jo-Philipp Wich <jo@mein.io> Cc: Steven Barth <steven@midlink.org> Cc: Daniel Golle <dgolle@allnet.de> Cc: John Crispin <john@phrozen.org> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* map: don't set default firewall zone to wanHans Dedecker2019-05-262-23/+27
| | | | | | | | | | Don't set the default firewall zone to wan if not specified to keep the behavior aligned with other tunnel protocols like gre and 6rd. If the interface zone is not specified try to get it from the firewall config when constructing the procd firewall rule. While at it only add procd inbound/outbound firewall rules if a zone is specified. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* map: depend on nat46, provide map-tHans Dedecker2019-01-271-6/+7
| | | | Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* map: drop default encaplimit valueHans Dedecker2018-09-192-2/+2
| | | | | | | | | | | | | Setting encaplimit to a numerical value results into the value being included as tunnel encapsulation limit in the destination option header for tunneled packets. Several users have reported interop issues as not all ISPs support the destination option header containing the tunnel encapsulation limit resulting into broken map connectivity. Therefore drop the default encaplimit value for map tunnels so no destination option header is included by default. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* map: make tunnel encapsulation limit support configurable (FS#1501)Hans Dedecker2018-06-042-8/+10
| | | | | | | | | | | | Be compatible with ISPs which don't support the destination option header containing the tunnel encapsulation limit as reported in FS#1501. Setting the uci parameter encaplimit to ignore; allows to disable the insertion of the destination option header in the map-e packets. Otherwise the tunnel encapsulation limit value can be set to a value from 0 till 255 by setting the encaplimit uci parameter accordingly. If no encaplimit value is specified the default value is 4 as before. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* map: fix psidlen becoming negative (FS#1430)Hans Dedecker2018-03-292-11/+17
| | | | | | | | | Fix psidlen becomes negative in case embedded address bit lenght is smaller than IPv4 suffix length. While at it improve parameter checking making the code more logical and easier to read. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* map: use nested json data object to store map-e fmrs parametersHans Dedecker2017-08-292-7/+11
| | | | | | | Replace the string array containing the fmrs parameters by a nested data json object holding an array of fmrs parameters Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* map: fix boolean argument passed to blobmsg_check_attr in mapcalcHans Dedecker2017-08-262-2/+2
| | | | Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* map: add ealen as configurable uci parameterHans Dedecker2017-08-242-1/+2
| | | | Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* map: take over maintainershipHans Dedecker2017-01-121-1/+1
| | | | | Signed-off-by: Hans Dedecker <dedeckeh@gmail.com> Acked-by: Jo-Philipp Wich <jo@mein.io>
* map: delete map-t device when tearing down map interfaceHans Dedecker2017-01-122-2/+12
| | | | | | | | | | | | Delete the map-t device when tearing down the map-t interface; as such there's no conflict when the map-t interface comes up again when trying to add the map-t device as the map-t device was still present (Can not add: device 'map-wan6_4' already exists!). Only call ifdown in teardown for map-e and lw6o4 map interfaces types in order to suppress the trace "wan6_4 (6652): Interface wan6_4_ not found" Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* map: Have cmake find libubus.hFlorian Fainelli2016-12-161-0/+3
| | | | | | Update CMakeList.txt to look for libubus.h since we depend on it. Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
* network/ipv6/map: drop Build/Prepare rule in favor of default oneAlexandru Ardelean2016-10-151-5/+0
| | | | Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* 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
* map: be less restrictive when matching lw4over6 prefixesSteven Barth2015-09-082-6/+11
| | | | | | Signed-off-by: Steven Barth <steven@midlink.org> SVN-Revision: 46819
* map: ignore insignificant PSID bitsSteven Barth2015-09-072-2/+4
| | | | | | Signed-off-by: Steven Barth <steven@midlink.org> SVN-Revision: 46804
* map: add debug-code for mapcalcSteven Barth2015-09-012-19/+29
| | | | | | Signed-off-by: Steven Barth <steven@midlink.org> SVN-Revision: 46763
* map: add sleep work-around for lw4o6 race-conditionSteven Barth2015-06-092-1/+4
| | | | | | Signed-off-by: Steven Barth <steven@midlink.org> SVN-Revision: 45936
* map: add support for lw4o6 address matching, minor optimizationsSteven Barth2015-05-262-38/+58
| | | | | | Signed-off-by: Steven Barth <steven@midlink.org> SVN-Revision: 45770
* map: set ealen to psidlen for lw4over6Steven Barth2015-05-162-1/+4
| | | | | | Signed-off-by: Steven Barth <steven@midlink.org> SVN-Revision: 45689
* map: shorten autogenerated sub-interface names to account for limitsSteven Barth2015-04-302-3/+3
| | | | | | Signed-off-by: Steven Barth <steven@midlink.org> SVN-Revision: 45590
* map: Fix white space errorsJohn Crispin2015-02-031-3/+3
| | | | | | Signed-off-by: Hans Dedecker <dedeckeh@gmail.com> SVN-Revision: 44246
* map: export calculated ruleset to /tmpSteven Barth2015-01-132-1/+4
| | | | | | Signed-off-by: Steven Barth <steven@midlink.org> SVN-Revision: 43961
* map: ignore psid and psidlen if psidlen is 0Steven Barth2015-01-122-4/+6
| | | | | | Signed-off-by: Steven Barth <steven@midlink.org> SVN-Revision: 43946
* license info - revert r43155John Crispin2014-11-031-3/+0
| | | | | | | | turns out that r43155 adds duplicate info. Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 43167
* Add more license tags with SPDX identifiersJohn Crispin2014-11-031-0/+3
| | | | | | | | | | | | | | | | | | Note, that licensing stuff is a nightmare: many packages does not clearly state their licenses, and often multiple source files are simply copied together - each with different licensing information in the file headers. I tried hard to ensure, that the license information extracted into the OpenWRT's makefiles fit the "spirit" of the packages, e.g. such small packages which come without a dedicated source archive "inherites" the OpenWRT's own license in my opinion. However, I can not garantee that I always picked the correct information and/or did not miss license information. Signed-off-by: Michael Heimpold <mhei@heimpold.de> SVN-Revision: 43155
* Add a few SPDX tagsSteven Barth2014-11-021-0/+1
| | | | | | Signed-off-by: Steven Barth <steven@midlink.org> SVN-Revision: 43151
* map: fix portsets starting with 0 and use regular NAT for 1:1 MAPSteven Barth2014-10-023-19/+31
| | | | | | Signed-off-by: Steven Barth <steven@midlink.org> SVN-Revision: 42741
* map: add support for map-t if availableSteven Barth2014-06-042-2/+48
| | | | SVN-Revision: 41003
* Initial support for MAP-E and Lightweight 4over6 protocolSteven Barth2014-05-224-0/+597
SVN-Revision: 40823
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-18 14:06:23 +0000