Skip to content
Snippets Groups Projects
  1. Aug 09, 2018
    • 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
  2. Aug 05, 2018
    • 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
    • Andreas Ziegler's avatar
  3. Jul 29, 2018
  4. Jul 22, 2018
    • 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
    • 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
  5. Jul 19, 2018
  6. Jul 14, 2018
  7. Jul 12, 2018
    • 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
  8. Jul 11, 2018
  9. Jul 08, 2018
  10. Jul 07, 2018
  11. Jul 03, 2018
  12. Jul 02, 2018
  13. Jul 01, 2018
  14. Jun 30, 2018
  15. Jun 29, 2018
  16. Jun 25, 2018
  17. Jun 24, 2018
  18. Jun 23, 2018
  19. Jun 22, 2018
  20. Jun 19, 2018
  21. Jun 17, 2018
  22. Jun 13, 2018
  23. Jun 09, 2018
Loading