Commits on Jun 14, 2018
  1. libnfnetlink: Remove dead mirror

    diizzyy authored and dedeckeh committed Jun 11, 2018
    Remove as it's no longer available
    Signed-off-by: Daniel Engberg <>
  2. kernel: fix conntrack fixup of offloaded flows on timeout

    nbd168 committed Jun 14, 2018
    Fixes excessively long conntrack timeout of short lived connections
    Signed-off-by: Felix Fietkau <>
  3. kernel: fix conntrack leak for flow_offload connections

    nbd168 committed Jun 13, 2018
    This was caused by a race condition between offload teardown and
    conntrack gc bumping the timeout of offloaded connections
    Signed-off-by: Felix Fietkau <>
  4. kernel: allow hardware NAT offload drivers to keep a priv pointer

    nbd168 committed Apr 30, 2018
    Signed-off-by: Felix Fietkau <>
Commits on Jun 11, 2018
  1. dnsmasq: fix confdir option processing (FS#1572)

    dedeckeh committed Jun 11, 2018
    Fix condir option processing allowing to use the format
    "<directory>[,<file-extension>......]," as documented on the dnsmasq man
    page which previously resulted into bogus dir being created.
    Signed-off-by: Hans Dedecker <>
  2. base-files: sysupgrade: fix handling get_image unpack commands

    NeoRaider committed Jun 10, 2018
    On bcm53xx and brcm47xx, commands are passed to default_do_upgrade that
    expect the image to be passed on stdin, rather than as an argument.
    Fixes: 30f61a3 ("base-files: always use staged sysupgrade")
    Signed-off-by: Matthias Schiffer <>
Commits on Jun 10, 2018
  1. mac80211: rt2x00: no longer use TXOP_BACKOFF for probe frames

    dangowrt committed May 28, 2018
    Import a revert-commit from Stanislaw Gruszka which significantly
    improves WiFi performance on rt2x00 based hardware.
    Signed-off-by: Daniel Golle <>
    (cherry-picked from commit f4a639a)
Commits on Jun 9, 2018
  1. ramips: fix network config for ravpower wd03

    badzz authored and mkresin committed May 23, 2018
    This device has only one ethernet port.
    Signed-off-by: Matthias Badaire <>
    [add the existing eth0 as lan block, shorten commit message]
    Signed-off-by: Mathias Kresin <>
  2. ar71xx: use Power-LED as Diag-LED on FRITZBox 4020

    blocktrron authored and mkresin committed Jun 8, 2018
    This commit makes use of the Power-LED as Diag-LED, allowing the LED to
    work as a status indicator.
    Signed-off-by: David Bauer <>
  3. ar71xx: fix AVM package selection

    blocktrron authored and mkresin committed Jun 8, 2018
    The AVM package selection partially broke with the addition of the
    FRITZ!Box 4020. This commit restores the intended behavior.
    Signed-off-by: David Bauer <>
Commits on Jun 8, 2018
  1. mtd-utils: revert faulty upstream patch for now

    chunkeey authored and blogic committed Jun 7, 2018
    Some of the ubi-tools in the upstream mtd-utils have been
    broken by a bad patch upstream. It causes major breakage
    during sysupgrade when the kernel, rootfs, ... volumes
    are deleted in the wrong order.
    This patch therefore reverts the faulty upstream commit which
    fixes the bug.
    linux-mtd mailing-list thread:
    Cc: John Crispin <>
    Reported-by: L. Wayne Leach <>
    Signed-off-by: Christian Lamparter <>
    (cherry picked from commit daf1964)
  2. ar71xx: fix USB switch to mPCIE for Mikrotik rb91x boards

    xback authored and blogic committed Jun 7, 2018
    Some devices like the Mikrotik RB912 only have 1 USB port
    which is shared between an USB A type port, and the mini PCIe socket.
    Toggling a gpio selects the output to which USB is connected.
    Since kernel 4.9, gpio base is rounded up to a value of 32.
    Commit 65da6f9 ("ar71xx: fix secondary gpio controller base values") accounts correctly for that.
    In this commit, rb912 sees it's value changed from AR934X_GPIO_COUNT (23) to 32
    This means that the USB toggle gpio number actually also changes from 52 to 61.
    But ..
    Some of these GPIO numbers are also used in other locations, like the boardfile.
    The author forgot to also change them over there.
    Switching the USB port to mPCIe now shows my modem is correctly discovered again:
    [ 2863.864471] usb 1-1: new high-speed USB device number 4 using ehci-platform
    [ 2864.055303] usb 1-1: config 1 has an invalid interface number: 8 but max is 3
    [ 2864.062728] usb 1-1: config 1 has no interface number 1
    [ 2864.074567] qcserial 1-1:1.0: Qualcomm USB modem converter detected
    [ 2864.081474] usb 1-1: Qualcomm USB modem converter now attached to ttyUSB0
    [ 2864.111960] qcserial 1-1:1.2: Qualcomm USB modem converter detected
    [ 2864.118976] usb 1-1: Qualcomm USB modem converter now attached to ttyUSB1
    [ 2864.139808] qcserial 1-1:1.3: Qualcomm USB modem converter detected
    [ 2864.146777] usb 1-1: Qualcomm USB modem converter now attached to ttyUSB2
    [ 2864.165276] qmi_wwan 1-1:1.8: cdc-wdm0: USB WDM device
    [ 2864.171879] qmi_wwan 1-1:1.8 wwan0: register 'qmi_wwan' at usb-ehci-platform-1, WWAN/QMI device, 02:00:44:ed:3b:11
    Fixes: 65da6f9 ("ar71xx: fix secondary gpio controller base values")
    Signed-off-by: Koen Vandeputte <>
    Cc: Robin Leblon <>
    Cc: Felix Fietkau <>
    (cherry picked from commit 55b4b1e)
Commits on Jun 7, 2018
  1. busybox: udhcpc: no MSG_DONTROUTE when sending packet

    adiov authored and dedeckeh committed Jun 6, 2018
    This reverts a change made in Sep 2017 [1] which introduced
    MSG_DONTROUTE flag to prevent udhcpc from reaching out to servers on a
    different subnet. That change violates RFC2131 by forcing fully
    configured clients, who got their configurations through an offer
    relayed by a DHCP relay, from renewing through a unicast request
    directly to the DHCP server, resulting in the client resorting to
    boradcasting lease extension requests instead of unicasting them,
    further breaking RFC2131.
    The problem with MSG_DONTROUTE appears when talking to a properly
    configured DHCP server that rejects non-compliant requests. Such server
    will reject lease extension attempts sent via broadcast rather than
    unicast, as is the case with Finnish ISPs Telia and DNA as well as
    Estonian ISP Starman. Once the lease expires without renewal, udhcpc
    enters init mode, taking down the interfaces with it, and thus causing
    interruption on every lease expiry. On some ISPs (such as the ones
    mentioned above) that can be once every 10-20 minutes. The interruptions
    appear in the logs as such:
    udhcpc: sending renew to x.x.x.x
    udhcpc: send: Network unreachable
    udhcpc: sending renew to
    udhcpc: sending renew to
    udhcpc: lease lost, entering init state
    Interface 'wan' has lost the connection
    Interface 'wan' is now down
    Network alias 'eth0' link is down
    udhcpc: sending select for y.y.y.y
    udhcpc: lease of y.y.y.y obtained, lease time 1200
    Network alias 'eth0' link is up
    Interface 'wan' is now up
    During lease extension, a fully configured client should be able to
    reach out to the server from which it recieved the lease for extension,
    regardless in which network it is; that's up to the gateway to find. [2]
    This patch ensures that.
    Signed-off-by: Adi Shammout <>
    Signed-off-by: Hans Dedecker <> [PKG_RELEASE increase]
  2. logd: create log directory for log_file

    karlp authored and dedeckeh committed Feb 22, 2018
    If log_file is specified, make sure its directory exists.
    Signed-off-by: Karl Palsson <>
    Signed-off-by: Hans Dedecker <> [PKG_RELEASE increase]
  3. kernel: fix 811-pci_disable_usb_common_quirks.patch

    stintel committed Jun 7, 2018
    The kernel bump wrongly modified the patch
    Sync it from master.
    Fixes: 1199a91 ("kernel: bump 4.14 to 4.14.48 for 18.06")
    Signed-off-by: Stijn Tintel <>
  4. kernel: bump 4.14 to 4.14.48 for 18.06

    Stijn Segers authored and blogic committed Jun 5, 2018
    Refreshed patches. The following patches were upstreamed and have been deleted:
    * target/linux/lantiq/patches-4.14/0025-MIPS-lantiq-gphy-Remove-reboot-remove-reset-asserts.patch
    * target/linux/generic/pending-4.14/101-clocksource-mips-gic-timer-fix-clocksource-counter-w.patch
    * target/linux/generic/pending-4.14/103-MIPS-c-r4k-fix-data-corruption-related-to-cache-coherence.patch
    * target/linux/generic/pending-4.14/181-net-usb-add-lte-modem-wistron-neweb-d18q1.patch
    Compile-tested: ramips/mt7621, x86/64
    Run-tested: ramips/mt7621
    Signed-off-by: Stijn Segers <>
  5. kernel: bump 4.9 to 4.9.106 for 18.06

    Stijn Segers authored and blogic committed Jun 5, 2018
    Refreshed patches. The following patches were upstreamed and have been deleted:
    * target/linux/ar71xx/patches-4.9/106-01-MIPS-ath79-fix-AR724X_PLL_REG_PCIE_CONFIG-offset.patch
    * target/linux/generic/pending-4.9/180-net-phy-at803x-add-support-for-AT8032.patch
    * target/linux/generic/pending-4.9/181-net-usb-add-lte-modem-wistron-neweb-d18q1.patch
    * target/linux/generic/pending-4.9/182-net-qmi_wwan-add-BroadMobi-BM806U-2020-2033.patch
    Signed-off-by: Stijn Segers <>
Commits on Jun 6, 2018
  1. ar71xx: switch CPE/WBS 210/510 to okli-loader

    NeoRaider committed Jun 5, 2018
    We recently increased the kernel partition size of the CPE/WBS 210/510.
    This works fine for new installations of the factory image, but on
    sysupgrades, the partition table read by the bootloader is not adjusted.
    This limits the maximum size of the kernel loaded by the bootloader to the
    old partition size.
    While adjusting the partition table would be a cleanest solution, such a
    migration would have to happen before an upgrade to a new version with a
    newer kernel. This is error-prone and would require a two-step upgrade, as
    we mark the partition table partition read-only.
    Instead, switch from the lzma-loader with embedded kernel to the
    okli-loader, so only the tiny lzma-loader is loaded by the bootloader as
    "kernel", and the lzma-loader will then load the rest of the kernel by
    Fixes: e39847e ("ar71xx: increase kernel partition size for CPE/WBS 210/510")
    Signed-off-by: Matthias Schiffer <>
  2. ar71xx: make loader-okli build step more generic

    NeoRaider committed Jun 5, 2018
    Add support for different loader types.
    Signed-off-by: Matthias Schiffer <>
  3. ar71xx: lzma-loader: constify kernel argv array

    NeoRaider committed Jun 5, 2018
    By making the kernel argv array const, the .data section can always be
    omitted from the laoder binary.
    Signed-off-by: Matthias Schiffer <>
  4. ar71xx: lzma-loader: set page size to 4KB

    NeoRaider committed Jun 5, 2018
    The text section in the ELF loader is aligned to the maximum page size,
    which defaults to 64KB. Reduce it to the actual page size to avoid wasting
    flash space for this alignment.
    Signed-off-by: Matthias Schiffer <>
  5. ar71xx: lzma-loader: move padding workaround to gzip step

    NeoRaider committed Jun 6, 2018
    Some devices (TP-Link TL-WR1043ND v1) don't boot reliably when the
    uncompressed loader is too small. This was workarounded in the loader by
    adding 512KB of padding to the .data section of the loader binary.
    This approach had two issues:
    - The padding was only working when .data was non-empty (otherwise the
      section would become NOBITS, omitting it in the binary). .data was only
      empty when no CMDLINE was set, leading to further workarounds like
      fe594bf ("ath79: fix loader-okli, lzma-loader"), and this
      workaround was only effective because a missing "const" led to the kernel
      argv being stored in .data instead of .rodata
    - The padding was not only added to the compressed .gz loader, but also
      uncompressed .bin and .elf loaders. The prevented embedding the kernel
      cmdline in the loader for non-gz loader types.
    To fix both issues, move the creation of the padding from the linker script
    to the gzip step.
    Signed-off-by: Matthias Schiffer <>
  6. base-files: fix UCI config parsing and callback handling

    guidosarducci authored and dedeckeh committed Mar 8, 2018
    There are several long-standing issues present in the UCI shell API as
    documented in They
    relate both to high-level, user-defined callback functions used to
    process UCI config files, and also to low-level functions used within
    scripts generally.
    The related problems have been encountered now and in the past, e.g., and include:
    a) UCI parsing option() function and user-defined option_cb() callbacks
    being erroneously called during processing of "list" config file entries;
    b) normal usage of the low-level config_set() unexpectedy calling any
    defined option_cb() if present; and
    c) handling of the list_cb() not respecting the NO_CALLBACK variable.
    Root causes include a function stack "inversion", where the low-level
    config_set() function incorrectly calls the high-level option() function,
    intended only for processing the "option" keyword of UCI config files.
    This change addresses the inversion and other issues, making the option
    handling code more consistent and smaller, and simplifying developers'
    usage of UCI callbacks.
    Signed-off-by: Tony Ambardar <>
    Signed-off-by: Hans Dedecker <> [PKG_RELEASE increase]
Commits on Jun 5, 2018
  1. kernel: backport patch to fix dst handling for offloaded connections

    nbd168 committed Jun 5, 2018
    Signed-off-by: Felix Fietkau <>
Commits on Jun 1, 2018
  1. Revert "ramips: Move PCI driver to files directory"

    blogic committed Jun 1, 2018
    This reverts commit a098a78.
    Signed-off-by: John Crispin <>
  2. Revert "ramips: Remove redundant owner assignment"

    blogic committed Jun 1, 2018
    This reverts commit 2ad4daf.
    Signed-off-by: John Crispin <>
  3. Revert "ramips: improve interrupt mapping"

    blogic committed Jun 1, 2018
    This reverts commit 5f7396e.
    Signed-off-by: John Crispin <>
  4. Revert "ramips: remove conditional compilation."

    blogic committed Jun 1, 2018
    This reverts commit 1f78625.
    Signed-off-by: John Crispin <>
  5. Revert "ramips: remove unnecessary resource details."

    blogic committed Jun 1, 2018
    This reverts commit edea934.
    Signed-off-by: John Crispin <>
  6. Revert "ramips: pci: sync with staging driver"

    blogic committed Jun 1, 2018
    This reverts commit e07baec.
    Signed-off-by: John Crispin <>
  7. Revert "ramips: Fix WiFi after 5f7396e"

    blogic committed Jun 1, 2018
    This reverts commit 8ccdf80.
    Signed-off-by: John Crispin <>
  8. mvebu: fix broken console on WRT32X (venom)

    lantis1008 authored and blogic committed May 29, 2018
    The console bootarg is being corrupted on boot, causing various issues
    including broken sysupgrade.
    Utilising the bootargs mangle patch from other targets, hardcode the console
    arguments and fetch the rootfs from the bootloader.
    Kernel command line: console=ttyS0,115200 root=/dev/mtdblock8
    Bootloader command line (ignored): console= root=/dev/mtdblock8
    Please cherry pick to 18.06 too
    Signed-off-by: Michael Gray <>
    (cherry picked from commit 4fdc6ca)
Commits on May 31, 2018
  1. wireguard: bump to 0.0.20180531 to fix flow offloading

    zx2c4 authored and dedeckeh committed May 31, 2018
    This version bump was made upstream mostly for OpenWRT, and should fix
    an issue with a null dst when on the flow offloading path.
    While we're at it, Kevin and I are the only people actually taking care
    of this package, so trim the maintainer list a bit.
    Signed-off-by: Jason A. Donenfeld <>
Commits on May 30, 2018
  1. ramips: Use generic board detect for GnuBee devices

    neheb authored and blogic committed May 27, 2018
    This is a port of an old commit from mkresin's tree:
    This has the potential to break sysupgrade but it should be fine as
    there is no stable release of LEDE or OpenWrt that support these devices.
    Signed-off-by: Rosen Penev <>
    (cherry picked from commit 9685f39)
  2. ramips: Fix WiFi after 5f7396e

    neheb authored and blogic committed May 29, 2018
    That commit exposed a bug in the DTS files used by mt7621 where the wrong
    reg value for pcie1 (and potentially pcie2) was being used. This was
    causing WiFi failures for interfaces in pcie1.
    eg. 2.4GHz working but not 5GHz.
    As all of these dts entries are already specified in mt7621.dtsi, remove
    Signed-off-by: Rosen Penev <>
    (cherry picked from commit 02f815d)