Skip to content
Snippets Groups Projects
  1. Jan 15, 2022
    • Pawel Dembicki's avatar
      package: kernel: add driver module for NCT7802Y · 1ed50b92
      Pawel Dembicki authored
      
      This commit add package with hwmon-nct7802 module.
      
      This driver implements support for the Nuvoton NCT7802Y hardware monitoring
      chip. NCT7802Y supports 6 temperature sensors, 5 voltage sensors, and 3 fan
      speed sensors.
      
      Signed-off-by: default avatarPawel Dembicki <paweldembicki@gmail.com>
      (fixed c&p'ed module description)
      Signed-off-by: default avatarChristian Lamparter <chunkeey@gmail.com>
      1ed50b92
    • Joshua Roys's avatar
      ipq40xx: add support for ASUS RT-ACRH17/RT-AC42U · 51b9aef5
      Joshua Roys authored
      
      SOC:	IPQ4019
      CPU:	Quad-core ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
      DRAM:	256 MB
      NAND:	128 MiB Macronix MX30LF1G18AC
      ETH:	Qualcomm Atheros QCA8075 Gigabit Switch (4x LAN, 1x WAN)
      USB:	1x 3.0 (via Synopsys DesignWare DWC3 controller in the SoC)
      WLAN1:	Qualcomm Atheros QCA4019 2.4GHz 802.11bgn 2x2:2
      WLAN2:	Qualcomm Atheros QCA9984 5GHz 802.11nac 4x4:4
      INPUT:	1x WPS, 1x Reset
      LEDS:	Status, WIFI1, WIFI2, WAN (red & blue), 4x LAN
      
      This board is very similar to the RT-ACRH13/RT-AC58U. It must be flashed
      with an intermediary initramfs image, the jffs2 ubi volume deleted, and
      then finally a sysupgrade with the final image performed.
      
      Signed-off-by: default avatarJoshua Roys <roysjosh@gmail.com>
      (added ALT0)
      Signed-off-by: default avatarChristian Lamparter <chunkeey@gmail.com>
      51b9aef5
  2. Jan 14, 2022
  3. Jan 13, 2022
    • Paul Spooren's avatar
      iptables: enable nftable support by default · 0637093e
      Paul Spooren authored
      
      OpenWrt plans to move over to firewall4 which uses nftables under the
      hood. To allow a smooth migration the package `iptables-nft` offer a
      transparent wrapper to apply iptables rules to nftables.
      
      Without the config option for nftables the package isn't installed and
      therefore can't be tested. This commit enabled it and therefore provides
      the wrapper.
      
      The size of the iptables package increases from 25436 to 26500 Bytes.
      
      Signed-off-by: default avatarPaul Spooren <mail@aparcar.org>
      0637093e
  4. Jan 12, 2022
  5. Jan 10, 2022
  6. Jan 09, 2022
    • Sven Eckelmann's avatar
      ath79: Add support for OpenMesh OM5P-AC v1 · 97f56172
      Sven Eckelmann authored
      Device specifications:
      ======================
      
      * Qualcomm/Atheros QCA9558 ver 1 rev 0
      * 720/600/240 MHz (CPU/DDR/AHB)
      * 128 MB of RAM
      * 16 MB of SPI NOR flash
        - 2x 7 MB available; but one of the 7 MB regions is the recovery image
      * 2T2R 2.4 GHz Wi-Fi (11n)
      * 2T2R 5 GHz Wi-Fi (11ac)
      * 6x GPIO-LEDs (3x wifi, 2x ethernet, 1x power)
      * external h/w watchdog (enabled by default))
      * TTL pins are on board (arrow points to VCC, then follows: GND, TX, RX)
      * TI tmp423 (package kmod-hwmon-tmp421) for temperature monitoring
      * 2x ethernet
        - eth0
          + AR8035 ethernet PHY (RGMII)
          + 10/100/1000 Mbps Ethernet
          + 802.3af POE
          + used as LAN interface
        - eth1
          + AR8035 ethernet PHY (SGMII)
          + 10/100/1000 Mbps Ethernet
          + 18-24V passive POE (mode B)
          + used as WAN interface
      * 12-24V 1A DC
      * internal antennas
      
      Flashing instructions:
      ======================
      
      Various methods can be used to install the actual image on the flash.
      Two easy ones are:
      
      ap51-flash
      ----------
      
      The tool ap51-flash (https://github.com/ap51-flash/ap51-flash
      
      ) should be
      used to transfer the image to the u-boot when the device boots up.
      
      initramfs from TFTP
      -------------------
      
      The serial console must be used to access the u-boot shell during bootup.
      It can then be used to first boot up the initramfs image from a TFTP server
      (here with the IP 192.168.1.21):
      
         setenv serverip 192.168.1.21
         setenv ipaddr 192.168.1.1
         tftpboot 0c00000 <filename-of-initramfs-kernel>.bin && bootm $fileaddr
      
      The actual sysupgrade image can then be transferred (on the LAN port) to the
      device via
      
        scp <filename-of-squashfs-sysupgrade>.bin root@192.168.1.1:/tmp/
      
      On the device, the sysupgrade must then be started using
      
        sysupgrade -n /tmp/<filename-of-squashfs-sysupgrade>.bin
      
      Signed-off-by: default avatarSven Eckelmann <sven@narfation.org>
      97f56172
    • Sven Eckelmann's avatar
      ath79: Add support for OpenMesh OM5P-AN · 72ef5945
      Sven Eckelmann authored
      Device specifications:
      ======================
      
      * Qualcomm/Atheros AR9344 rev 2
      * 560/450/225 MHz (CPU/DDR/AHB)
      * 64 MB of RAM
      * 16 MB of SPI NOR flash
        - 2x 7 MB available; but one of the 7 MB regions is the recovery image
      * 1T1R 2.4 GHz Wi-Fi
      * 2T2R 5 GHz Wi-Fi
      * 6x GPIO-LEDs (3x wifi, 2x ethernet, 1x power)
      * 1x GPIO-button (reset)
      * external h/w watchdog (enabled by default)
      * TTL pins are on board (arrow points to VCC, then follows: GND, TX, RX)
      * TI tmp423 (package kmod-hwmon-tmp421) for temperature monitoring
      * 2x ethernet
        - eth0
          + AR8035 ethernet PHY
          + 10/100/1000 Mbps Ethernet
          + 802.3af POE
          + used as LAN interface
        - eth1
          + 10/100 Mbps Ethernet
          + builtin switch port 1
          + 18-24V passive POE (mode B)
          + used as WAN interface
      * 12-24V 1A DC
      * internal antennas
      
      Flashing instructions:
      ======================
      
      Various methods can be used to install the actual image on the flash.
      Two easy ones are:
      
      ap51-flash
      ----------
      
      The tool ap51-flash (https://github.com/ap51-flash/ap51-flash
      
      ) should be
      used to transfer the image to the u-boot when the device boots up.
      
      initramfs from TFTP
      -------------------
      
      The serial console must be used to access the u-boot shell during bootup.
      It can then be used to first boot up the initramfs image from a TFTP server
      (here with the IP 192.168.1.21):
      
         setenv serverip 192.168.1.21
         setenv ipaddr 192.168.1.1
         tftpboot 0c00000 <filename-of-initramfs-kernel>.bin && bootm $fileaddr
      
      The actual sysupgrade image can then be transferred (on the LAN port) to the
      device via
      
        scp <filename-of-squashfs-sysupgrade>.bin root@192.168.1.1:/tmp/
      
      On the device, the sysupgrade must then be started using
      
        sysupgrade -n /tmp/<filename-of-squashfs-sysupgrade>.bin
      
      Signed-off-by: default avatarSven Eckelmann <sven@narfation.org>
      72ef5945
    • Daniel Golle's avatar
      opkg: update to git HEAD of 2022-01-09 · 000825d7
      Daniel Golle authored
      
       db7fb64 libopkg: pkg_hash: prefer to-be-installed packages
       2edcfad libopkg: set 'const' attribute for argv
      
      This should fix the ImageBuilder problems people are having since we
      introduced the 'uci-firewall' providers.
      
      Signed-off-by: default avatarDaniel Golle <daniel@makrotopia.org>
      Unverified
      000825d7
    • Stijn Tintel's avatar
      firewall4: bump to git HEAD · 0f50d3da
      Stijn Tintel authored
      
       9a509d4 ruleset.uc: consolidate ip and ip6 offload
       21f311d ruleset.uc: don't trim newline before comment sign
       f121383 tests: enable flow offloading in tests
       550df40 tests: add test for unknown defaults option
       47c5a5b tests: add test for deprecated rule option
       69a89d6 tests: add test for unknown rule option
       07579df fw4.uc: handle interface zone option
      
      Signed-off-by: default avatarStijn Tintel <stijn@linux-ipv6.be>
      0f50d3da
  7. Jan 08, 2022
  8. Jan 07, 2022
  9. Jan 06, 2022
  10. Jan 05, 2022
    • Daniel Kestrel's avatar
      ltq-deu: disable arc4 algorithm · b61d756b
      Daniel Kestrel authored
      
      ARC4 was used for WEP, which is not secure anymore. Therefor it is
      disabled in the driver, but the code is not removed for now.
      
      Signed-off-by: default avatarDaniel Kestrel <kestrel1974@t-online.de>
      b61d756b
    • Daniel Kestrel's avatar
      ltq-deu: add aes_gcm algorithm · fc4d88cf
      Daniel Kestrel authored
      
      The lantiq AES hardware does not support the gcm algorithm. But it
      can be implemented in the driver as a combination of the aes_ctr
      algorithm and the xor plus gfmul operations for the hashing.
      Due to the wrapping of the several algorithms and the inefficient
      16 byte block by 16 byte block invokation in the kernel
      implementations, this driver is about 3 times faster for the larger
      block sizes.
      
      Signed-off-by: default avatarDaniel Kestrel <kestrel1974@t-online.de>
      fc4d88cf
    • Daniel Kestrel's avatar
      ltq-deu: change PKG_RELEASE to AUTORELEASE · 973e28f2
      Daniel Kestrel authored
      
      As per suggestion by adschm, PKG_RELEASE is set to AUTORELEASE.
      
      Signed-off-by: default avatarDaniel Kestrel <kestrel1974@t-online.de>
      973e28f2
    • Daniel Kestrel's avatar
      ltq-deu: remove redundant code for setting the key in aes · a0d6b09c
      Daniel Kestrel authored
      
      After adding xts and cbcmac the aes algorithm source had three sections
      for setting the aes key to the hardware which are identical.
      Method aes_set_key_hw was created which is now called from within the
      spinlock secured control sections in methods ifx_deu_aes, ifx_deu_aes_xts
      and aes_cbcmac_final_impl and reduces the size of ifxmips_aes.c.
      
      Signed-off-by: default avatarDaniel Kestrel <kestrel1974@t-online.de>
      a0d6b09c
    • Daniel Kestrel's avatar
      ltq-deu: add shash cbcmac-aes algorithm to the driver · 79efaa7f
      Daniel Kestrel authored
      
      Since commit 53b67839 hostapd is using the kernel api which includes the
      cbcmac-aes shash algorithm. The kernels implementation is a wrapper around
      the aes encryption algorithm, which encrypts block (16 bytes) by block.
      When the ltq-deu driver is present, it uses hardware aes, but every 16 byte
      encrypt requires setting the key. This is very inefficient and is a huge
      overhead. Since the cbcmac-aes is simply a hash that uses the cbc aes
      algorithm starting with an iv set to x'00' with an optional ecb aes
      encryption of a possible last incomplete block that is padded with the
      positional bytes of the last cbc encrypted block, this algorithm is now
      added to the driver. Most of the code is derived from md5-hmac and
      tailored for aes. Tested with the kernels crypto testmgr including extra
      tests against the kernels generic ccm module implementation.
      This patch also fixes the overallocation in the aes_ctx that is caused
      by using u32 instead of u8 for the aes keys.
      
      Signed-off-by: default avatarDaniel Kestrel <kestrel1974@t-online.de>
      79efaa7f
    • Daniel Kestrel's avatar
      ltq-deu: remove driver disablement for kernel 5.4 and above · f8e5c608
      Daniel Kestrel authored
      
      Remove the dependency on kernel 5.4 from the Makefile to allow the
      driver to compile with kernel 5.10 or kernel versions higher than
      5.4.
      
      Signed-off-by: default avatarDaniel Kestrel <kestrel1974@t-online.de>
      f8e5c608
    • Daniel Kestrel's avatar
      ltq-deu: add aes_xts algorithm · 43422dee
      Daniel Kestrel authored
      
      The lantiq AES hardware does not support the xts algorithm. Apart
      from the cipher text stealing (XTS), the AES XTS implementation is
      just an XOR with the IV, followed by AES ECB, followed by another
      XOR with the IV and as such can be also implemented by using the
      lantiq hardware's CBC AES implemention plus one additional XOR with
      the IV in the driver. The output IV by CBC AES is also not usable
      and the gfmul operation not supported by lantiq hardware. Both need
      to be done in the driver too in addition to the IV treatment which is
      the initial encryption by the other half of the input key and to
      set the IV to the IV registers for every block.
      In the generic kernel implementation, the block size for XTS is set
      to 16 bytes, although the algorithm is designed to process any size
      of input larger than 16 bytes. But since there is no way to
      indicate a minimum input length, the block size is used. This leads
      to certain issues when the skcipher walk functions are used, e.g.
      processing less than block size bytes is not supported by calling
      skcipher_walk_done.
      The walksize is 2 AES blocks because otherwise for splitted input
      or output data, less than blocksize is to be returned in some cases,
      which cannot be processed. Another issue was that depending on
      possible split of input/output data, just 16 bytes are returned while
      less than 16 bytes were remaining, while cipher text stealing
      requires 17 bytes or more for processing.
      For example, if the input is 60 bytes and the walk is 48, then
      processing 48 bytes leads to a return code of -EINVAL for
      skcipher_walk_done. Therefor the processed counter is used to
      figure out, when the actual cipher text stealing for the remaining
      bytes less than blocksize needs to be applied.
      Measured with cryptsetup benchmark, this XTS AES implementation is
      about 19% faster than the kernels XTS implementation that uses the
      hardware ECB AES (ca. 18.6 MiB/s vs. 15.8 MiB/s decryption 256b key).
      The implementation was tested with the kernels crypto testmgr against
      the kernels generic XTS AES implementation including extended tests.
      
      Signed-off-by: default avatarDaniel Kestrel <kestrel1974@t-online.de>
      43422dee
    • Daniel Kestrel's avatar
      ltq-deu: update initialisations for hmac algorithms · 006fee0d
      Daniel Kestrel authored
      
      The processing in the hmac algorithms depends on the status fields:
      count, dbn and started. Not all were initialised in the init method
      and after finishing the final method. Added missing fields to init
      method and call init method after finishing final.
      The memsets have the wrong size in the original driver and did not
      clear everything and are not necessary. Since no memset is done in
      the kernels generic implementation, memsets were removed.
      
      Signed-off-by: default avatarDaniel Kestrel <kestrel1974@t-online.de>
      006fee0d
    • Daniel Kestrel's avatar
      ltq-deu: remove compiler warning and shorten locked sections · 6ade9d1d
      Daniel Kestrel authored
      
      Removing hash pointer in _hmac_setkey since its not needed and causes
      a compiler warning.
      Make the spinlock control sections shorter and move initializations
      out of the control sections to free the spinlock faster for allowing
      other threads to use the hash engine.
      Minor improvements for indentation and removal of blanks and blank
      lines in some areas.
      
      Signed-off-by: default avatarDaniel Kestrel <kestrel1974@t-online.de>
      6ade9d1d
Loading