Skip to content
Snippets Groups Projects

Compare revisions

Changes are shown as if the source revision was being merged into the target revision. Learn more about comparing revisions.

Source

Select target project
No results found

Target

Select target project
  • ffbs/ffbs-gluon
  • parabol1337/ffbs-gluon
  • darkbit/ffbs-gluon
3 results
Show changes
Commits on Source (15)
  • Julian's avatar
  • Christoph Krapp's avatar
    modules: update LEDE · c28b797c
    Christoph Krapp authored
    
    aaecfecdcd kernel: bump kernel 4.4 to version 4.4.139
    b08003223a base-files: fix links in banner.failsafe
    71019a7605 ar71xx: fix 5 GHz Wi-Fi on NBG6716
    ba5c0a1dea Revert "base-files: fix UCI config parsing and callback handling"
    5c6a8a9cdb kernel: bump kernel 4.4 to version 4.4.138
    cf4a37a581 uci: add missing 'option' support to uci_rename()
    7fc94b2a25 mac80211: rt2x00: no longer use TXOP_BACKOFF for probe frames
    b03826d8aa kernel: bump kernel 4.4 to version 4.4.137
    21f44e3389 map: add ealen as configurable uci parameter
    
    Signed-off-by: default avatarChristoph Krapp <achterin@googlemail.com>
    Unverified
    c28b797c
  • Matthias Schiffer's avatar
  • Matthias Schiffer's avatar
  • Adorfer's avatar
    gluon-config-mode-mesh-vpn: i18n/de: fix missing comma · 658f1ea4
    Adorfer authored
    (cherry picked from commit 65d172f8)
    Unverified
    658f1ea4
  • Sven Eckelmann's avatar
    gluon-mesh-batman-adv: Drop IPv4 anycast related packets from/to bat0 · a7a5db9f
    Sven Eckelmann authored
    The commit b3762fc6 ("gluon-client-bridge: move IPv4 local subnet route
    to br-client (#1312)") moves the IPv4 prefix from the local-port interface
    to br-client. A client requesting an IPv4 connection to the IPv4 anycast
    address of the node (the device running gluon) will create following
    packets:
    
    1. ARP packet from client to get the MAC of the mac address of the anycast
       IPv4 address
    2. ARP reply from node to client with the anycast MAC address for the IPv4
       anycast address
    3. IPv4 packet from client which requires reply (for example ICMP echo
       request)
    4. ARP request for the client MAC address for its IPv4 address in prefix4
       (done with the mac address of br-client and transmitted over br-client)
    5. IPv4 packet from node (transmitted over br-client with br-client MAC
       address) as reply for the client IPv4 packet (for example ICMP echo
       reply)
    
    The step 4 is extremely problematic here. ARP replies with the anycast IPv4
    address must not be submitted or received via bat0 - expecially not when it
    contains an node specific MAC address as source. When it is still done then
    the wrong MAC address is stored in the batadv DAT cache and ARP packet is
    maybe even forwarded to clients. This latter is especially true for ARP
    requests which are broadcast and will be flooded to the complete mesh.
    
    Clients will see these ARP packets and change their own neighbor IP
    (translation) table. They will then try to submit the packets for IPv4
    anycast addresses to the complete wrong device in the mesh. This will for
    example break the access to the status page to the connected device or the
    anycast DNS forwarder implementation. Especially the latter causes extreme
    latency when clients try to connect to server using a domain name or even
    breaks the connection setup process completely. Both are caused by the
    unanswered DNS requests which at first glance look like packet loss.
    
    An node must therefore take care of:
    
    * not transmitting ARP packets related to the anycast IPv4 address over
      bat0
    * drop ARP packets related to the anycast IPv4 when they are received on
      bat0 from a still broken node
    * don't accept ARP packets related to the anycast IPv4 replies on local
      node when it comes from bat0
    
    Fixes: b3762fc6 ("gluon-client-bridge: move IPv4 local subnet route to br-client (#1312)")
    a7a5db9f
  • Sven Eckelmann's avatar
    gluon-client-bridge: Revert "move IPv4 local subnet route to br-client (#1312)" · ea9a69f7
    Sven Eckelmann authored
    The commit b3762fc6 ("gluon-client-bridge: move IPv4 local subnet route
    to br-client (#1312)") moves the IPv4 prefix from the local-port interface
    to br-client. A client requesting an IPv4 connection to the IPv4 anycast
    address of the node (the device running gluon) will create following
    packets:
    
    1. ARP packet from client to get the MAC of the mac address of the anycast
       IPv4 address
    2. ARP reply from node to client with the anycast MAC address for the IPv4
       anycast address
    3. IPv4 packet from client which requires reply (for example ICMP echo
       request)
    4. ARP request for the client MAC address for its IPv4 address in prefix4
       (done with the mac address of br-client and transmitted over br-client)
    5. IPv4 packet from node (transmitted over br-client with br-client MAC
       address) as reply for the client IPv4 packet (for example ICMP echo
       reply)
    
    The step 4 and 5 are problematic here because packets use the node specific
    MAC addresses from br-client instead of the anycast MAC address. The client
    will receive the ARP packet with the node specific MAC address and change
    their own neighbor IP (translation) table. This will for example break the
    access to the status page to the connected device or the anycast DNS
    forwarder implementation when the client roams to a different node.
    
    This reverts commit b3762fc6 and adds an
    upgrade code to remove local_node_route on on existing installations.
    ea9a69f7
  • mokkin's avatar
    docs: site: fix typo (#1498) · aaef6163
    mokkin authored
    aaef6163
  • Andreas Ziegler's avatar
  • Andreas Ziegler's avatar
    modules: update LEDE · 0cb98882
    Andreas Ziegler authored
    309414ee8d uclient: update to latest git HEAD
    bcf91e578c downloads.mk: introduce name-agnostic PROJECT_GIT variable
    b7e3f10e80 sdk: include arch/arm/ Linux includes along with arch/arm64/ ones
    d93ef3c8c8 sdk: bundle usbip userspace sources
    e5b7404f25 kmod-sched-cake: bump to 20180716
    2725ad8de4 iproute2: merge upstream CAKE support
    28d4e55432 WDR4900v1 remove dt node for absent hw crypto.
    21c317a892 build: fix compile error when a package includes itself in PROVIDES
    aee5c53a8d apm821xx: fix sata access freezes
    54b91c85e7 Revert "iproute2: tc: bump to support kmod-sched-cake"
    90eac8984a Revert "kmod-sched-cake: bump to 20180716"
    91c9400816 scripts: bundle-libraries: fix build on OS X (FS#1493)
    54c0ef6ff5 build: bundle-libraries.sh: patch bundled ld.so
    79c8f2f50b mtd: improve check for TRX header being already fixed
    828eaeee25 mtd: support bad blocks within the mtd_fixtrx()
    8d4da3c589 iproute2: tc: bump to support kmod-sched-cake
    0e1606ba3d kmod-sched-cake: bump to 20180716
    c6a46c6e1d LEDE v17.01.5: revert to branch defaults
    248b358903 LEDE v17.01.5: adjust config defaults
    38e704be71 kernel: bump kernel 4.4 to version 4.4.140
    0cb98882
  • Matthias Schiffer's avatar
    modules: update LEDE · 6a3d5554
    Matthias Schiffer authored
    0a2c984222d0 kernel: ext4: fix check to prevent initializing reserved inodes
    91d209362b97 kernel: bump kernel 4.4 to version 4.4.147
    b5d9776cd24b firmware: amd64-microcode: update to 20180524
    55ab8649e72b firmware: intel-microcode: bump to 20180703
    
    Fixes #1504
    Unverified
    6a3d5554
  • Matthias Schiffer's avatar
    modules: update LEDE · b4e87400
    Matthias Schiffer authored
    8f5c55f63ece tools/e2fsprogs: update to 1.44.1
    d35a7bf4b462 e2fsprogs: bump to 1.44.0
    79ac69d9c926 tools/e2fsprogs: Update to 1.43.7
    5d9114c9cb3b tools/e2fsprogs: Update to 1.43.6
    7955fab22ac4 tools/e2fsprogs: Update to 1.43.5
    866e5b495677 tools/e2fsprogs: Update to 1.43.4
    a964738a5c88 Revert "tools/e2fsprogs: fix building on a glibc 2.27 host"
    1e09cbf11844 tools/bison: Update to 3.0.5
    9e864bfccea5 mac80211: brcmfmac: fix compilation with SDIO support
    13f219569d4c mac80211: brcmfmac: backport patch setting WIPHY_FLAG_HAVE_AP_SME
    0c76265d0819 mac80211: brcmfmac: backport important changes from the 4.19
    9d8940c5b92f mac80211: brcmfmac: backport important changes from the 4.18
    84ef414bd422 mac80211: brcmfmac: backport important changes from the 4.16
    57102f6c0633 mac80211: brcmfmac: backport important changes from the 4.15
    6805e44004b7 mac80211: brcmfmac: backport important changes from the 4.14
    e3bc2e488d03 mac80211: brcmfmac: backport important changes from the 4.13
    00b4e6567726 mac80211: brcmfmac: backport important changes from the 4.12
    f8c364b72042 mac80211: brcmfmac: backport use-after-free fix from 4.11
    85e6ac468efc mac80211: brcmfmac: group 4.11 backport patches
    d3b8b5be3455 openssl: update to version 1.0.2p
    f3865bd4efa8 kernel: bump kernel 4.4 to version 4.4.148
    5886a5060a4c mbedtls: update to version 2.7.5
    9bc43f3e65bc curl: fix some security problems
    b3983323a1f2 wpa_supplicant: fix CVE-2018-14526
    6449ed155301 tools: findutils: fix compilation with glibc 2.28
    6e78c5502c94 tools: m4: fix compilation with glibc 2.28
    583fd4b229b0 brcm47xx: revert upstream commit breaking BCM4718A1
    
    Fixes build with glibc 2.28.
    Unverified
    b4e87400
  • Matthias Schiffer's avatar
    docs: releases/v2018.1: add regressions to known issues · bc0d240d
    Matthias Schiffer authored
    Fixes #1519
    Unverified
    bc0d240d
  • Matthias Schiffer's avatar
    docs: add v2018.1.1 release notes · ed3cb1f5
    Matthias Schiffer authored
    Unverified
    ed3cb1f5
  • Matthias Schiffer's avatar
    docs, README: Gluon v2018.1.1 · 469e0107
    Matthias Schiffer authored
    Unverified
    469e0107
Showing
with 134 additions and 34 deletions
......@@ -19,7 +19,7 @@ the future development of Gluon.
Please refrain from using the `master` branch for anything else but development purposes!
Use the most recent release instead. You can list all releases by running `git tag`
and switch to one by running `git checkout v2018.1 && make update`.
and switch to one by running `git checkout v2018.1.1 && make update`.
If you're using the autoupdater, do not autoupdate nodes with anything but releases.
If you upgrade using random master commits the nodes *will break* eventually.
......
......@@ -52,11 +52,7 @@ copyright = '2015-2018, Project Gluon'
# The version info for the project you're documenting, acts as replacement for
# |version| and |release|, also used in various other places throughout the
# built documents.
#
# The short X.Y version.
version = '2018.1'
# The full version, including alpha/beta/rc tags.
release = '2018.1'
version = release = '2018.1.1'
# The language for content autogenerated by Sphinx. Refer to documentation
# for a list of supported languages.
......
......@@ -37,7 +37,7 @@ increase throughput, although in practice the gain is minimal.
**Gateway configuration:**
1) Prepend the ``none`` cipher in fastds method list
1) Prepend the ``null`` cipher in fastd's method list
**Config Mode:**
......
......@@ -70,6 +70,7 @@ Several Freifunk communities in Germany use Gluon as the foundation of their Fre
:caption: Releases
:maxdepth: 1
releases/v2018.1.1
releases/v2018.1
releases/v2017.1.8
releases/v2017.1.7
......
Gluon 2018.1.1
==============
Bugfixes
~~~~~~~~
* Fix a bug leading to configuration loss on upgrade under certain circumstances
(`#1496 <https://github.com/freifunk-gluon/gluon/issues/1496>`_)
The issue can only occur when upgrading from 2018.1 and there are multiple
mirror entries in *site.conf* (specifically, an early failure for one of the
mirrors, e.g. during DNS resolution, followed by a successful upgrade from a
different mirror triggers the issue).
This is a regression in Gluon 2018.1.
* Fix next-node ARP issue
(`#1488 <https://github.com/freifunk-gluon/gluon/issues/1488>`_)
A routing table issue led to ARP requests being sent from the next-node IPv4 address, but with
a node-specific source MAC address. This could make the next-node IPv4 address unreachable.
This is a regression in Gluon 2018.1.
* Fix build on hosts with glibc 2.28
Fixed by various tool upgrades in LEDE (*bison*, *e2fsutils*, ...)
Other changes
~~~~~~~~~~~~~
* Linux kernel has been updated to v4.4.148
Known issues
~~~~~~~~~~~~
* Default TX power on many Ubiquiti devices is too high, correct offsets are unknown (`#94 <https://github.com/freifunk-gluon/gluon/issues/94>`_)
Reducing the TX power in the Advanced Settings is recommended.
* The MAC address of the WAN interface is modified even when Mesh-on-WAN is disabled (`#496 <https://github.com/freifunk-gluon/gluon/issues/496>`_)
This may lead to issues in environments where a fixed MAC address is expected (like VMware when promicious mode is disallowed).
* Inconsistent respondd API (`#522 <https://github.com/freifunk-gluon/gluon/issues/522>`_)
The current API is inconsistent and will be replaced eventually. The old API will still be supported for a while.
* Frequent reboots due to out-of-memory or high load due to memory pressure on weak hardware specially in larger meshes
(`#1243 <https://github.com/freifunk-gluon/gluon/issues/1243>`_)
Optimizations in Gluon 2018.1 have significantly improved memory usage.
There are still known bugs leading to unreasonably high load that we hope to
solve in future releases.
......@@ -92,9 +92,9 @@ ramips-rt305x [#newtarget]_ [#noibss]_
sunxi [#newtarget]_
===================
* LeMaker
* LeMaker/SinoVoip
- Lamobo r1
- Banana Pi (M1)
.. [#newtarget]
......@@ -268,6 +268,20 @@ must be made:
When shown, the password form requires a minimum password length of 12 characters now. This requirement
can be modified using the *config_mode.remote_login.min_password_length* setting.
* Next-node hostnames
The builtin DNS resolver of Gluon can be configured to resolve a next-node hostname to the
next-node IP address without querying an upstream DNS server. Since Gluon v2018.1, multiple
names can be specified. Old configurations setting *next_node.name* to a string must be
updated to provide an array of strings instead:
.. code-block:: lua
next_node = {
name = { 'nextnode.location.community.example.org' },
-- ...
},
i18n
====
......@@ -287,7 +301,19 @@ The status page has been rewritten to simplify the code and reduce its size. Rat
having a static frontend and retrieving all information via JavaScript, all static information
in the status page is now generated on the node, and JavaScript is only used for dynamic data.
To achieve this, the status page was ported to the gluon-web framework. The new status page
Many status page API endpoints have been removed; for all remaining endpoints, CORS
(Cross-Origin Resource Sharing) has been disabled, as it led to a privacy issues:
malicious websites could access the API via cross-site scripting, determining which
node a user was connected to.
The removal of CORS breaks compatibility with the node switching feature of the
old status page implementation: In the new status page, switching to another node will
reload the whole status page from the target node, while the old implementation would
only switch to another backend host. While this will facilitate future updates, as
frontend and backend always come from the same node and no stable API needs to be maintained,
it prevents switching from the old status page to nodes running the new version.
To achieve all this, the status page was ported to the gluon-web framework. The new status page
also makes use of Gluon's usual i18n facilities now. In addition, the gluon-web-model
package was split out of the gluon-web core package, as model support is only required
for config mode packages, but not for the new status page.
......@@ -374,3 +400,21 @@ Known issues
Optimizations in Gluon 2018.1 have significantly improved memory usage.
There are still known bugs leading to unreasonably high load that we hope to
solve in future releases.
* Configuration loss on upgrade under certain circumstances
(`#1496 <https://github.com/freifunk-gluon/gluon/issues/1496>`_)
The issue can only occur when upgrading from 2018.1 and there are multiple
mirror entries in *site.conf* (specifically, an early failure for one of the
mirrors, e.g. during DNS resolution, followed by a successful upgrade from a
different mirror triggers the issue).
This is a regression in Gluon 2018.1.
* Next-node ARP issue
(`#1488 <https://github.com/freifunk-gluon/gluon/issues/1488>`_)
A routing table issue leads to ARP requests being sent from the next-node IPv4 address, but with
a node-specific source MAC address. This can make the next-node IPv4 address unreachable.
This is a regression in Gluon 2018.1.
-- This is an example site configuration for Gluon v2018.1
-- This is an example site configuration for Gluon v2018.1.1
--
-- Take a look at the documentation located at
-- http://gluon.readthedocs.org/ for details.
......
......@@ -8,7 +8,7 @@ Gluon's releases are managed using `Git tags`_. If you are just getting
started with Gluon we recommend to use the latest stable release of Gluon.
Take a look at the `list of gluon releases`_ and notice the latest release,
e.g. *v2018.1*. Always get Gluon using git and don't try to download it
e.g. *v2018.1.1*. Always get Gluon using git and don't try to download it
as a Zip archive as the archive will be missing version information.
Please keep in mind that there is no "default Gluon" build; a site configuration
......@@ -43,7 +43,7 @@ Building the images
-------------------
To build Gluon, first check out the repository. Replace *RELEASE* with the
version you'd like to checkout, e.g. *v2018.1*.
version you'd like to checkout, e.g. *v2018.1.1*.
::
......
......@@ -104,7 +104,7 @@ wifi24 \: optional
WLAN configuration for 2.4 GHz devices.
``channel`` must be set to a valid wireless channel for your radio.
There are currently three interface types available. You many choose to
There are currently three interface types available. You may choose to
configure any subset of them:
- ``ap`` creates a master interface where clients may connect
......
......@@ -2,7 +2,7 @@ GLUON_FEEDS='openwrt gluon routing luci'
LEDE_REPO=https://git.openwrt.org/openwrt/openwrt.git
LEDE_BRANCH=lede-17.01
LEDE_COMMIT=b6a1f43075f96b0028e33ed1af1fe31068791d24
LEDE_COMMIT=8f5c55f63eceb326c3427a5ba79cea2a96af0e4f
PACKAGES_OPENWRT_REPO=https://github.com/openwrt/packages.git
PACKAGES_OPENWRT_BRANCH=lede-17.01
......
......@@ -23,7 +23,8 @@ uci:section('network', 'device', 'local_node_dev', {
local ip4, ip6
if next_node.ip4 then
ip4 = next_node.ip4 .. '/32'
local plen = site.prefix4():match('/%d+$')
ip4 = next_node.ip4 .. plen
end
if next_node.ip6 then
......
......@@ -29,7 +29,7 @@ msgid ""
"bandwidth available for the network. You can limit how much bandwidth the "
"node will use at most."
msgstr ""
"Dein Knoten kann deine Internetverbindung nutzen um darüber eine "
"Dein Knoten kann deine Internetverbindung nutzen, um darüber eine "
"VPN-Verbindung zu anderen Knoten aufzubauen. Die dafür "
"genutzte Bandbreite kannst du beschränken. Aktiviere die Option, falls keine "
"per WLAN erreichbaren Nachbarknoten in deiner Nähe sind oder du deine "
......
......@@ -15,6 +15,14 @@ rule('OUTPUT --logical-out br-client -o bat0 -s ' .. macaddr .. ' -j DROP')
if next_node.ip4 then
rule('FORWARD --logical-out br-client -o bat0 -p ARP --arp-ip-src ' .. next_node.ip4 .. ' -j DROP')
rule('FORWARD --logical-out br-client -o bat0 -p ARP --arp-ip-dst ' .. next_node.ip4 .. ' -j DROP')
rule('FORWARD --logical-out br-client -i bat0 -p ARP --arp-ip-src ' .. next_node.ip4 .. ' -j DROP')
rule('FORWARD --logical-out br-client -i bat0 -p ARP --arp-ip-dst ' .. next_node.ip4 .. ' -j DROP')
rule('OUTPUT --logical-out br-client -o bat0 -p ARP --arp-ip-src ' .. next_node.ip4 .. ' -j DROP')
rule('OUTPUT --logical-out br-client -o bat0 -p ARP --arp-ip-dst ' .. next_node.ip4 .. ' -j DROP')
rule('INPUT -i bat0 -p ARP --arp-ip-src ' .. next_node.ip4 .. ' -j DROP')
rule('INPUT -i bat0 -p ARP --arp-ip-dst ' .. next_node.ip4 .. ' -j DROP')
rule('FORWARD --logical-out br-client -o bat0 -p IPv4 --ip-destination ' .. next_node.ip4 .. ' -j DROP')
rule('OUTPUT --logical-out br-client -o bat0 -p IPv4 --ip-destination ' .. next_node.ip4 .. ' -j DROP')
......
......@@ -25,10 +25,6 @@ uci:section('network', 'interface', 'client', {
uci:delete('network', 'client_lan')
uci:delete('network', 'local_node_route')
uci:section('network', 'route', 'local_node_route', {
interface = 'client',
target = site.prefix4(),
})
uci:delete('network', 'local_node_route6')
uci:section('network', 'route6', 'local_node_route6', {
......
......@@ -12,7 +12,7 @@ as a separate package.
Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
diff --git a/package/base-files/Makefile b/package/base-files/Makefile
index 4fbc9a265b535d850fe812085677b3f6aabf4e1f..c971de4deee7cd331ddcad6b87eb9fefd7af6a64 100644
index 1d034fdede7598f15b1f802c47e834990e5852d9..f473ef732106eb8fa05e7c5b59df176fef33e42d 100644
--- a/package/base-files/Makefile
+++ b/package/base-files/Makefile
@@ -19,7 +19,9 @@ PKG_BUILD_DEPENDS:=usign/host
......
......@@ -64,10 +64,10 @@ index bc2fc2f774c4f2f0bbfa6e43d9b9a55e9b63153d..38cc5d7853c79f2a7800a387310a95ab
mr16|\
nbg6616|\
diff --git a/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata b/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
index b3e23c9a8f8c56870ef36fb55ae52e6b5ea61134..68f90de802ddd18e09a1da39c0d56292eea9489c 100644
index 96ca65e694bb5ed449dcae8dbca1930d25612602..fc9eb005623fc029f839d7ce14788ffba32e42e5 100644
--- a/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
+++ b/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
@@ -92,6 +92,7 @@ case "$FIRMWARE" in
@@ -98,6 +98,7 @@ case "$FIRMWARE" in
ath10kcal_extract "art" 20480 2116
ath10kcal_patch_mac $(macaddr_add $(cat /sys/class/net/eth0/address) -2)
;;
......@@ -102,7 +102,7 @@ index d2dc88127c02746cdecc4ced28f33548f35d037c..6258713dd0e3325ab109689f0ed3b51e
c-55|\
carambola2|\
diff --git a/target/linux/ar71xx/config-4.4 b/target/linux/ar71xx/config-4.4
index a8622454b421c1c74a8a71134b53c50399114aa5..e10401d42ae06506f82f2f5538fbc7df79fd4c65 100644
index 91eb9f0de7ef6c472cdccf2022d888df53b75e46..d1d879cd764259571cce2a5e091ae99f0d7a6d6d 100644
--- a/target/linux/ar71xx/config-4.4
+++ b/target/linux/ar71xx/config-4.4
@@ -51,6 +51,7 @@ CONFIG_ATH79_MACH_AP152=y
......
......@@ -9,10 +9,10 @@ Based-on-patch-by: Henryk Heisig <hyniu@o2.pl>
Signed-off-by: Andreas Ziegler <github@andreas-ziegler.de>
diff --git a/target/linux/ar71xx/config-4.4 b/target/linux/ar71xx/config-4.4
index e10401d42ae06506f82f2f5538fbc7df79fd4c65..c82fcf09228be7063967f2517e0942651234afb8 100644
index d1d879cd764259571cce2a5e091ae99f0d7a6d6d..e576fd2ec4f0a8d3613f00aa0a29586b8c65abe0 100644
--- a/target/linux/ar71xx/config-4.4
+++ b/target/linux/ar71xx/config-4.4
@@ -272,6 +272,7 @@ CONFIG_GENERIC_TIME_VSYSCALL=y
@@ -273,6 +273,7 @@ CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GPIOLIB=y
CONFIG_GPIOLIB_IRQCHIP=y
CONFIG_GPIO_DEVRES=y
......@@ -20,7 +20,7 @@ index e10401d42ae06506f82f2f5538fbc7df79fd4c65..c82fcf09228be7063967f2517e094265
# CONFIG_GPIO_LATCH is not set
CONFIG_GPIO_NXP_74HC153=y
CONFIG_GPIO_PCF857X=y
@@ -429,6 +430,7 @@ CONFIG_SOC_QCA956X=y
@@ -430,6 +431,7 @@ CONFIG_SOC_QCA956X=y
CONFIG_SPI=y
CONFIG_SPI_ATH79=y
CONFIG_SPI_BITBANG=y
......
......@@ -108,7 +108,7 @@ index 6258713dd0e3325ab109689f0ed3b51e27c41f89..774e3c8964ef724d1efbae56434aeaa9
unifiac-lite|\
unifiac-pro|\
diff --git a/target/linux/ar71xx/config-4.4 b/target/linux/ar71xx/config-4.4
index c82fcf09228be7063967f2517e0942651234afb8..57b6d2e541d7ef9dea8570ba8de72164d97b9775 100644
index e576fd2ec4f0a8d3613f00aa0a29586b8c65abe0..6da3c323d300705a29355cdccff09fce1ce1bad7 100644
--- a/target/linux/ar71xx/config-4.4
+++ b/target/linux/ar71xx/config-4.4
@@ -181,6 +181,7 @@ CONFIG_ATH79_MACH_TL_WR1041N_V2=y
......
......@@ -92,10 +92,10 @@ index 61db387c9ecefd7090c25a5f5d75fdbf65a44d65..97372bed0ea2fadfab10f22916a1e0d6
mr16|\
nbg6616|\
diff --git a/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata b/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
index 68f90de802ddd18e09a1da39c0d56292eea9489c..96b8f6b9a4bdd6a1609a819e72ade315bccfb3c0 100644
index fc9eb005623fc029f839d7ce14788ffba32e42e5..be818b78638b741fff963c222bab7c395996c608 100644
--- a/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
+++ b/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
@@ -92,6 +92,7 @@ case "$FIRMWARE" in
@@ -98,6 +98,7 @@ case "$FIRMWARE" in
ath10kcal_extract "art" 20480 2116
ath10kcal_patch_mac $(macaddr_add $(cat /sys/class/net/eth0/address) -2)
;;
......
......@@ -12,10 +12,10 @@ every C7 v4 with LEDE carries the same MAC-Address on the 5GHz WiFi.
Signed-off-by: David Bauer <mail@david-bauer.net>
diff --git a/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata b/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
index 96b8f6b9a4bdd6a1609a819e72ade315bccfb3c0..607bbd2c0ec4b59ba569550e9e0e87b80c7ddddb 100644
index be818b78638b741fff963c222bab7c395996c608..697fcb68d246aa445ce029440643ad5950e48f6d 100644
--- a/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
+++ b/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
@@ -47,6 +47,10 @@ board=$(ar71xx_board_name)
@@ -53,6 +53,10 @@ board=$(ar71xx_board_name)
case "$FIRMWARE" in
"ath10k/cal-pci-0000:00:00.0.bin")
case $board in
......@@ -26,7 +26,7 @@ index 96b8f6b9a4bdd6a1609a819e72ade315bccfb3c0..607bbd2c0ec4b59ba569550e9e0e87b8
cf-e380ac-v1|\
cf-e380ac-v2|\
dlan-pro-1200-ac|\
@@ -92,7 +96,6 @@ case "$FIRMWARE" in
@@ -98,7 +102,6 @@ case "$FIRMWARE" in
ath10kcal_extract "art" 20480 2116
ath10kcal_patch_mac $(macaddr_add $(cat /sys/class/net/eth0/address) -2)
;;
......