commits January 2023

commits@lists.open-mesh.org

1 participants
283 discussions

[doc] main: Merge branch 'backup-redmine/2022-04-09' (0293019d)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branch : main >--------------------------------------------------------------- commit 0293019d0b27fbc40ebf5cdf3a2f623701d200a5 Merge: 53e56385 9172f708 Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Apr 9 09:37:38 2022 +0200 Merge branch 'backup-redmine/2022-04-09' >--------------------------------------------------------------- 0293019d0b27fbc40ebf5cdf3a2f623701d200a5 devtools/Kernel_debugging_over_JTAG.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --cc devtools/Kernel_debugging_over_JTAG.rst index 65d438cc,00000000..4755fee2 mode 100644,000000..100644 --- a/devtools/Kernel_debugging_over_JTAG.rst +++ b/devtools/Kernel_debugging_over_JTAG.rst @@@ -1,402 -1,0 +1,402 @@@ +.. SPDX-License-Identifier: GPL-2.0 + +Kernel debugging over JTAG +========================== + +As shown in the :doc:`Kernel debugging with qemu's GDB server <Kernel_debugging_with_qemu\'s_GDB_server>` +documentation, it is easy to debug the Linux kernel in an +:doc:`emulated system <OpenWrt_in_QEMU>`. But some problems might only be +reproducible on actual hardware +(:doc:`connected to the emulation setup <Mixing_VM_with_gluon_hardware>`). It +is therefore sometimes necessary to debug a whole system. + +`JTAG <https://en.wikipedia.org/wiki/JTAG>`__ is a good way to get +access to the hardware state independent of the software currently +running on it. It is therefore a good choice when the used hardware +`exposes JTAG (or +SWD) <https://openwrt.org/docs/techref/hardware/port.jtag>`__ + +Requirements: + +* target board which exposes JTAG + + - `the 8devices lima + board <https://www.8devices.com/products/lima>`__ is used in this + document + +* debug adapter hardware + + - `Bus Blaster + v3 <http://dangerousprototypes.com/docs/Bus_Blaster_v3_design_overview>`__ + - Raspberry Pi��s GPIO pins of the expansion header + - `Bus + Pirate <http://dangerousprototypes.com/docs/Bus_Blaster_v3_design_overview>`__ + (really slow and not recommended) + - �� + +* On Chip Debugger for JTAG/SWD + + - `OpenOCD <http://openocd.org/>`__ + +Preparing an debug adapter hardware +----------------------------------- + +The connection between the debug adapter and the target board must +established by connecting a couple of pins with each other. The color +schema used here is from the `Sparkfun Bus Pirate +cable <https://antibore.wordpress.com/2011/06/22/quick-reference-for-sparkfun-bus-…>`__ + +The debug and target board via at least following of the debug adapter +hardware: + +* TDI (Test Data In) +* TDO (Test Data Out) +* TCK (Test Clock) +* TMS (Test Mode Select) +* GND (common ground) +* VTG (voltage reference) + +The adapter hardware must also be selected in the OpenOCD configuration. + +Only one adapter hardware must be attached. But some example +configurations are shown as reference. + +Bus Blaster adapter hardware +~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +The Bus Blaster v3 with the 20 pin header and the default buffer logic +the usage of the pins already written next to header. Just make sure to +leave the board in self powered (not closed 2 pin header) + +.. image:: jtag-busblaster.svg + +The configuration of the adapter hardware and the target board is also +straight forward since the release of OpenOCD 0.11 + +:: + + cat > jtag_debug.cfg << "EOF" + source [find interface/ftdi/dp_busblaster.cfg] + adapter speed 2000 + transport select jtag + + # in case to start debugging session without "reset halt": + # "reset halt" would be necessary here because otherwise the flash chip cannot + # be detected and the gdb attach fails with + # "Unknown flash device (ID 0x00000000)" + gdb_memory_map disable + + source [find board/8devices-lima.cfg] + EOF + +Raspberry PI (4 B) adapter hardware +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +The Raspberry PI 4B can be used as a simple adapter hardware because +there are plenty of GPIOs available and OpenOCD is able to control them +directly. Only the correctly `raw GPIO number for each +Pin <https://www.raspberrypi-spy.co.uk/2012/06/simple-guide-to-the-rpi-gpio-head…>`__ +has to be found. A good way to connect them (while keeping the SPI pins +free for reflashing SPI chips) is: + +* GND: Pin 9 +* TDO: GPIO17 (Pin 11) +* TDI: GPIO27 (Pin 13) +* TCK: GPIO22 (Pin 15) +* TMS: GPIO23 (Pin 16) + +.. image:: jtag-rpi4.svg + +The hardest part is to find the `correct base of the GPIO controller and +to set the speed settings <https://openwrt.org/toh/meraki/mr18/jtag>`__ + +The configuration of the adapter hardware and the target board is also +possible since the release of OpenOCD 0.11 + +:: + + cat > jtag_debug.cfg << "EOF" + adapter driver bcm2835gpio + + # GPIOs for: tck tms tdi tdo + bcm2835gpio_jtag_nums 22 23 27 17 + + # configuration for raspberry pi 4B + bcm2835gpio_peripheral_base 0xFE000000 + bcm2835gpio_speed_coeffs 236181 60 + + adapter speed 1000 + + transport select jtag + + # in case to start debugging session without "reset halt": + # "reset halt" would be necessary here because otherwise the flash chip cannot + # be detected and the gdb attach fails with + # "Unknown flash device (ID 0x00000000)" + gdb_memory_map disable + + source [find board/8devices-lima.cfg] + + + # allow to connect via telnet/gdb to OpenOCD from actual development machine + bindto 0.0.0.0 + EOF + +Bus Pirate adapter hardware +~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +The Bus Pirate��s SPI pins can also be used for JTAG. But it is an +extremely slow debug adapter compared to the previously mentioned ones. +For example a flash read_bank 0 flash.img 0 65536 takes 35682s when +using the 8devices lima as target board - for example, an Raspberry Pi +4B as debug adapter hardware will only need 2 minutes for the same +operations. + +Just connect: + +* TDO: MISO +* TDI: MOSI +* TMS: CS +* TCK: SCK +* GND: GND + +The configuration of the adapter hardware and the target board is also +straight forward since the release of OpenOCD 0.11 + +:: + + cat > jtag_debug.cfg << "EOF" + source [find interface/buspirate.cfg] + + buspirate_vreg 0 + buspirate_mode normal + buspirate_pullup 0 + + buspirate_port /dev/ttyUSB2 + + adapter speed 1000 + transport select jtag + + # in case to start debugging session without "reset halt": + # "reset halt" would be necessary here because otherwise the flash chip cannot + # be detected and the gdb attach fails with + # "Unknown flash device (ID 0x00000000)" + gdb_memory_map disable + + source [find board/8devices-lima.cfg] + EOF + +Preparing the 8devices lima target board +---------------------------------------- + +The board which should run the firmware must be connected to at least +following pins of the debug adapter hardware: + +- TDI (Test Data In) +- TDO (Test Data Out) +- TCK (Test Clock) +- TMS (Test Mode Select) +- GND (common ground) +- VTG (voltage reference) + +The 8devices lima reference board exposes all over its GPIO pins: + - - TDI: J2 - GPIO1 - - TDO: J2 - GPIO2 - - TCK: J2 - GPIO0 ++- TDI: J2 11 - GPIO1 ++- TDO: J2 12 - GPIO2 ++- TCK: J2 10 - GPIO0 +- TMS: J2 13 - GPIO3 +- GND: J1 16 - GND +- VTG: J1 15 - 3.3V + +.. image:: jtag-8devices-lima.svg + +Preparing OpenWrt +----------------- + +There is nearly no requirements from OpenWrt but there are several +things which can make the debugging a lot easier. + +Enable debug info +~~~~~~~~~~~~~~~~~ + +The actual configuration has to be set in the target kernel +configuration: + +:: + + CONFIG_DEBUG_INFO=y + CONFIG_DEBUG_INFO_DWARF4=y + # CONFIG_DEBUG_INFO_REDUCED is not set + CONFIG_GDB_SCRIPTS=y + +The kernel address space layout randomization complicates the resolving +of addresses of symbols. It is highly recommended to start the kernel +with the parameter ��nokaslr��. For example by adding it to CONFIG_CMDLINE +or by adjusting the bootargs in the bootloader. It should be checked in +/proc/cmdline whether it was really booted with this parameter. + +For ar71xx (8devices lima in my case), it would look like: + +.. code-block:: diff + + diff --git a/target/linux/ar71xx/config-4.14 b/target/linux/ar71xx/config-4.14 + index 9a524fae4316caa10431bd6b3b4dadbe8660f14c..397e15bcecd4e9c696a2321174969541b673cbd3 100644 + --- a/target/linux/ar71xx/config-4.14 + +++ b/target/linux/ar71xx/config-4.14 + @@ -308,10 +310,14 @@ CONFIG_CPU_SUPPORTS_MSA=y + CONFIG_CRYPTO_RNG2=y + CONFIG_CRYPTO_WORKQUEUE=y + CONFIG_CSRC_R4K=y + +CONFIG_DEBUG_INFO=y + +CONFIG_DEBUG_INFO_DWARF4=y + +# CONFIG_DEBUG_INFO_REDUCED is not set + CONFIG_DMA_NONCOHERENT=y + CONFIG_EARLY_PRINTK=y + CONFIG_ETHERNET_PACKET_MANGLE=y + CONFIG_FIXED_PHY=y + +CONFIG_GDB_SCRIPTS=y + CONFIG_GENERIC_ATOMIC64=y + CONFIG_GENERIC_CLOCKEVENTS=y + CONFIG_GENERIC_CMOS_UPDATE=y + diff --git a/target/linux/ar71xx/image/Makefile b/target/linux/ar71xx/image/Makefile + index 804532b55cb145134acf47accd095bbb24dee059..c485389f56c34ca8216c1016d515be2836ab2349 100644 + --- a/target/linux/ar71xx/image/Makefile + +++ b/target/linux/ar71xx/image/Makefile + @@ -58,7 +58,7 @@ define Device/Default + PROFILES = Default Minimal $$(DEVICE_PROFILE) + MTDPARTS := + BLOCKSIZE := 64k + - CONSOLE := ttyS0,115200 + + CONSOLE := ttyS0,115200 nokaslr + CMDLINE = $$(if $$(BOARDNAME),board=$$(BOARDNAME)) $$(if $$(MTDPARTS),mtdparts=$$(MTDPARTS)) $$(if $$(CONSOLE),console=$$(CONSOLE)) + KERNEL := kernel-bin | patch-cmdline | lzma | uImage lzma + COMPILE := + +Enabling python support for gdb +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +OpenWrt will build a gdb when CONFIG_GDB=y is set in .config. But this +version is missing python support. But it can be enabled with following +patch: + +.. code-block:: diff + + diff --git a/toolchain/gdb/Makefile b/toolchain/gdb/Makefile + index 41ba9853fd26d5ea2ba3759946a9591c668d92e9..afe4f01201fca21adc465a3fbd3c3751ec23df25 100644 + --- a/toolchain/gdb/Makefile + +++ b/toolchain/gdb/Makefile + @@ -45,7 +45,7 @@ HOST_CONFIGURE_ARGS = \ + --without-included-gettext \ + --enable-threads \ + --with-expat \ + - --without-python \ + + --with-python \ + --disable-binutils \ + --disable-ld \ + --disable-gas \ + @@ -56,9 +56,11 @@ define Host/Install + $(INSTALL_BIN) $(HOST_BUILD_DIR)/gdb/gdb $(TOOLCHAIN_DIR)/bin/$(TARGET_CROSS)gdb + ln -fs $(TARGET_CROSS)gdb $(TOOLCHAIN_DIR)/bin/$(GNU_TARGET_NAME)-gdb + strip $(TOOLCHAIN_DIR)/bin/$(TARGET_CROSS)gdb + + -$(MAKE) -C $(HOST_BUILD_DIR)/gdb/data-directory install + endef + + define Host/Clean + + -$(MAKE) -C $(HOST_BUILD_DIR)/gdb/data-directory uninstall + rm -rf \ + $(HOST_BUILD_DIR) \ + $(TOOLCHAIN_DIR)/bin/$(TARGET_CROSS)gdb \ + +It is often possible (and in case of memory access/symbol relocation +problems even recommended) to just use the normal Distro��s multiarch +gdb. This would be in Debian ��gdb-multiarch��. + +Start debugging session +----------------------- + +Starting OpenOCD +~~~~~~~~~~~~~~~~ + +The start of OpenOCD couldn��t be more trivial: + +.. code-block:: sh + + openocd -f jtag_debug.cfg + +It should start a telnet server (for manual intervention) on TCP port +4444, scan the JTAG chains and afterwards start the internal gdbserver +on port 3333. + +Connecting gdb +~~~~~~~~~~~~~~ + +I would use following folder in my ar71xx build environment but they +will be different for other architectures or OpenWrt versions: + +* ``LINUX_DIR=${OPENWRT_DIR}/build_dir/target-mips_24kc_musl/linux-ar71xx_generic/linux-4.14.236/`` +* ``GDB=${OPENWRT_DIR}/staging_dir/toolchain-mips_24kc_gcc-7.5.0_musl/bin/mips-openwrt-linux-gdb`` +* ``BATADV_DIR=${OPENWRT_DIR}/build_dir/target-mips_24kc_musl/linux-ar71xx_generic/batman-adv-2019.2/`` + +When openocd was started, we can configure gdb. It has to connect via +the local openocd gdbstub to the target device. We must change to the +LINUX_DIR first and can then start our target specific GDB with our +uncompressed kernel image. + +.. code-block:: sh + + cd "${LINUX_DIR}" + "${GDB}" -iex "set auto-load safe-path scripts/gdb/" -ex "target extended-remote localhost:3333" ./vmlinux + +The debug information for each module must be loaded using lx-symbols or +otherwise only debug information for builtin code will be accessible + +:: + + lx-symbols .. + + continue + +You should make sure that it doesn��t load any \ **.ko files from +ipkg-**\ directories. These files are stripped and doesn��t contain the +necessary symbol information. When necessary, just delete these folders +or specify the folders with the unstripped kernel modules: + +:: + + lx-symbols ../batman-adv-2019.2/.pkgdir/ ../backports-4.19.66-1/.pkgdir/ ../button-hotplug/.pkgdir/ + +The rest of the process works similar to debugging using gdbserver. Just +set some additional breakpoints and let the kernel run again. + +Some other ideas are documented in :doc:`GDB_Linux_snippets`. + +The kernel hacking debian image page should also be checked to +:ref:`increasing the chance of getting debugable modules <devtools-hacking-debian-image-building-the-batman-adv-module>` which didn��t had all +information optimized away. The relevant flags could be set directly in +the routing feed like this: + +.. code-block:: diff + + diff --git a/batman-adv/Makefile b/batman-adv/Makefile + index 967965e..0abd42f 100644 + --- a/batman-adv/Makefile + +++ b/batman-adv/Makefile + @@ -17,6 +17,9 @@ PKG_LICENSE_FILES:=LICENSES/preferred/GPL-2.0 LICENSES/preferred/MIT + + STAMP_CONFIGURED_DEPENDS := $(STAGING_DIR)/usr/include/mac80211-backport/backport/autoconf.h + + +RSTRIP:=: + +STRIP:=: + + + include $(INCLUDE_DIR)/kernel.mk + include $(INCLUDE_DIR)/package.mk + + @@ -77,7 +80,7 @@ define Build/Compile + $(KERNEL_MAKE_FLAGS) \ + M="$(PKG_BUILD_DIR)/net/batman-adv" \ + $(PKG_EXTRA_KCONFIG) \ + - EXTRA_CFLAGS="$(PKG_EXTRA_CFLAGS)" \ + + EXTRA_CFLAGS="$(PKG_EXTRA_CFLAGS) -fno-inline -Og -fno-optimize-sibling-calls" \ + NOSTDINC_FLAGS="$(NOSTDINC_FLAGS)" \ + modules + endef

1 0

[doc] backup-redmine/2022-03-12,backup-redmine/2022-04-09,backup-redmine/2022-05-07,backup-redmine/2022-06-11,backup-redmine/2022-08-06,backup-redmine/2022-10-07,backup-redmine/2022-11-14,backup-redmine/2023-01-14,main: doc: batman-adv/SubmittingLinux (025c2944)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

1 0

[doc] main: Merge branch 'backup-redmine/2022-03-12' (53e56385)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branch : main >--------------------------------------------------------------- commit 53e56385b1a89e3b638320fbade889f1505ddd73 Merge: 74dbf18c 025c2944 Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Mar 12 15:06:29 2022 +0100 Merge branch 'backup-redmine/2022-03-12' >--------------------------------------------------------------- 53e56385b1a89e3b638320fbade889f1505ddd73

1 0

[doc] backup-redmine/2022-04-09,backup-redmine/2022-05-07,backup-redmine/2022-06-11,backup-redmine/2022-08-06,backup-redmine/2022-10-07,backup-redmine/2022-11-14,backup-redmine/2023-01-14,main: doc: devtools/Kernel_debugging_over_JTAG (9172f708)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2022-04-09,backup-redmine/2022-05-07,backup-redmine/2022-06-11,backup-redmine/2022-08-06,backup-redmine/2022-10-07,backup-redmine/2022-11-14,backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit 9172f708c7e5a17b568c1fa0f00f892dcb6eaa9e Author: Sven Eckelmann <sven(a)narfation.org> Date: Thu Mar 31 11:09:41 2022 +0000 doc: devtools/Kernel_debugging_over_JTAG >--------------------------------------------------------------- 9172f708c7e5a17b568c1fa0f00f892dcb6eaa9e devtools/Kernel_debugging_over_JTAG.textile | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/devtools/Kernel_debugging_over_JTAG.textile b/devtools/Kernel_debugging_over_JTAG.textile index d245447c..8e6406bb 100644 --- a/devtools/Kernel_debugging_over_JTAG.textile +++ b/devtools/Kernel_debugging_over_JTAG.textile @@ -154,9 +154,9 @@ The board which should run the firmware must be connected to at least following The 8devices lima reference board exposes all over its GPIO pins: -* TDI: J2 - GPIO1 -* TDO: J2 - GPIO2 -* TCK: J2 - GPIO0 +* TDI: J2 11 - GPIO1 +* TDO: J2 12 - GPIO2 +* TCK: J2 10 - GPIO0 * TMS: J2 13 - GPIO3 * GND: J1 16 - GND * VTG: J1 15 - 3.3V

1 0

[doc] main: Merge branch 'backup-redmine/2022-02-12' (74dbf18c)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branch : main >--------------------------------------------------------------- commit 74dbf18cd0d3db9496d587acfdafd6b944fc9ea0 Merge: ae9a292b 2ed38e53 Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Feb 12 08:57:08 2022 +0100 Merge branch 'backup-redmine/2022-02-12' >--------------------------------------------------------------- 74dbf18cd0d3db9496d587acfdafd6b944fc9ea0 open-mesh/Download.rst | 26 ++++++++++++++------------ 1 file changed, 14 insertions(+), 12 deletions(-) diff --cc open-mesh/Download.rst index 27126488,00000000..08d6b6ec mode 100644,000000..100644 --- a/open-mesh/Download.rst +++ b/open-mesh/Download.rst @@@ -1,264 -1,0 +1,266 @@@ +.. SPDX-License-Identifier: GPL-2.0 + +Download B.A.T.M.A.N. +===================== + +We are currently working on different branches. To get the details about +the differences of these branches, see our :doc:`Branches Explained page <BranchesExplained>`. + +Please use the maint branch for your public infrastructure unless you +know exactly what you are doing and are prepared for the big unknown. + +.. _open-mesh-download-download-released-source-code: + +Download Released Source Code +----------------------------- + +- The latest version of batman-adv is - `batman-adv-2021.4.tar.gz <https://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv…>`__ - `md5 <https://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv…>`__ - `sha1 <https://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv…>`__ - `asc <https://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv…>`__ ++ `batman-adv-2022.0.tar.gz <https://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv…>`__ ++ `md5 <https://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv…>`__ ++ `sha1 <https://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv…>`__ ++ `asc <https://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv…>`__ +- The latest version of batctl (management and control tool for + batman-adv) is - `batctl-2021.4.tar.gz <https://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2021.4.…>`__ - `md5 <https://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2021.4.…>`__ - `sha1 <https://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2021.4.…>`__ - `asc <https://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2021.4.…>`__ ++ `batctl-2022.0.tar.gz <https://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2022.0.…>`__ ++ `md5 <https://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2022.0.…>`__ ++ `sha1 <https://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2022.0.…>`__ ++ `asc <https://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2022.0.…>`__ +- The latest version of alfred (Almighty Lightweight Fact Remote + Exchange Daemon) is - `alfred-2021.4.tar.gz <https://downloads.open-mesh.org/batman/stable/sources/alfred/alfred-2021.4.…>`__ - `md5 <https://downloads.open-mesh.org/batman/stable/sources/alfred/alfred-2021.4.…>`__ - `sha1 <https://downloads.open-mesh.org/batman/stable/sources/alfred/alfred-2021.4.…>`__ - `asc <https://downloads.open-mesh.org/batman/stable/sources/alfred/alfred-2021.4.…>`__ ++ `alfred-2022.0.tar.gz <https://downloads.open-mesh.org/batman/stable/sources/alfred/alfred-2022.0.…>`__ ++ `md5 <https://downloads.open-mesh.org/batman/stable/sources/alfred/alfred-2022.0.…>`__ ++ `sha1 <https://downloads.open-mesh.org/batman/stable/sources/alfred/alfred-2022.0.…>`__ ++ `asc <https://downloads.open-mesh.org/batman/stable/sources/alfred/alfred-2022.0.…>`__ + +- The latest stable version of batmand + (:ref:`unmaintained <open-mesh-BranchesExplained-batmand>`) is + `batman-0.3.2.tar.gz <https://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.t…>`__ + `md5 <https://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.t…>`__ + `sha1 <https://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.t…>`__ + `asc <https://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.t…>`__ +- The latest version of the vis server for the batmand (package not + needed for batman-adv) is + `vis-0.3.2.tar.gz <https://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.…>`__ + `md5 <https://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.…>`__ + `sha1 <https://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.…>`__ + `asc <https://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.…>`__ + +If you are wondering whether batman-adv or batmand might suit your setup +better, have a look at :doc:`this page </batman-adv/Wiki>`. Please note that +the development is focusing on batman-adv at the moment. + +To download previous release tarballs, simply check out our `download +section <https://downloads.open-mesh.org/batman/releases/>`__. + +If you find any bugs, please :doc:`let us know <Contribute>`! + +Git Repository Access +--------------------- + +Since we started integrating the batman-adv kernel module into the +mainline Linux tree, we maintain a git repository which contains the +batman-adv maintenance branches. More information can be found +:doc:`on our git page <UsingBatmanGit>`. +On overview about all the git repositories can be found on our `git +frontend <https://git.open-mesh.org>`__. We also host individual +repositories for development related to batman or meshing in general. +Feel free to contact us if you are interested in getting a repository +too. + +batman-adv in the Linux tree +---------------------------- + +Since linux 2.6.33 batman-adv is part of the official linux tree. You +can build batman-adv along with your linux binary by simply selecting +batman-adv in the Linux drivers section. If you want to have access to +the latest features on a non-bleeding edge kernel, you can clone our +git repository which still are backward compatible to all +stable/longterm kernels. + +It follows an overview of linux versions and the batman-adv version they +contain, so that you can easily pick the compatible batctl packages: + +- linux 2.6.33 => batman-adv 0.2.0 (get batctl 0.2.0 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 2.6.34 => batman-adv 0.2.1 (get batctl 0.2.1 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 2.6.35 => batman-adv 2010.0.x (get batctl 2010.0.x from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 2.6.36 => batman-adv 2010.1.x (get batctl 2010.1.x from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 2.6.37 => batman-adv 2010.2.x (get batctl 2010.2.x from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 2.6.38 => batman-adv 2011.0.x (get batctl 2011.0.x from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 2.6.39 => batman-adv 2011.1.x (get batctl 2011.1.x from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 3.0 => batman-adv 2011.2.x (get batctl 2011.2.x from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 3.1 => batman-adv 2011.3.x (get batctl 2011.3.x from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 3.2 => batman-adv 2011.4.x (get batctl 2011.4.x from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 3.3 => batman-adv 2012.0.x (get batctl 2012.0.x from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 3.4 => batman-adv 2012.1.x (get batctl 2012.1.x from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 3.5 => batman-adv 2012.2.x (get batctl 2012.2.x from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 3.6 => batman-adv 2012.3.x (get batctl 2012.3.x from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 3.7 => batman-adv 2012.4.x (get batctl 2012.4.x from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 3.8 => batman-adv 2013.0.x (get batctl 2013.0.x from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 3.9 => batman-adv 2013.1.x (get batctl 2013.1.x from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 3.10 => batman-adv 2013.2.x (get batctl 2013.2.x from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 3.11 => batman-adv 2013.3.x (get batctl 2013.3.x from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 3.12 => batman-adv 2013.4.x (get batctl 2013.4.x from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 3.13 => batman-adv 2014.0.x (get batctl 2014.0.x from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ + NOTE: in-kernel version number is 2013.5.0 +- linux 3.14 => batman-adv 2014.1.x (get batctl 2014.1.x from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 3.15 => batman-adv 2014.2.x (get batctl 2014.2.x from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 3.16 => batman-adv 2014.3.x (get batctl 2014.3.x from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 3.17-3.19 => batman-adv 2014.4.x (get batctl 2014.4.x from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 4.0-4.1 => batman-adv 2015.0 (get batctl 2015.0 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/>`__ +- linux 4.2-4.3 => batman-adv 2015.1 (get batctl 2015.1 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 4.4 => batman-adv 2015.2 (get batctl 2015.2 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 4.5 => batman-adv 2016.0 (get batctl 2016.0 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 4.6 => batman-adv 2016.1 (get batctl 2016.1 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 4.7 => batman-adv 2016.2 (get batctl 2016.2 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 4.8 => batman-adv 2016.3 (get batctl 2016.3 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 4.9 => batman-adv 2016.4 (get batctl 2016.4 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 4.10 => batman-adv 2016.5 (get batctl 2016.5 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 4.11 => batman-adv 2017.0.1 (get batctl 2017.0 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 4.12 => batman-adv 2017.1 (get batctl 2017.1 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 4.13 => batman-adv 2017.2 (get batctl 2017.2 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 4.14 => batman-adv 2017.3 (get batctl 2017.3 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 4.15 => batman-adv 2017.4 (get batctl 2017.4 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 4.16 => batman-adv 2018.0 (get batctl 2018.0 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 4.17 => batman-adv 2018.1 (get batctl 2018.1 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 4.18 => batman-adv 2018.2 (get batctl 2018.2 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 4.19 => batman-adv 2018.3 (get batctl 2018.3 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 4.20 => batman-adv 2018.4 (get batctl 2018.4 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 5.0 => batman-adv 2019.0 (get batctl 2019.0 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 5.1 => batman-adv 2019.1 (get batctl 2019.1 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 5.2 => batman-adv 2019.2 (get batctl 2019.2 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 5.3 => batman-adv 2019.3 (get batctl 2019.3 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 5.4 => batman-adv 2019.4 (get batctl 2019.4 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 5.5 => batman-adv 2019.5 (get batctl 2019.5 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 5.6 => batman-adv 2020.0 (get batctl 2020.0 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 5.7 => batman-adv 2020.1 (get batctl 2020.1 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 5.8 => batman-adv 2020.2 (get batctl 2020.2 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 5.9 => batman-adv 2020.3 (get batctl 2020.3 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 5.10 => batman-adv 2020.4 (get batctl 2020.4 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 5.11 => batman-adv 2021.0 (get batctl 2021.0 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 5.13 => batman-adv 2021.1 (get batctl 2021.1 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 5.14 => batman-adv 2021.2 (get batctl 2021.2 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 5.15 => batman-adv 2021.3 (get batctl 2021.3 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ +- linux 5.16 => batman-adv 2021.4 (get batctl 2021.4 from + `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ ++- linux 5.17 => batman-adv 2022.0 (get batctl 2022.0 from ++ `here <https://downloads.open-mesh.org/batman/stable/sources/batctl/)>`__ + +Arch Linux +---------- + +Batman-adv and Batctl are avaible in the +`AUR <https://wiki.archlinux.org/index.php/AUR>`__ as PKGBUILD: + +- `batctl <https://aur.archlinux.org/packages/batctl/>`__ - Latest + Batctl +- `batman-adv <https://aur.archlinux.org/packages/batman-adv/>`__ - + Latest Batman-adv +- `batman-adv-v14 <https://aur.archlinux.org/packages/batman-adv-v14/>`__ + - Last Batman-adv with compability-version 14 (2013.4) +- `batctl-v14 <https://aur.archlinux.org/packages/batctl-v14/>`__ - + Last Batctl with compability-version 14 (2013.4) + +Debian +------ + +Use apt-get (or any other dpkg frontend of choice) to install +B.A.T.M.A.N. onto your debian machine. Following packages are available: + +- `alfred <https://packages.debian.org/sid/alfred>`__ +- `batmand <https://packages.debian.org/sid/batmand>`__ +- `batctl <https://packages.debian.org/sid/batctl>`__ +- `linux <https://packages.debian.org/source/unstable/linux>`__ - + batman-advanced kernel module as `part of the + official <https://bugs.debian.org/622361>`__ kernel packages + +Similar packages are also available through `Ubuntu +universe <https://help.ubuntu.com/community/Repositories/Ubuntu>`__ . + +Gentoo +------ + +Use emerge to build B.A.T.M.A.N. on your gentoo machine. Following +ebuilds are available: + +- `net-misc/batctl <https://packages.gentoo.org/packages/net-misc/batctl>`__ +- `net-misc/batman-adv <https://packages.gentoo.org/packages/net-misc/batman-adv>`__ + +openSUSE +-------- + +- `network:utilities / + batctl <https://build.opensuse.org/package/show?package=batctl&project=network%3Aut…>`__ +- the batman-adv module is available as module in the official kernel + packages + +Building OpenWRT packages +------------------------- + +B.A.T.M.A.N. is also included in OpenWRT as a package. Download the +extra package feed, link the batman folder into your main OpenWRT svn +directory and use "make menuconfig" to select the B.A.T.M.A.N. flavor +you intend to use. This enables you to integrate B.A.T.M.A.N. seamlessly +into your builds (see :doc:`this page </batman-adv/Building-with-openwrt>` for +a detailed explanation). + +More information about how to build the OpenWRT toolchain is available +`here <https://wiki.openwrt.org/doc/howto/build>`__.

1 0

[doc] backup-redmine/2022-03-12,backup-redmine/2022-04-09,backup-redmine/2022-05-07,backup-redmine/2022-06-11,backup-redmine/2022-08-06,backup-redmine/2022-10-07,backup-redmine/2022-11-14,backup-redmine/2023-01-14,main: doc: batman-adv/Multicast-Packet-Type (a6f86690)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2022-03-12,backup-redmine/2022-04-09,backup-redmine/2022-05-07,backup-redmine/2022-06-11,backup-redmine/2022-08-06,backup-redmine/2022-10-07,backup-redmine/2022-11-14,backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit a6f86690513dfdc818e492c4bf07a2a3c7fb486b Author: Linus L��ssing <linus.luessing(a)c0d3.blue> Date: Thu Feb 24 23:06:25 2022 +0000 doc: batman-adv/Multicast-Packet-Type >--------------------------------------------------------------- a6f86690513dfdc818e492c4bf07a2a3c7fb486b batman-adv/Multicast-Packet-Type.textile | 102 +++++++++++++++++++++++++++++++ 1 file changed, 102 insertions(+) diff --git a/batman-adv/Multicast-Packet-Type.textile b/batman-adv/Multicast-Packet-Type.textile new file mode 100644 index 00000000..b860aa4d --- /dev/null +++ b/batman-adv/Multicast-Packet-Type.textile @@ -0,0 +1,102 @@ +h1. Multicast Packet Type + +h2. Brief + +Reduce number of packets / overhead by introducing a new batman-adv multicast packet type which is capable of holding multiple destination addresses. + +h2. Current State + +batman-adv now has IP multicast group awareness. And with that can detect in advance which other nodes want to receive an IPv4/IPv6 multicast packet for a specific multicast destination/multicast group. + +The sender algorithm so far is simply either sending a packet via one batman-adv unicast packet for each interested destination node: + +!{width: 66%;}https://www.open-mesh.org/attachments/download/888/basic-multicast-mul…! + +Or when the number of destination is larger than 16 (default, configurable) it will fall back to using a single batman-adv broadcast packet: + +!{width: 66%;}https://www.open-mesh.org/attachments/download/890/basic-multicast-man…! + +The former method is more efficient when the number of interested nodes is rather small. And allows bothering less nodes in the mesh and by that then generating less overhead in the overall mesh. However it still often leads to duplicated transmissions of the multicast IP packet especially on the first hops. + +For more details see: +* [[Multicast-optimizations]] + +h2. Technical Specification + +MCAST packet type header: + +<pre><code> 0 1 2 3 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Packet Type | Version | TTL | reserved | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | (Anonymous) Originator / MCAST Tracker-ID ... | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | ... | TVLV length | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-| + | MCAST Tracker TVLV ... | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-| + | Data ... | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +</code></pre> + +* Packet Type: BATADV_MCAST (0x05) +* Version: 15 +* TTL: +* reserved: 0x00 +* (Anonymous) Originator / Tracker-ID: 6 random bytes per (orig-addr, mcast-addr) tuple +* TVLV length: + + +MCAST Tracker TVLV: + +<pre><code> 0 1 2 3 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | TVLV Type | TVLV Version | TVLV Length | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | MCAST Address ... | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | ... | #Num Dests (N) | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Dest 1 ... | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | ... | Dest 2 ... | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | ... | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Dest N ... | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | ... | [padding] | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +</code></pre> + +* TVLV Type: + +h4. Preparations for Multicast Tracker Packets (future enhancements) + +The fields _Tracker-ID_ and _MCAST Address_ will not be used in the initial implementation of the batman-adv multicast packet type. But they are in preparation for the future enhancements where control and data plane can be separated. That is where batman-adv multicast packets can also be send without _Data_ (_Multicast Tracker Packets_) and the destinations are cached on nodes on the path. And then further batman-adv multicast packets could be send with _Data_ but with a zero length TVLV, so without the destination addresses. + +h2. Implementation Tasks + +*All nodes:* +* Signalize Multicast Packet capability to other nodes (add flag to BATADV_TVLV_MCAST) + +*Forwarding Nodes:* +* Parse Multicast Packet Type, potentially split multicast packet if multiple next hops to forward to + +*Receiving Nodes:* +* Decapsulate: Remove batman-adv multicast packet header, forward to upper interface (bat0) + +*Originating Nodes:* +# Check if all (optimization: on path) batman-adv originators support Multicast Packet Capability +# If yes, further check if number of batman-adv multicast per IP multicast packet is smaller than multicast fanout setting. So calculate MTU - sizeof(_Data_) - sizeof(multicast-packet-header) and divide by number of destinations (check Translation Table). If it exceeds multicast fanout then bail out and fall back to broadcast flooding. Otherwise continue: +# + + +TODOs: + +* 1 or 2 bytes for #Num Dests for Address X? + * If limit of entries were reached, we could just send another + mcast packet? (~6*256 = 1536). Or do we want to be prepared + for jumbo frames?

1 0

[doc] main: Merge branch 'backup-redmine/2022-01-08' (ae9a292b)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branch : main >--------------------------------------------------------------- commit ae9a292bded2d96f05c16ac3c6ca13116c108b75 Merge: 91a915be 6412768e Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Jan 8 09:08:32 2022 +0100 Merge branch 'backup-redmine/2022-01-08' >--------------------------------------------------------------- ae9a292bded2d96f05c16ac3c6ca13116c108b75 devtools/Kernel_debugging_with_kgdb.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --cc devtools/Kernel_debugging_with_kgdb.rst index b52efd6a,00000000..ada2d42b mode 100644,000000..100644 --- a/devtools/Kernel_debugging_with_kgdb.rst +++ b/devtools/Kernel_debugging_with_kgdb.rst @@@ -1,454 -1,0 +1,454 @@@ +.. SPDX-License-Identifier: GPL-2.0 + +OpenWrt KGDB +============ + +As shown in the :doc:`Kernel_debugging_with_qemu's_GDB_server` documentation, it +is easy to debug Linux kernel in an :doc:`emulated system <OpenWrt_in_QEMU>`. +But some problems might only be reproducible on actual hardware +:doc:`connected to the emulation setup <Mixing_VM_with_gluon_hardware>`. It +is therefore sometimes necessary to debug a whole system. + +In best case, the system can be :doc:`debugged using +JTAG <Kernel_debugging_over_JTAG>`. But this +is often not possible and an in-kernel gdb remote stub like +`KGDB <https://www.kernel.org/doc/html/latest/dev-tools/kgdb.html>`__ +has to be used. The only requirement it has on the actual board is a +simple serial console with poll_{get,put}_char() support. + +Preparing OpenWrt +----------------- + +Turning off watchdog +~~~~~~~~~~~~~~~~~~~~ + +Most CPUs have some kind of watchdog integrated. They can often be +turned off and are often inactive when the watchdog driver is not +loaded. For example, ath79 can be build without the internal watchdog +support by changing in ``target/linux/ath79/config-*``: + +.. code-block:: diff + + -CONFIG_ATH79_WDT=y + +# CONFIG_ATH79_WDT is not set + +Unfortunately, there are also external watchdog chips which cannot be +turned off. They have to be manually triggered regularly during the +debugging process to prevent a sudden reboot. The details depend on the +actual hardware but it often ends up in writing to a specific (GPIO +control/set/clear) register. An example how to manually trigger an GPIO +connected watchdog manually can be found in +:ref:`GDB Linux snippets <devtools-gdb-linux-snippets-Working-with-external-Watchdog-over-GPIO>` + +Enabling KGDB in kernel +~~~~~~~~~~~~~~~~~~~~~~~ + +The actual kernel gdbstub cannot be enabled via OpenWrt's .config. +Instead the actual configuration has to be set in the target +configuration: + +:: + + # CONFIG_STRICT_KERNEL_RWX is not set + CONFIG_FRAME_POINTER=y + CONFIG_KGDB=y + CONFIG_KGDB_SERIAL_CONSOLE=y + CONFIG_DEBUG_INFO=y + CONFIG_DEBUG_INFO_DWARF4=y + # CONFIG_DEBUG_INFO_REDUCED is not set + CONFIG_GDB_SCRIPTS=y + + # optional: to allow activation of kgdb over serial by agent-proxy + # instead of manually triggering it over /proc/sysrq-trigger + CONFIG_MAGIC_SYSRQ_SERIAL=y + +For x86-64, the change (mostly created using make kernel_menuconfig) +would be: + +.. code-block:: diff + + diff --git a/target/linux/x86/config-5.4 b/target/linux/x86/config-5.4 + index 6676f9501a..2518c8f57b 100644 + --- a/target/linux/x86/config-5.4 + +++ b/target/linux/x86/config-5.4 + @@ -78,6 +78,7 @@ CONFIG_COMMON_CLK=y + CONFIG_COMPAT_32=y + CONFIG_COMPAT_32BIT_TIME=y + # CONFIG_COMPAT_VDSO is not set + +CONFIG_CONSOLE_POLL=y + CONFIG_CONSOLE_TRANSLATIONS=y + # CONFIG_CPU5_WDT is not set + CONFIG_CPU_FREQ=y + @@ -116,6 +117,9 @@ CONFIG_DCACHE_WORD_ACCESS=y + # CONFIG_DCDBAS is not set + # CONFIG_DEBUG_BOOT_PARAMS is not set + # CONFIG_DEBUG_ENTRY is not set + +CONFIG_DEBUG_INFO=y + +CONFIG_DEBUG_INFO_DWARF4=y + +# CONFIG_DEBUG_INFO_REDUCED is not set + CONFIG_DEBUG_MEMORY_INIT=y + CONFIG_DEBUG_MISC=y + # CONFIG_DEBUG_NMI_SELFTEST is not set + @@ -161,6 +165,7 @@ CONFIG_FUSION=y + CONFIG_FUSION_MAX_SGE=128 + CONFIG_FUSION_SPI=y + CONFIG_FW_LOADER_PAGED_BUF=y + +CONFIG_GDB_SCRIPTS=y + CONFIG_GENERIC_ALLOCATOR=y + CONFIG_GENERIC_BUG=y + CONFIG_GENERIC_CLOCKEVENTS=y + @@ -306,6 +311,11 @@ CONFIG_KALLSYMS=y + CONFIG_KEXEC=y + CONFIG_KEXEC_CORE=y + CONFIG_KEYBOARD_ATKBD=y + +CONFIG_KGDB=y + +# CONFIG_KGDB_KDB is not set + +# CONFIG_KGDB_LOW_LEVEL_TRAP is not set + +CONFIG_KGDB_SERIAL_CONSOLE=y + +# CONFIG_KGDB_TESTS is not set + # CONFIG_LEDS_CLEVO_MAIL is not set + CONFIG_LOCK_DEBUGGING_SUPPORT=y + # CONFIG_M486 is not set + @@ -314,6 +324,8 @@ CONFIG_M586MMX=y + # CONFIG_M586TSC is not set + # CONFIG_M686 is not set + # CONFIG_MACHZ_WDT is not set + +CONFIG_MAGIC_SYSRQ=y + +CONFIG_MAGIC_SYSRQ_SERIAL=y + # CONFIG_MATOM is not set + # CONFIG_MCORE2 is not set + # CONFIG_MCRUSOE is not set + @@ -421,6 +433,7 @@ CONFIG_SCx200HR_TIMER=y + # CONFIG_SCx200_GPIO is not set + # CONFIG_SCx200_WDT is not set + CONFIG_SERIAL_8250_PCI=y + +# CONFIG_SERIAL_KGDB_NMI is not set + CONFIG_SERIO=y + CONFIG_SERIO_I8042=y + CONFIG_SERIO_LIBPS2=y + diff --git a/target/linux/x86/image/Makefile b/target/linux/x86/image/Makefile + index f61e4ff802..e8c05c58e5 100644 + --- a/target/linux/x86/image/Makefile + +++ b/target/linux/x86/image/Makefile + @@ -9,7 +9,7 @@ GRUB2_VARIANT = + GRUB_TERMINALS = + GRUB_SERIAL_CONFIG = + GRUB_TERMINAL_CONFIG = + -GRUB_CONSOLE_CMDLINE = + +GRUB_CONSOLE_CMDLINE = nokaslr + + ifneq ($(CONFIG_GRUB_CONSOLE),) + GRUB_CONSOLE_CMDLINE += console=tty0 + +For ath79 (GL.inet AR750 in my case), it would look like: + +.. code-block:: diff + + diff --git a/target/linux/ath79/config-5.4 b/target/linux/ath79/config-5.4 + index 60f57692e2..01b66897fe 100644 + --- a/target/linux/ath79/config-5.4 + +++ b/target/linux/ath79/config-5.4 + @@ -25,7 +25,7 @@ CONFIG_ARCH_WANT_DEFAULT_TOPDOWN_MMAP_LAYOUT=y + CONFIG_ARCH_WANT_IPC_PARSE_VERSION=y + CONFIG_AT803X_PHY=y + CONFIG_ATH79=y + -CONFIG_ATH79_WDT=y + +# CONFIG_ATH79_WDT is not set + CONFIG_BLK_MQ_PCI=y + CONFIG_CEVT_R4K=y + CONFIG_CLKDEV_LOOKUP=y + @@ -34,6 +34,8 @@ CONFIG_CMDLINE="rootfstype=squashfs,jffs2" + CONFIG_CMDLINE_BOOL=y + # CONFIG_CMDLINE_OVERRIDE is not set + CONFIG_COMMON_CLK=y + +CONFIG_CONSOLE_POLL=y + +CONFIG_CONSOLE_TRANSLATIONS=y + # CONFIG_COMMON_CLK_BOSTON is not set + CONFIG_COMPAT_32BIT_TIME=y + CONFIG_CPU_BIG_ENDIAN=y + @@ -52,9 +54,13 @@ CONFIG_CPU_SUPPORTS_HIGHMEM=y + CONFIG_CPU_SUPPORTS_MSA=y + CONFIG_CRYPTO_RNG2=y + CONFIG_CSRC_R4K=y + +CONFIG_DEBUG_INFO=y + +CONFIG_DEBUG_INFO_DWARF4=y + +# CONFIG_DEBUG_INFO_REDUCED is not set + CONFIG_DMA_NONCOHERENT=y + CONFIG_DMA_NONCOHERENT_CACHE_SYNC=y + CONFIG_DTC=y + +CONFIG_DUMMY_CONSOLE=y + CONFIG_EARLY_PRINTK=y + CONFIG_EFI_EARLYCON=y + CONFIG_ETHERNET_PACKET_MANGLE=y + @@ -63,6 +69,7 @@ CONFIG_FONT_8x16=y + CONFIG_FONT_AUTOSELECT=y + CONFIG_FONT_SUPPORT=y + CONFIG_FW_LOADER_PAGED_BUF=y + +CONFIG_GDB_SCRIPTS=y + CONFIG_GENERIC_ATOMIC64=y + CONFIG_GENERIC_CLOCKEVENTS=y + CONFIG_GENERIC_CMOS_UPDATE=y + @@ -132,18 +139,27 @@ CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y + CONFIG_HAVE_RSEQ=y + CONFIG_HAVE_SYSCALL_TRACEPOINTS=y + CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y + +CONFIG_HW_CONSOLE=y + CONFIG_HZ_PERIODIC=y + CONFIG_IMAGE_CMDLINE_HACK=y + CONFIG_INITRAMFS_SOURCE="" + +CONFIG_INPUT=y + CONFIG_IRQCHIP=y + CONFIG_IRQ_DOMAIN=y + CONFIG_IRQ_FORCED_THREADING=y + CONFIG_IRQ_MIPS_CPU=y + CONFIG_IRQ_WORK=y + +CONFIG_KGDB=y + +# CONFIG_KGDB_KDB is not set + +# CONFIG_KGDB_LOW_LEVEL_TRAP is not set + +CONFIG_KGDB_SERIAL_CONSOLE=y + +# CONFIG_KGDB_TESTS is not set + CONFIG_LEDS_GPIO=y + # CONFIG_LEDS_RESET is not set + CONFIG_LIBFDT=y + CONFIG_LOCK_DEBUGGING_SUPPORT=y + +CONFIG_MAGIC_SYSRQ=y + +CONFIG_MAGIC_SYSRQ_SERIAL=y + CONFIG_MDIO_BITBANG=y + CONFIG_MDIO_BUS=y + CONFIG_MDIO_DEVICE=y + @@ -161,6 +177,7 @@ CONFIG_MIPS_CLOCK_VSYSCALL=y + # CONFIG_MIPS_CMDLINE_FROM_BOOTLOADER is not set + CONFIG_MIPS_CMDLINE_FROM_DTB=y + # CONFIG_MIPS_ELF_APPENDED_DTB is not set + +CONFIG_MIPS_FP_SUPPORT=y + CONFIG_MIPS_L1_CACHE_SHIFT=5 + # CONFIG_MIPS_NO_APPENDED_DTB is not set + CONFIG_MIPS_RAW_APPENDED_DTB=y + @@ -217,6 +234,7 @@ CONFIG_RESET_ATH79=y + CONFIG_RESET_CONTROLLER=y + CONFIG_SERIAL_8250_NR_UARTS=1 + CONFIG_SERIAL_8250_RUNTIME_UARTS=1 + +# CONFIG_SERIAL_KGDB_NMI is not set + CONFIG_SERIAL_AR933X=y + CONFIG_SERIAL_AR933X_CONSOLE=y + CONFIG_SERIAL_AR933X_NR_UARTS=2 + @@ -248,3 +266,8 @@ CONFIG_TICK_CPU_ACCOUNTING=y + CONFIG_TINY_SRCU=y + CONFIG_USB_SUPPORT=y + CONFIG_USE_OF=y + +# CONFIG_VGACON_SOFT_SCROLLBACK is not set + +# CONFIG_VGA_CONSOLE is not set + +CONFIG_VT=y + +# CONFIG_VT_CONSOLE is not set + +# CONFIG_VT_HW_CONSOLE_BINDING is not set + +Enabling python support for gdb +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +OpenWrt will build a gdb when ``CONFIG_GDB=y`` is set in .config. But it is +important to also enable the python support via ``CONFIG_GDB_PYTHON=y`` or +otherwise the Linux helper will not be able to correctly scan for modules. +This feature was only added **after** the OpenWrt 21.02 release. + +For older versions of OpenWrt (including 21.02.x), following script can also be +used: + +.. code-block:: diff + + diff --git a/toolchain/gdb/Makefile b/toolchain/gdb/Makefile + index 05e3c7de3c..0ab20cb2d5 100644 + --- a/toolchain/gdb/Makefile + +++ b/toolchain/gdb/Makefile + @@ -36,7 +36,7 @@ HOST_CONFIGURE_ARGS = \ + --without-included-gettext \ + --enable-threads \ + --with-expat \ + - --without-python \ + + --with-python \ + --disable-unit-tests \ + --disable-ubsan \ + --disable-binutils \ + @@ -49,9 +49,11 @@ define Host/Install + $(INSTALL_BIN) $(HOST_BUILD_DIR)/gdb/gdb $(TOOLCHAIN_DIR)/bin/$(TARGET_CROSS)gdb + ln -fs $(TARGET_CROSS)gdb $(TOOLCHAIN_DIR)/bin/$(GNU_TARGET_NAME)-gdb + strip $(TOOLCHAIN_DIR)/bin/$(TARGET_CROSS)gdb + + -$(MAKE) -C $(HOST_BUILD_DIR)/gdb/data-directory install + endef + + define Host/Clean + + -$(MAKE) -C $(HOST_BUILD_DIR)/gdb/data-directory uninstall + rm -rf \ + $(HOST_BUILD_DIR) \ + $(TOOLCHAIN_DIR)/bin/$(TARGET_CROSS)gdb \ + +Start debugging session +----------------------- + +Turning off kASLR +~~~~~~~~~~~~~~~~~ + +The kernel address space layout randomization complicates the resolving +of addresses of symbols. It is highly recommended to start the kernel +with the parameter "nokaslr". For example by adding it to CONFIG_CMDLINE +or by adjusting the bootargs in the bootloader. It should be checked in +/proc/cmdline whether it was really booted with this parameter. + +Configure KGDB serial +~~~~~~~~~~~~~~~~~~~~~ + +The kgdb needs a serial device to work. This has to be set in the module +parameter. We assume now that the serial console on our device is ttyS0 +with baudrate 115200: + +.. code-block:: sh + + echo ttyS0,115200 > /sys/module/kgdboc/parameters/kgdboc + +Switch to kgdb +~~~~~~~~~~~~~~ + +The gdb frontend cannot directly talk to the kernel over serial and +create breakpoints. The sysrq mechanism has to be used to switch from +Linux to kgdb before gdb can be used. Under OpenWrt, this can be done +using + +.. code-block:: sh + + echo g > /proc/sysrq-trigger + +Connecting gdb +~~~~~~~~~~~~~~ + +I would use following folder in my x86-64 build environment but they +will be different for other architectures or OpenWrt versions: + +* ``LINUX_DIR=${OPENWRT_DIR}/build_dir/target-x86_64_musl/linux-x86_64/linux-5.4.143/`` +* ``GDB=${OPENWRT_DIR}/staging_dir/toolchain-x86_64_gcc-8.4.0_musl/bin/x86_64-openwrt-linux-gdb`` +* ``BATADV_DIR=${OPENWRT_DIR}/build_dir/target-x86_64_musl/linux-x86_64/batman-adv-2021.1/`` + +When kgdb is activated using sysrq, we can configure gdb. It has to +connect via a serial adapter to the target device. We must change to the +LINUX_DIR first and can then start our target specific GDB with our +uncompressed kernel image before we will connect to the remote device. + +.. code-block:: sh + + cd "${LINUX_DIR}" + "${GDB}" -iex "set auto-load safe-path scripts/gdb/" -iex "set serial baud 115200" -iex "target remote /dev/ttyUSB0" ./vmlinux + +In this example, we are using an USB TTL converter (/dev/ttyUSB0). It +has to be configured in gdb + +:: + + lx-symbols .. + + continue + +You should make sure that it doesn't load any \ **.ko files from +ipkg-**\ directories. These files are stripped and doesn't contain the +necessary symbol information. When necessary, just delete these folders +or specify the folders with the unstripped kernel modules: + +:: + + lx-symbols ../batman-adv-2021.1/.pkgdir/ ../backports-5.10.42-1/.pkgdir/ ../button-hotplug/.pkgdir/ + +The rest of the process works similar to debugging using gdbserver. Just +set some additional breakpoints and let the kernel run again. kgdb will +then inform gdb whenever a breakpoints was hit. Just keep in mind that +it is not possible to interrupt the kernel from gdb (without a Oops or +an already existing breakpoint) - use the sysrq mechanism again from +Linux to switch back to kgdb. + +Some other ideas are documented in +:doc:`GDB_Linux_snippets`. + +The kernel hacking debian image page should also be checked to +:ref:`increase the chance of getting debugable modules <devtools-hacking-debian-image-building-the-batman-adv-module>` which didn't had all +information optimized away. The relevant flags could be set directly in +the routing feed like this: + +.. code-block:: diff + + diff --git a/batman-adv/Makefile b/batman-adv/Makefile + index 967965e..0abd42f 100644 + --- a/batman-adv/Makefile + +++ b/batman-adv/Makefile + @@ -17,6 +17,9 @@ PKG_LICENSE_FILES:=LICENSES/preferred/GPL-2.0 LICENSES/preferred/MIT + + STAMP_CONFIGURED_DEPENDS := $(STAGING_DIR)/usr/include/mac80211-backport/backport/autoconf.h + + +RSTRIP:=: + +STRIP:=: + + + include $(INCLUDE_DIR)/kernel.mk + include $(INCLUDE_DIR)/package.mk + + @@ -77,7 +80,7 @@ define Build/Compile + $(KERNEL_MAKE_FLAGS) \ + M="$(PKG_BUILD_DIR)/net/batman-adv" \ + $(PKG_EXTRA_KCONFIG) \ + - EXTRA_CFLAGS="$(PKG_EXTRA_CFLAGS)" \ + + EXTRA_CFLAGS="$(PKG_EXTRA_CFLAGS) -fno-inline -Og -fno-optimize-sibling-calls" \ + NOSTDINC_FLAGS="$(NOSTDINC_FLAGS)" \ + modules + endef + +Agent-Proxy +----------- + +Instead of switching all the time between gdb and the terminal emulator +(via UART/TTL), it can be rather helpful to use a splitter which can multiplex +the kgdb and the normal terminal. So instead of using screen/minicom/... + gdb +against the tty device, the different sessions are just started against a TCP +port. + +Installation +~~~~~~~~~~~~ + +.. code-block:: shell + + $ git clone https://git.kernel.org/pub/scm/utils/kernel/kgdb/agent-proxy.git/ + $ make -C agent-proxy + +Starting up session +~~~~~~~~~~~~~~~~~~~ + +.. code-block:: shell + - $ /agent-proxy/agent-proxy '127.0.0.1:5550^127.0.0.1:5551' 0 /dev/ttyUSB0,115200 ++ $ ./agent-proxy/agent-proxy '127.0.0.1:5550^127.0.0.1:5551' 0 /dev/ttyUSB0,115200 + +To connect to the terminal session, a simple telnet or telnet-like tool +is enough: + +.. code-block:: shell + + $ screen //telnet localhost 5550 + +The setup of the kgdboc must happen exactly as described before. Including the +switch to the debugging mode via sysrq. + +The gdb has to be attached like to a remote gdb session + +.. code-block:: shell + + $ cd "${LINUX_DIR}" + $ "${GDB}" -iex "set auto-load safe-path scripts/gdb/" -iex "target remote localhost:5551" ./vmlinux + +Enable KGDB on panic +-------------------- + +Usually, a debugger catches problems like segfaults and allows a user to debug +the problem further. On modern setups with kgdb, this is not the case becaus +the system will automatically reboot after n-seconds. + +This can be avoided by changing the sysctl config ``kernel.panic`` to 0. Either +in ``/etc/sysctl.d/`` or by manually issuing + +.. code-block:: shell + + sysctl -w kernel.panic=0 + +If a kgdb(oc) is attached then it should automatically receive a message when +the Oops was noticed and can then be debugged further.

1 0

[doc] backup-redmine/2022-02-12,backup-redmine/2022-03-12,backup-redmine/2022-04-09,backup-redmine/2022-05-07,backup-redmine/2022-06-11,backup-redmine/2022-08-06,backup-redmine/2022-10-07,backup-redmine/2022-11-14,backup-redmine/2023-01-14,main: doc: open-mesh/News-draft (404b609b)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2022-02-12,backup-redmine/2022-03-12,backup-redmine/2022-04-09,backup-redmine/2022-05-07,backup-redmine/2022-06-11,backup-redmine/2022-08-06,backup-redmine/2022-10-07,backup-redmine/2022-11-14,backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit 404b609bdfc8f226303a18c82584a5ea1de9bc91 Author: Sven Eckelmann <sven(a)narfation.org> Date: Fri Jan 28 11:47:08 2022 +0000 doc: open-mesh/News-draft >--------------------------------------------------------------- 404b609bdfc8f226303a18c82584a5ea1de9bc91 open-mesh/News-draft.textile | 67 +++++++++++++++++++++++++------------------- 1 file changed, 38 insertions(+), 29 deletions(-) diff --git a/open-mesh/News-draft.textile b/open-mesh/News-draft.textile index 9dd62857..4a5ec70a 100644 --- a/open-mesh/News-draft.textile +++ b/open-mesh/News-draft.textile @@ -1,75 +1,71 @@ -h1. DRAFT: Batman-adv 2021.4 released +h1. DRAFT: Batman-adv 2022.0 released -Nov 16th, 2021. Today the B.A.T.M.A.N. team publishes the November 2021 update to batman-adv! Several code cleanups and bugfixes are included in this version. +Feb 1st, 2022. Today the B.A.T.M.A.N. team publishes the February 2022 update to batman-adv! To improve the usability in containers, batman-adv can now be controlled and monitored via netlink in unprivileged containers. alfred got more flexible in the way it is handling interfaces. The batman-adv interface can now be changed at runtime and it can be started without any interfaces. Also several code cleanups are included in this version. As the kernel module always depends on the Linux kernel it is compiled against, it does not make sense to provide binaries on our website. As usual, you will find the signed tarballs in our download section: -https://downloads.open-mesh.org/batman/releases/batman-adv-2021.4/ +https://downloads.open-mesh.org/batman/releases/batman-adv-2022.0/ h2. Thanks Thanks to all people sending in patches: -* Eric W. Biederman <ebiederm(a)xmission.com> -* Jakub Kicinski <kuba(a)kernel.org> -* Kyungrok Chung <acadx0(a)gmail.com> -* Pavel Skripkin <paskripkin(a)gmail.com> +* Linus L��ssing <linus.luessing(a)c0d3.blue> +* Marek Lindner <mareklindner(a)neomailbox.ch> +* Minghao Chi <chi.minghao(a)zte.com.cn> * Simon Wunderlich <sw(a)simonwunderlich.de> +* Sven Eckelmann <sven(a)narfation.org> h2. batman-adv <pre> $ git describe origin/master -v2021.3-11-g80822fdf -$ range=v2021.3..v2021.3-11-g80822fdf +v2021.4-7-ga2484e1a +$ range=v2021.4..v2021.4-7-ga2484e1a $ git shortlog --email --no-merges "${range}" $ git log --no-merges "${range}"|grep -e '$Reported\|Tested\|Acked\|Reviewed-by\|Co-authored-by$-by'|sed 's/.*:/*/'|sort|uniq - - - - new kernel version ================== - batman-adv: prepare for const netdev->dev_addr - batman-adv: create netdev->dev_addr assignment helpers - batman-adv: use eth_hw_addr_set() instead of ether_addr_copy() + batman-adv: compat: Fix linux/build_bug.h include for Linux 4.9.297 coding style cleanup/refactoring ================================ - batman-adv: Have kernel threads return instead of calling do_exit - batman-adv: make use of helper netif_is_bridge_master() + batman-adv: remove unneeded variable various ======= + batman-adv: allow netlink usage in unprivileged containers + bugfixes ======== - batman-adv: fix error handling + batman-adv: mcast: don't send link-local multicast to mcast routers -2021.4 (2021-11-16) +2022.0 (2021-02-01) =================== -* support latest kernels (4.4 - 5.16) +* support latest kernels (4.4 - 5.17) * coding style cleanups and refactoring +* allow netlink usage in unprivileged containers * bugs squashed: - - fix error handling during interface initialization + - don't send link-local multicast to mcast routers </pre> h2. batctl <pre> $ git describe origin/master -v2021.3-1-g2d4e026 -$ range=v2021.3..v2021.3-1-g2d4e026 +v2021.4-1-ge45cb92 +$ range=v2021.4..v2021.4-1-ge45cb92 $ git shortlog --email --no-merges "${range}" $ git log --no-merges "${range}"|grep -e '$Reported\|Tested\|Acked\|Reviewed-by\|Co-authored-by$-by'|sed 's/.*:/*/'|sort|uniq @@ -91,7 +87,7 @@ bugfixes -2021.4 (2021-11-16) +2022.0 (2021-02-01) =================== * (no changes) @@ -103,17 +99,30 @@ h2. alfred <pre> $ git describe origin/master -v2021.3-1-g34374fa -$ range=v2021.3..v2021.3-1-g34374fa +v2021.4-7-g2cca531 +$ range=v2021.4..v2021.4-7-g2cca531 $ git shortlog --email --no-merges "${range}" $ git log --no-merges "${range}"|grep -e '$Reported\|Tested\|Acked\|Reviewed-by\|Co-authored-by$-by'|sed 's/.*:/*/'|sort|uniq +Marek Lindner <mareklindner(a)neomailbox.ch> (4): + alfred: remove meaningless printf() call + alfred: introduce 'change batman-adv interface' IPC call + alfred: move interface check into helper function + alfred: Allow operating without any interface specified + +Simon Wunderlich <sw(a)simonwunderlich.de> (1): + alfred: Start new development cycle +Sven Eckelmann <sven(a)narfation.org> (2): + alfred: Avoid large send buffer for fixed size IPC commands + alfred: Simplify calculation of fixed size IPC TLV length -2021.4 (2021-11-16) +2022.0 (2021-02-01) =================== -* (no changes) +* coding style cleanups and refactoring +* allow changing of batman-adv interface at runtime +* allow to start alfred without interfaces specified </pre>

1 0

14 Jan '23

1 0

[doc] backup-redmine/2022-02-12,backup-redmine/2022-03-12,backup-redmine/2022-04-09,backup-redmine/2022-05-07,backup-redmine/2022-06-11,backup-redmine/2022-08-06,backup-redmine/2022-10-07,backup-redmine/2022-11-14,backup-redmine/2023-01-14,main: doc: open-mesh/Download (2ed38e53)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2022-02-12,backup-redmine/2022-03-12,backup-redmine/2022-04-09,backup-redmine/2022-05-07,backup-redmine/2022-06-11,backup-redmine/2022-08-06,backup-redmine/2022-10-07,backup-redmine/2022-11-14,backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit 2ed38e53c3895c21a8f5a58c8f332d1b1aa88882 Author: Simon Wunderlich <sw(a)simonwunderlich.de> Date: Thu Feb 3 18:43:52 2022 +0000 doc: open-mesh/Download >--------------------------------------------------------------- 2ed38e53c3895c21a8f5a58c8f332d1b1aa88882 open-mesh/Download.textile | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/open-mesh/Download.textile b/open-mesh/Download.textile index c7739b4e..fe30d179 100644 --- a/open-mesh/Download.textile +++ b/open-mesh/Download.textile @@ -7,9 +7,9 @@ Please use the maint branch for your public infrastructure unless you know exact h2. Download Released Source Code -* The latest version of [[batman-adv:Wiki|batman-adv]] is "batman-adv-2021.4.tar.gz":https://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv-2021.4.tar.gz "md5":https://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv-2021.4.tar.gz.md5 "sha1":https://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv-2021.4.tar.gz.sha1 "asc":https://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv-2021.4.tar.gz.asc -* The latest version of batctl (management and control tool for batman-adv) is "batctl-2021.4.tar.gz":https://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2021.4.tar.gz "md5":https://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2021.4.tar.gz.md5 "sha1":https://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2021.4.tar.gz.sha1 "asc":https://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2021.4.tar.gz.asc -* The latest version of alfred (Almighty Lightweight Fact Remote Exchange Daemon) is "alfred-2021.4.tar.gz":https://downloads.open-mesh.org/batman/stable/sources/alfred/alfred-2021.4.tar.gz "md5":https://downloads.open-mesh.org/batman/stable/sources/alfred/alfred-2021.4.tar.gz.md5 "sha1":https://downloads.open-mesh.org/batman/stable/sources/alfred/alfred-2021.4.tar.gz.sha1 "asc":https://downloads.open-mesh.org/batman/stable/sources/alfred/alfred-2021.4.tar.gz.asc +* The latest version of [[batman-adv:Wiki|batman-adv]] is "batman-adv-2022.0.tar.gz":https://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv-2022.0.tar.gz "md5":https://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv-2022.0.tar.gz.md5 "sha1":https://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv-2022.0.tar.gz.sha1 "asc":https://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv-2022.0.tar.gz.asc +* The latest version of batctl (management and control tool for batman-adv) is "batctl-2022.0.tar.gz":https://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2022.0.tar.gz "md5":https://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2022.0.tar.gz.md5 "sha1":https://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2022.0.tar.gz.sha1 "asc":https://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2022.0.tar.gz.asc +* The latest version of alfred (Almighty Lightweight Fact Remote Exchange Daemon) is "alfred-2022.0.tar.gz":https://downloads.open-mesh.org/batman/stable/sources/alfred/alfred-2022.0.tar.gz "md5":https://downloads.open-mesh.org/batman/stable/sources/alfred/alfred-2022.0.tar.gz.md5 "sha1":https://downloads.open-mesh.org/batman/stable/sources/alfred/alfred-2022.0.tar.gz.sha1 "asc":https://downloads.open-mesh.org/batman/stable/sources/alfred/alfred-2022.0.tar.gz.asc * The latest stable version of batmand ([[open-mesh:BranchesExplained#batmand|unmaintained]]) is "batman-0.3.2.tar.gz":https://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.tar.gz "md5":https://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.tar.gz.md5 "sha1":https://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.tar.gz.sha1 "asc":https://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.tar.gz.asc * The latest version of the vis server for the batmand (package not needed for batman-adv) is "vis-0.3.2.tar.gz":https://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.gz "md5":https://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.gz.md5 "sha1":https://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.gz.sha1 "asc":https://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.gz.asc @@ -93,6 +93,8 @@ It follows an overview of linux versions and the batman-adv version they contain * linux 5.14 => batman-adv 2021.2 (get batctl 2021.2 from "here":https://downloads.open-mesh.org/batman/stable/sources/batctl/) * linux 5.15 => batman-adv 2021.3 (get batctl 2021.3 from "here":https://downloads.open-mesh.org/batman/stable/sources/batctl/) * linux 5.16 => batman-adv 2021.3 +* linux 5.17 => batman-adv 2022.0 (get batctl 2022.0 from "here":https://downloads.open-mesh.org/batman/stable/sources/batctl/) + h2. Arch Linux

1 0

← Newer
1
...
9
10
11
12
13
14
15
...
29
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits January 2023