aboutsummaryrefslogtreecommitdiffstats
path: root/package/network/ipv6
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-156-11/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* odhcp6c: update to latest git HEADHans Dedecker2020-03-291-3/+3
| | | | | | f575351 ra: fix sending router solicitations Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* odhcp6c: fix compilation with musl 1.2.0Hans Dedecker2020-03-261-3/+3
| | | | | | 49305e6 odhcp6c: fix compilation with musl 1.2.0 Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* 6in4/6in4.sh: remove some bashism (usage of [[)Sven Roederer2020-01-261-1/+1
| | | | | | | "[[" is a bash extension for test. As the ash-implementation is not fully compatible we drop its usage. Signed-off-by: Sven Roederer <devel-sven@geroedel.de>
* 6in4: add rfc1918 check functionSean Kenny2019-10-181-0/+19
| | | | | | | | | | | | | | | | | | | | | | | This is a precursor to adding proper support for multiple 6in4 tunnels with the already programmed tunlink parameter. This is an essential sanity check so as to not break existing and working behind NAT setups. Signed-off-by: Sean Kenny <skenny@wfap.ca> 6in4: add myip he.net api parameter logic This is to add proper support for multiple 6in4 tunnels with the already programmed tunlink parameter. As it stands before this commit, if there is a multi wan setup that consists of dynamic ips, there is no way to use the dynamic update feature as the he.net api is implicitly using the ip address of the caller. This will explicitly use the ipaddr specified in the interface config OR the ip of the tunlink interface specified in the dynamic update api call instead ONLY if the final resolved ipaddr variable is not an rfc1918 address. Signed-off-by: Sean Kenny <skenny@wfap.ca>
* odhcp6c: update to latest git HEADHans Dedecker2019-09-071-2/+2
| | | | | | e199804 dhcpv6: sanitize oro options Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* 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>
* 464xlat: don't set default firewall zone to wanHans Dedecker2019-05-262-13/+17
| | | | | | | | | | 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 a procd inbound firewall rule if a zone is specified. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* 6to4: update OpenWrt documentation URLVieno Hakkerinen2019-03-091-1/+1
| | | | Signed-off-by: Vieno Hakkerinen <txt.file@txtfile.eu>
* map: depend on nat46, provide map-tHans Dedecker2019-01-271-6/+7
| | | | Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* 464xlat: import from routing, add myself as maintainerHans Dedecker2019-01-274-0/+316
| | | | Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* odhcp6c: update to latest git HEADHans Dedecker2019-01-111-3/+3
| | | | | | | | | | d2e247d odhcp6c: align further with RFC8415 ce83a23 dhcpv6: avoid parsing unncessary IAs b079733 dhcpv6: set cnt to correct IOV enum 41494da dhcpv6: get rid of request_prefix f7437e4 dhcpv6: sanitize option request list 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>
* ds-lite: 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 ds-lite connectivity. Therefore drop the default encaplimit value for ds-lite tunnels so no destination option header is included by default. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* odhcp6c: add client fqdn and reconfigure optionspacien2018-09-082-3/+9
| | | | | | | | Allowing DHCPV6_CLIENT_FQDN and DHCPV6_ACCEPT_RECONFIGURE to be turned off. Defaulting to false, former behavior remains unchanged. Signed-off-by: pacien <pacien.trangirard@pacien.net> Signed-off-by: Hans Dedecker <dedeckeh@gmail.com> [PKG_RELEASE increase]
* odhcp6c: apply IPv6/ND configuration earlierHans Dedecker2018-08-092-8/+9
| | | | | | | | | | Apply IPv6/ND configuration before proto_send_update so that all config info is available when netifd is handling the notify_proto ubus call. In particular this fixes an issue when netifd is updating the downstream IPv6 mtu as netifd was still using the not yet updated upstream IPv6 mtu to set the downstream IPv6 mtu Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* thc-ipv6: Update URLsRosen Penev2018-07-291-2/+2
| | | | | | Development has moved to GitHub. Found using UScan. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* odhcp6c: add noserverunicast config option for broken DHCPv6 serversHans Dedecker2018-07-152-6/+9
| | | | | | | | | Fix broken DHCPv6 servers which provide the server unicast option but do not reply on DHCPv6 renew messages directed to the IPv6 address contained in the server unicast option whihc results in broken IPv6 connectivity. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* odhcp6c: update to latest git HEADHans Dedecker2018-06-201-4/+4
| | | | | | b99c1f6 odhcp6c: remove len check in option parsing handle Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* odhcp6c: user string option supportHans Dedecker2018-06-111-3/+3
| | | | | | ca8822b odhcp6c: add support for user string options 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>
* odhcp6c: make ds-lite/map tunnel encapsulation limit support configurable ↵Hans Dedecker2018-06-043-3/+9
| | | | | | | | | | | | | | (FS#1501) Be compatible with ISPs which don't support the destination option header containing the tunnel encapsulation limit as reported in FS#1501 for dynamic created ds-lite/map interfaces. Setting the uci parameter encaplimit_dslite/map to ignore; allows to disable the insertion of the destination option header for the dynamic created ds-lite/map interface. Otherwise the tunnel encapsulation limit value can be set to a value from 0 till 255 by setting the encaplimit_dslite/map uci parameter accordingly. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* ds-lite: make tunnel encapsulation limit support configurable (FS#1501)Hans Dedecker2018-06-042-3/+7
| | | | | | | | | | | | 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 ds-lite 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>
* odhcp6c: update to latest git HEADHans Dedecker2018-04-291-3/+3
| | | | | | | 5316d7f ra: always trigger update in case of RA parameter change 327f73d dhcpv6: fix strncpy bounds Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* odhcp6c: update to latest git HEADHans Dedecker2018-04-051-4/+4
| | | | | | | | 74b5a3 script: fix possible negative delay 473f248 dhcpv6: always trigger script update in case of IA updates ea18935 ra: rework route information option handling Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* odhcp6c: update to latest git HEADHans Dedecker2018-03-311-3/+3
| | | | | | | | | | 5cbd305 odhcp6c: improve code readibility eb83b7e treewide: improve error handling b7b11cb dhcpv6: initialize ifreq struct f0469e2 ra: handle socket fail creation d573461 odhcp6c: fix file pointer leakage 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>
* 6in4: support multiple additional user prefixesJo-Philipp Wich2018-03-132-6/+11
| | | | | | | | | | | | | | Support configuration in the form... list ip6prefix 2001:db8:1234::/64 list ip6prefix 2001:db8:5678::/64 ... to allow specifying multiple routed IPv6 prefixes. Implements feature request FS#1361. Signed-off-by: Jo-Philipp Wich <jo@mein.io> Acked-by: Hans Dedecker <dedeckeh@gmail.com>
* odhcp6c: rework sendopts handlingHans Dedecker2018-02-242-7/+6
| | | | | | Bring logic of sendopts handling in line with ip6prefix handling Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* odhcp6c: support multiple additional user prefixesJo-Philipp Wich2018-02-243-6/+13
| | | | | | | | | | | | | Support configuration in the form... list ip6prefix 2001:db8:1234::/64 list ip6prefix 2001:db8:5678::/64 ... to allow specifying multiple additional IPv6 prefixes. Implements feature request FS#1361. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* odhcp6c: fix appending of emtpy sendopt value (FS#1336)Hans Dedecker2018-02-082-2/+2
| | | | | | | | Don't append an empty sendopts value as odhcp6c bails out immediately on an empty -x option triggering an infinite start loop of odhcp6c Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* odhcp6c: change sendopts option into listHans Dedecker2018-02-082-7/+9
| | | | | | | | Commit a26045049b added support for sendopts as a string; since multiple sendopts values can be specified it makes more sense to model it as a list of strings. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* odhcp6c: add defaultreqopts config optionHans Dedecker2018-02-012-3/+6
| | | | | | | | | By default odhcp6c asks for a default list of options; the config option defaultreqopts allows to tweak this behavior. When set to 0 odhcp6c will not ask for any options except for the options specified in the reqopts config option. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* odhcp6c: add sendopts config support and update to latest git HEADHans Dedecker2018-01-182-5/+11
| | | | | | | | | | | | | | | | | | | | | Add sendopts config support allowing to add options in sent DHCPv6 packets. Options can be configured as follows : uci set network.wan6.sendopts="sntpservers:3001:3001::1,3001:3001::2 11:00000000000000000000006674692F 0x3e8:ABCDEF" Based on a patch by Frank Andrieu <fandrieu@gmail.com> See https://git.openwrt.org/?p=project/odhcp6c.git;a=commit;h=510aaf6d528210c5e8a6159f9b80b32615e88c5f for a more detailed description. Latest git changes : 1f93bd4 dhcpv6: rework option passthrough logic a477e95 odhcp6c: rework userclass and vendorclass command handling 510aaf6 odhcp6c: add -x opt:val support ab75be1 treewide: update copyrights to 2018 f3a4609 odhcp6c: let odhcp6c_add_state return a success/failure indication Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* 6rd: pass ipcalc as argument to evalHans Dedecker2018-01-152-3/+3
| | | | | | | | Instead of grepping for NETWORK after calling ipcalc.sh; pass ipcalc.sh as argument to eval allowing to use $NETWORK to retrieve the IPv4 prefix (ip4prefix). Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* treewide: replace LEDE_GIT with PROJECT_GITJo-Philipp Wich2018-01-101-1/+1
| | | | | | | Remove LEDE_GIT references in favor to the new name-agnostic PROJECT_GIT variable. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* odhcp6c: add workaround for broken extendprefix scenarioHans Dedecker2017-09-052-3/+20
| | | | | | | | | | | | Extendprefix is typically used to extend an IPv6 RA prefix from a mobile wan link to the LAN; such scenario requires correct RA prefix settings like the on link flag not being set. However some mobile manufacter set the RA prefix on link flag which breaks basic IPv6 routing. Work around this issue by filtering out the route being equal to the extended prefix. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* odhcp6c: add ra_holdoff config option and update to git HEAD version (FS#964)Hans Dedecker2017-09-032-6/+9
| | | | | | | | | 51733a6 ra: align RA update interval with RFC4861 (FS#964) Add ra_holdoff config option which allows to configure the RA minimum update interval which is by default 3 seconds as stated in RFC4861. 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>
* dhcpv6: add missing dollar sign in dhcpv6 script (FS#874)Hans Dedecker2017-06-292-2/+2
| | | | Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* 6rd: add 6rd specific settings as nested json objectHans Dedecker2017-05-222-3/+7
| | | | | | Add 6rd specific settings prefix, relay-prefix as a nested data json object Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* odhcp6c: update to git HEAD versionHans Dedecker2017-03-221-3/+3
| | | | | | | | | | | 0463b05 dhcpv6: rebind capability support in reconfigure message (rfc6644) 53767fc dhcpv6: respect renew end point when handling reconfigure message dd892e2 dhcpv6: calculate T1, T2 and T3 in a more sane manner 8a6ca6e md5: use libubox md5 library as local implementation 89822de dhcpv6: don't return renew msg in case of invalid msg type in reconfigure msg 4160c0e treewide: align coding style Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* odhcp6c: update to git HEAD versionHans Dedecker2017-03-161-3/+6
| | | | | | 7e0d8b8 CMakeLists: don't enable libubox md5 implementation by default Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* odhcp6c: update to git HEAD versionHans Dedecker2017-03-061-3/+3
| | | | | | c69555c dhcpv6: use PRIu64 print macro Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* thc-ipv6: Allow overriding CFLAGSFlorian Fainelli2017-03-011-0/+12
| | | | | | | | thc-ipv6 did not allow an external environment to override CFLAGS, which would lead to our CFLAGS not being passed properly (relro, optimizations, etc...) Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
* odhcp6c: fix PKG_MIRROR_HASHHans Dedecker2017-02-171-1/+1
| | | | Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 21:09:03 +0000