In der Firmwarebäckerei

Bei mir sieht aktuell auch alles gut aus.
→ Experimental ?

Ich würde heute Abend noch den respondd-Patch mitreinbacken (und die kaputten mailto-Links fixen), und danach gen experimental gehen wollen.

Soll ich noch etwas testen?

Vermutlich; laß’ uns nach der MV das Thema wieder betrachten …

1.4.0~42 wurde als experimental & testing veröffentlicht.

… mein „Joy-IT JT-OR750i“ läßt sich seit Version 1.4.0~36 leider nicht mehr dazu überreden, Firmwareupdates durchzuführen. Weder mit autoupdater noch über die Config-Modus (mit ~42 versucht). :frowning:
Nachtrag: 1.4.0~36 war auch die erste Version, die ich da installiert habe.

Einen im Auslieferungszustand habe ich noch. Den teste ich mal am WE.

Cul8er
Matthias

1 Like

Hmm. Mein Mi 4A Gigabit Edition mochte nicht von 1.4.0 auf 1.5.0 sich updaten, per autoupdater hing das Teil, Download der FW nach /tmp brachte eine Fehlermeldung über einen Versionsmismatch.

Sprich: Magst Du mal ein cd /tmp ; wget $URL ; sysupgrade -v gluon-4830<TAB> beim Joy-IT probieren, vielleicht gibt das genauere Diagnostik.

That said: Joy-IT und 4A Gigabit kommen offiziell erst in Gluon v2021.1.1 (Joy-IT) bzw. v2022.1 (4A GE), die Backports in unser Gluon v2020.2.x aka 1.4.0 bergen daher natürlich die Gefahr, daß es darin noch Bugs/Inkompatibilitäten gibt. Aber von 1.4.0~36 auf 1.4.0~42 sollte das eigentlich schon tun — mach bitte mal ein dmesg | grep "ffgt@":

root@33332-Schalueckstr-107-bc62:~# dmesg | grep "ffgt@"
[    0.000000] Linux version 5.10.161 (ffgt@kaos) (mipsel-openwrt-linux-musl-gcc (OpenWrt GCC 11.2.0 r20044+10-ddeeb35007) 11.2.0, GNU ld (GNU Binutils) 2.37) #0 Wed Feb 8 17:04:11 2023

(Ältere 1.4er Builds wurden noch auf tomjon gebaut, was aber die gleiche Plattform ist (AMD Ryzen 5 3600) — unsere Intel(R) Xeon(R) E5645 im alten Buildserver colosses kauen ca. doppelt bis dreimal solange an einem Build, der auf dem Ryzen schon knapp 70 Minuten dauert.) Aber eigentlich dürfte das kein Grund sein, warum es beim Joy-IT nicht klappt.

testing: 39 von 39 online mit 1.4.0~42
experimental: 10 von 11 online mit 1.4.0~42 (1 offline: Joy-IT JT-OR750i)

Insgesamt 62 von gut 300 Knoten fahren mittlerweile 1.4.0~42 — AFAICS steht einem Push nach stable eigentlich nichts mehr im Wege?

  OS: 19.07-SNAPSHOT, r11430+26-ecbbb3    FW: 1.4.0~36
  HW: Joy-IT JT-OR750i
root@17194-Joy-IT-11b7:~# dmesg | grep "ffgt@"
[    0.000000] Linux version 4.14.275 (ffgt@tomjon) (gcc version 7.5.0 (OpenWrt GCC 7.5.0 r11430+26-ecbbb373ed)) #0 Thu May 5 15:49:05 2022
root@17194-Joy-IT-11b7:~#

Habe ich da die falsche URL erwischt?

`root@17194-Joy-IT-11b7:/tmp# wget http://fw.4830.org/firmware/experimental/sysupgrade/gluon-4830-1.4.0~42-joy-it-jt-or750i-sysupgrade.bin
Downloading 'http://fw.4830.org/firmware/experimental/sysupgrade/gluon-4830-1.4.0~42-joy-it-jt-or750i-sysupgrade.bin'
Failed to send request: Operation not permitted
root@17194-Joy-IT-11b7:/tmp# wget https://fw.4830.org/firmware/experimental/sysupgrade/gluon-4830-1.4.0~42-joy-it-jt-or750i-sysupgrade.bin
wget: SSL support not available, please install one of the libustream-.*[ssl|tls] packages as well as the ca-bundle and ca-certificates packages.
root@17194-Joy-IT-11b7:/tmp#

`

jetzt hab ich die richtige …

root@17194-Joy-IT-11b7:/tmp# wget http://firmware.ipv6.4830.org/experimental/sysupgrade/gluon-4830-1.4.0~42-joy-it-jt-or750i-sysupgrade.bin
Downloading 'http://firmware.ipv6.4830.org/experimental/sysupgrade/gluon-4830-1.4.0~42-joy-it-jt-or750i-sysupgrade.bin'
Connecting to 2a06:e881:1700:1:400:c0ff:fefb:e216:80
Writing to 'gluon-4830-1.4.0~42-joy-it-jt-or750i-sysupgrade.bin'
gluon-4830-1.4.0~42- 100% |*******************************|  7104k  0:00:00 ETA
Download completed (7275282 bytes)
root@17194-Joy-IT-11b7:/tmp# sysupgrade -v gluon-4830-1.4.0~42-joy-it-jt-or750i-sysupgrade.bin
Saving config files...
etc/config/ap-timer
etc/config/autoupdater
etc/config/autoupdater-wifi-fallback
etc/config/dhcp
etc/config/dropbear
etc/config/ffda
etc/config/ffgt
etc/config/firewall
etc/config/fstab
etc/config/gluon
etc/config/gluon-core
etc/config/gluon-node-info
etc/config/gluon-setup-mode
etc/config/gluon-wan-dnsmasq
etc/config/network
etc/config/simple-tc
etc/config/ssid-changer
etc/config/system
etc/config/tunneldigger
etc/config/ubootenv
etc/config/uhttpd
etc/config/usb-wan-hotplug
etc/config/wireless
etc/dropbear/authorized_keys
etc/dropbear/dropbear_rsa_host_key
etc/group
etc/hosts
etc/inittab
etc/opkg/keys/241deb18b2db76bd
etc/opkg/keys/2f8b0b98e08306bf
etc/opkg/keys/f94b9dd6febac963
etc/passwd
etc/profile
etc/rc.local
etc/shadow
etc/shells
etc/sysctl.conf
etc/sysupgrade.conf
lib/gluon/core/sysconfig/.keep
lib/gluon/core/sysconfig/gluon_version
lib/gluon/core/sysconfig/lan_ifname
lib/gluon/core/sysconfig/primary_mac
lib/gluon/core/sysconfig/setup_ifname
lib/gluon/core/sysconfig/wan_ifname
Commencing upgrade. Closing all shell sessions.

… aber leider noch die „FW: 1.4.0~36“

… auch mit der Version 1.5.0~39 geht kein Upgrade. :sob:

root@17194-Joy-IT-11b7:/tmp# wget http://firmware.ipv6.4830.org/tng/sysupgrade/gluon-4830-1.5.0~39-joy-it-jt-or750i-sysupgrade.bin
Downloading 'http://firmware.ipv6.4830.org/tng/sysupgrade/gluon-4830-1.5.0~39-joy-it-jt-or750i-sysupgrade.bin'
Connecting to 2a06:e881:1700:1:400:c0ff:fefb:e216:80
Writing to 'gluon-4830-1.5.0~39-joy-it-jt-or750i-sysupgrade.bin'
gluon-4830-1.5.0~39- 100% |*******************************|  8128k  0:00:00 ETA
Download completed (8323885 bytes)
root@17194-Joy-IT-11b7:/tmp# sysupgrade -v gluon-4830-1.5.0~39-joy-it-jt-or750i-sysupgrade.bin
Saving config files...
etc/config/ap-timer
etc/config/autoupdater
etc/config/autoupdater-wifi-fallback
etc/config/dhcp
etc/config/dropbear
etc/config/ffda
etc/config/ffgt
etc/config/firewall
etc/config/fstab
etc/config/gluon
etc/config/gluon-core
etc/config/gluon-node-info
etc/config/gluon-setup-mode
etc/config/gluon-wan-dnsmasq
etc/config/network
etc/config/simple-tc
etc/config/ssid-changer
etc/config/system
etc/config/tunneldigger
etc/config/ubootenv
etc/config/uhttpd
etc/config/usb-wan-hotplug
etc/config/wireless
etc/dropbear/authorized_keys
etc/dropbear/dropbear_rsa_host_key
etc/group
etc/hosts
etc/inittab
etc/opkg/keys/241deb18b2db76bd
etc/opkg/keys/2f8b0b98e08306bf
etc/opkg/keys/f94b9dd6febac963
etc/passwd
etc/profile
etc/rc.local
etc/shadow
etc/shells
etc/sysctl.conf
etc/sysupgrade.conf
lib/gluon/core/sysconfig/.keep
lib/gluon/core/sysconfig/gluon_version
lib/gluon/core/sysconfig/lan_ifname
lib/gluon/core/sysconfig/primary_mac
lib/gluon/core/sysconfig/setup_ifname
lib/gluon/core/sysconfig/wan_ifname
Commencing upgrade. Closing all shell sessions.

Nach dem Reboot …
OS: 19.07-SNAPSHOT, r11430+26-ecbbb3 FW: 1.4.0~36
HW: Joy-IT JT-OR750i

Ich werde den Knoten morgen mal komplett zurücksetzen. :man_shrugging:

Interssant.

Die Knoten können (noch; mit OpenWrt 22/Gluon v2022/unserer FW 1.5 ändert sich das IIRRC) kein SSL, die ziehen die FW per http (haben aber per signiertem Manifest ja eine Prüfsumme).

Erm. Hat der Joy-IT ggf. zwei Flash-Positionen (so wie IIRC Fritzbox 6490 und 7490)? Hmm, nö, schein’s nicht.

Vielleicht mal mit TFTP probieren?

ath79: add support for Joy-IT JT-OR750i

Specifications:
 * QCA9531, 16 MiB flash (Winbond W25Q128JVSQ), 128 MiB RAM
 * 802.11n 2T2R (external antennas)
 * QCA9887, 802.11ac 1T1R (connected with diplexer to one of the antennas)
 * 3x 10/100 LAN, 1x 10/100 WAN
 * UART header with pinout printed on PCB

Installation:
 * The device comes with a bootloader installed only
 * The bootloader offers DHCP and is reachable at http://10.123.123.1
 * Accept the agreement and flash sysupgrade.bin
 * Use Firefox if flashing does not work

TFTP recovery with static IP:
 * Rename sysupgrade.bin to jt-or750i_firmware.bin
 * Offer it via TFTP server at 192.168.0.66
 * Keep the reset button pressed for 4 seconds after connecting power

TFTP recovery with dynamic IP:
 * Rename sysupgrade.bin to jt-or750i_firmware.bin
 * Offer it via TFTP server with a DHCP server running at the same address
 * Keep the reset button pressed for 6 seconds after connecting power

EDIT: Oder mal mit der ~39 als Ausgangs-FW probieren:

Sollte dabei etwas schiefgehen, ist kein umständlicher Wiederherstellungsprozess notwendig, denn der Bootloader bemerkt den Fehler und öffnet das Webinterface erneut. Selbst wenn die Firmware noch läuft, aber ein Fehler in der Konfiguration ist, können Sie den Router in wenigen Minuten wieder betriebsbereit machen: einfach beim Einstecken des Stromsteckers den Reset-Knopf gedrückt halten und zehn Sekunden warten. Das Webinterface startet wieder und Sie können eine Firmware hochladen.

Confirmed, es gibt da wohl Probleme mit sysupgrade und dem Joy-IT OR750i:

Changelog from 2.4

TBH, ich würde dann an Deiner Stelle, @m.bitterlich, wohl direkt auf unsere, Gluon v2022.1.2-basierte, Firmware 1.5.0 gehen …

@wusel willst du die 1.4er nach „stable“ rüber schubsen? Ich habe bei meinen Produktiven Knoten keine Probleme fest stellen können nach dem Upgrade.

Es gab’ noch ein paar Änderungen, die 1.4.0 ist nun auch die Migrations-Firmware für Freifunk-Bielefeld-Knoten. Ich schiebe die aktuelle rawhide noch mal bis testing, und dann schauen wir mal.

Ok. Habe ich gemacht und funktionierte auch … 17194-Joy-IT-11b4

Ein großes Problem mit der Firmware (1.5.0~69 / gluon-v2022.1.2+) habe ich aber doch noch.
Die Knoten sind im Netzt sichtbar (Karte + SSH) können den Clients aber kein vernünftiges WLAN bieten. Entweder die Clients bekommen keine Verbindung oder wenn, dann haben sie „keinen Internetzugriff“.
Android meldet: IP-Adresse konnte nicht abgerufen werden.

Vielleicht findest Du dazu im Log etwas …

BusyBox v1.35.0 (2023-02-04 12:42:09 UTC) built-in shell (ash)

      _/_/_/_/                      _/      _/_/                      _/
     _/        _/  _/_/    _/_/          _/      _/    _/  _/_/_/    _/  _/
    _/_/_/    _/_/      _/_/_/_/  _/  _/_/_/_/  _/    _/  _/    _/  _/_/
   _/        _/        _/        _/    _/      _/    _/  _/    _/  _/  _/
  _/        _/          _/_/_/  _/    _/        _/_/_/  _/    _/  _/    _/

   Freifunk-Firmware für den Kreis Gütersloh, Bielefeld, die Müritz-Region
                     und die Feldberger Seenlandschaft

  Info/Kontakt: https://freifunk-kreisgt.de   | https://mueritz.freifunk.net
                https://freifunk-bielefeld.de | https://freifunk-feldberg.de

  Tools:
  - autoupdater -f    (Firmware-Update erzwingen)
  - batctl gwl        (Informationen zu batman-adv-Gateways anzeigen)
  - batctl o | wc -l  (Anzahl 'orginators' (Knoten) im Netz anzeigen)
  - batctl tg | wc -l (Anzahl aller Geräte im Netz anzeigen)


  OS: 22.03-SNAPSHOT, r20044+10-ddeeb3    FW: 1.5.0~69
  HW: TP-Link Archer C7 v2
root@17194-schattiger-Platz:~# logread  ...  Mist - zu lang!

Jetzt ab Aktivierung der Netzwerkkarte …

Thu Feb 23 22:28:27 2023 kern.info kernel: [   21.465772] ath10k_pci 0000:00:00.0: enabling device (0000 -> 0002)
Thu Feb 23 22:28:27 2023 kern.info kernel: [   21.472346] ath10k_pci 0000:00:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0
Thu Feb 23 22:28:27 2023 kern.info kernel: [   25.038223] ath10k_pci 0000:00:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
Thu Feb 23 22:28:27 2023 kern.info kernel: [   25.047617] ath10k_pci 0000:00:00.0: kconfig debug 1 debugfs 1 tracing 0 dfs 1 testmode 0
Thu Feb 23 22:28:27 2023 kern.info kernel: [   25.060313] ath10k_pci 0000:00:00.0: firmware ver 10.2.4-1.0-00047 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 35bd9258
Thu Feb 23 22:28:27 2023 kern.info kernel: [   25.779923] ath10k_pci 0000:00:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
Thu Feb 23 22:28:27 2023 kern.info kernel: [   26.993511] ath10k_pci 0000:00:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 cal nvmem max-sta 128 raw 0 hwcrypto 1
Thu Feb 23 22:28:27 2023 kern.debug kernel: [   27.127481] ath: EEPROM regdomain: 0x0
Thu Feb 23 22:28:27 2023 kern.debug kernel: [   27.127491] ath: EEPROM indicates default country code should be used
Thu Feb 23 22:28:27 2023 kern.debug kernel: [   27.127496] ath: doing EEPROM country->regdmn map search
Thu Feb 23 22:28:27 2023 kern.debug kernel: [   27.127508] ath: country maps to regdmn code: 0x3a
Thu Feb 23 22:28:27 2023 kern.debug kernel: [   27.127514] ath: Country alpha2 being used: US
Thu Feb 23 22:28:27 2023 kern.debug kernel: [   27.127519] ath: Regpair used: 0x3a
Thu Feb 23 22:28:27 2023 kern.info kernel: [   27.297004] batman_adv: B.A.T.M.A.N. advanced 2022.0-openwrt-7 (compatibility version 15) loaded
Thu Feb 23 22:28:27 2023 kern.debug kernel: [   27.329328] ath: EEPROM regdomain: 0x0
Thu Feb 23 22:28:27 2023 kern.debug kernel: [   27.329339] ath: EEPROM indicates default country code should be used
Thu Feb 23 22:28:27 2023 kern.debug kernel: [   27.329344] ath: doing EEPROM country->regdmn map search
Thu Feb 23 22:28:27 2023 kern.debug kernel: [   27.329357] ath: country maps to regdmn code: 0x3a
Thu Feb 23 22:28:27 2023 kern.debug kernel: [   27.329363] ath: Country alpha2 being used: US
Thu Feb 23 22:28:27 2023 kern.debug kernel: [   27.329367] ath: Regpair used: 0x3a
Thu Feb 23 22:28:27 2023 kern.debug kernel: [   27.346277] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
Thu Feb 23 22:28:27 2023 kern.info kernel: [   27.348016] ieee80211 phy1: Atheros AR9550 Rev:0 mem=0xb8100000, irq=12
Thu Feb 23 22:28:27 2023 user.info kernel: [   27.360121] kmodloader: done loading kernel modules from /etc/modules.d/*
Thu Feb 23 22:28:29 2023 daemon.info dnsmasq[1]: started, version 2.86 cachesize 150
Thu Feb 23 22:28:29 2023 daemon.info dnsmasq[1]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile
Thu Feb 23 22:28:29 2023 daemon.info dnsmasq[1]: UBus support enabled: connected to system bus
Thu Feb 23 22:28:29 2023 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Thu Feb 23 22:28:29 2023 daemon.warn dnsmasq[1]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Thu Feb 23 22:28:29 2023 daemon.info dnsmasq[1]: read /etc/hosts - 4 addresses
Thu Feb 23 22:28:29 2023 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses
Thu Feb 23 22:28:29 2023 authpriv.info dropbear[1541]: Not backgrounding
Thu Feb 23 22:28:35 2023 daemon.err gluon-arp-limiter[1825]: Error - interface bat0 is not present or not a batman-adv interface
Thu Feb 23 22:28:36 2023 daemon.err gluon-arp-limiter[1825]: Error - interface bat0 is not present or not a batman-adv interface
Thu Feb 23 22:28:37 2023 user.notice : Added device handler type: bonding
Thu Feb 23 22:28:37 2023 user.notice : Added device handler type: 8021ad
Thu Feb 23 22:28:37 2023 user.notice : Added device handler type: 8021q
Thu Feb 23 22:28:37 2023 user.notice : Added device handler type: macvlan
Thu Feb 23 22:28:37 2023 user.notice : Added device handler type: veth
Thu Feb 23 22:28:37 2023 user.notice : Added device handler type: bridge
Thu Feb 23 22:28:37 2023 user.notice : Added device handler type: Network device
Thu Feb 23 22:28:37 2023 user.notice : Added device handler type: tunnel
Thu Feb 23 22:28:42 2023 kern.info kernel: [   45.018416] eth1: link up (1000Mbps/Full duplex)
Thu Feb 23 22:28:42 2023 kern.info kernel: [   45.023127] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Thu Feb 23 22:28:42 2023 kern.info kernel: [   45.033968] br-client: port 1(eth1.1) entered blocking state
Thu Feb 23 22:28:42 2023 kern.info kernel: [   45.039766] br-client: port 1(eth1.1) entered disabled state
Thu Feb 23 22:28:42 2023 kern.info kernel: [   45.045762] device eth1.1 entered promiscuous mode
Thu Feb 23 22:28:42 2023 kern.info kernel: [   45.050662] device eth1 entered promiscuous mode
Thu Feb 23 22:28:42 2023 kern.info kernel: [   45.113578] br-client: port 1(eth1.1) entered blocking state
Thu Feb 23 22:28:42 2023 kern.info kernel: [   45.119372] br-client: port 1(eth1.1) entered forwarding state
Thu Feb 23 22:28:42 2023 daemon.notice netifd: Interface 'client' is enabled
Thu Feb 23 22:28:42 2023 user.notice sysctl: net.ipv6.conf.br-client.forwarding = 0
Thu Feb 23 22:28:42 2023 daemon.notice netifd: bridge 'br-client' link is up
Thu Feb 23 22:28:42 2023 daemon.notice netifd: Interface 'client' has link connectivity
Thu Feb 23 22:28:42 2023 daemon.notice netifd: Interface 'client' is setting up now
Thu Feb 23 22:28:43 2023 kern.info kernel: [   45.951472] eth0: link up (1000Mbps/Full duplex)
Thu Feb 23 22:28:43 2023 kern.info kernel: [   45.956449] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Thu Feb 23 22:28:43 2023 kern.info kernel: [   45.984600] br-wan: port 1(eth0.2) entered blocking state
Thu Feb 23 22:28:43 2023 kern.info kernel: [   45.990213] br-wan: port 1(eth0.2) entered disabled state
Thu Feb 23 22:28:43 2023 kern.info kernel: [   46.026995] device eth0.2 entered promiscuous mode
Thu Feb 23 22:28:43 2023 kern.info kernel: [   46.031866] device eth0 entered promiscuous mode
Thu Feb 23 22:28:43 2023 kern.info kernel: [   46.056591] IPv6: ADDRCONF(NETDEV_CHANGE): br-client: link becomes ready
Thu Feb 23 22:28:43 2023 kern.info kernel: [   46.100284] br-wan: port 1(eth0.2) entered blocking state
Thu Feb 23 22:28:43 2023 kern.info kernel: [   46.105771] br-wan: port 1(eth0.2) entered forwarding state
Thu Feb 23 22:28:43 2023 daemon.notice netifd: Interface 'wan' is enabled
Thu Feb 23 22:28:43 2023 daemon.notice netifd: Interface 'wan6' is enabled
Thu Feb 23 22:28:43 2023 daemon.notice netifd: bridge 'br-wan' link is up
Thu Feb 23 22:28:43 2023 daemon.notice netifd: Interface 'wan' has link connectivity
Thu Feb 23 22:28:43 2023 daemon.notice netifd: Interface 'wan' is setting up now
Thu Feb 23 22:28:43 2023 daemon.notice netifd: Interface 'wan6' has link connectivity
Thu Feb 23 22:28:43 2023 daemon.notice netifd: Interface 'wan6' is setting up now
Thu Feb 23 22:28:43 2023 daemon.notice netifd: VLAN 'eth1.1' link is up
Thu Feb 23 22:28:43 2023 daemon.notice netifd: Interface 'local_node' is enabled
Thu Feb 23 22:28:43 2023 daemon.notice netifd: Interface 'local_node' is setting up now
Thu Feb 23 22:28:43 2023 daemon.notice netifd: Interface 'local_node' is now up
Thu Feb 23 22:28:43 2023 daemon.notice netifd: Interface 'gluon_bat0' is setting up now
Thu Feb 23 22:28:43 2023 daemon.notice netifd: Interface 'loopback' is enabled
Thu Feb 23 22:28:43 2023 daemon.notice netifd: Interface 'loopback' is setting up now
Thu Feb 23 22:28:43 2023 daemon.notice netifd: Interface 'loopback' is now up
Thu Feb 23 22:28:43 2023 kern.info kernel: [   46.365605] IPv6: ADDRCONF(NETDEV_CHANGE): local-node: link becomes ready
Thu Feb 23 22:28:43 2023 daemon.err odhcp6c[2211]: Failed to send RS (Address not available)
Thu Feb 23 22:28:43 2023 kern.info kernel: [   46.438084] br-client: port 2(local-port) entered blocking state
Thu Feb 23 22:28:43 2023 kern.info kernel: [   46.444192] br-client: port 2(local-port) entered disabled state
Thu Feb 23 22:28:43 2023 kern.info kernel: [   46.663654] device local-port entered promiscuous mode
Thu Feb 23 22:28:43 2023 kern.info kernel: [   46.669126] br-client: port 2(local-port) entered blocking state
Thu Feb 23 22:28:43 2023 kern.info kernel: [   46.675227] br-client: port 2(local-port) entered forwarding state
Thu Feb 23 22:28:43 2023 daemon.err odhcp6c[2211]: Failed to send SOLICIT message to ff02::1:2 (Address not available)
Thu Feb 23 22:28:44 2023 daemon.notice netifd: Network device 'eth1' link is up
Thu Feb 23 22:28:44 2023 kern.info kernel: [   47.066357] IPv6: ADDRCONF(NETDEV_CHANGE): br-wan: link becomes ready
Thu Feb 23 22:28:44 2023 daemon.notice netifd: Network device 'eth0' link is up
Thu Feb 23 22:28:44 2023 daemon.notice netifd: VLAN 'eth0.2' link is up
Thu Feb 23 22:28:44 2023 daemon.notice netifd: Network device 'local-port' link is up
Thu Feb 23 22:28:44 2023 daemon.notice netifd: veth 'local-node' link is up
Thu Feb 23 22:28:44 2023 daemon.notice netifd: Interface 'local_node' has link connectivity
Thu Feb 23 22:28:44 2023 daemon.notice netifd: Network device 'lo' link is up
Thu Feb 23 22:28:44 2023 daemon.notice netifd: Interface 'loopback' has link connectivity
Thu Feb 23 22:28:44 2023 daemon.notice netifd: wan (2270): udhcpc: started, v1.35.0
Thu Feb 23 22:28:44 2023 daemon.err odhcp6c[2272]: Failed to send RS (Address not available)
Thu Feb 23 22:28:44 2023 daemon.err odhcp6c[2211]: Failed to send SOLICIT message to ff02::1:2 (Address not available)
Thu Feb 23 22:28:44 2023 daemon.err odhcp6c[2272]: Failed to send SOLICIT message to ff02::1:2 (Address not available)
Thu Feb 23 22:28:46 2023 user.notice sysctl: net.ipv6.conf.local-node.forwarding = 0
Thu Feb 23 22:28:46 2023 daemon.notice netifd: wan (2270): udhcpc: broadcasting discover
Thu Feb 23 22:28:47 2023 kern.info kernel: [   49.955650] 8021q: adding VLAN 0 to HW filter on device bat0
Thu Feb 23 22:28:47 2023 daemon.notice netifd: Interface 'bat0' is enabled
Thu Feb 23 22:28:47 2023 kern.info kernel: [   49.995958] br-client: port 3(bat0) entered blocking state
Thu Feb 23 22:28:47 2023 kern.info kernel: [   50.001577] br-client: port 3(bat0) entered disabled state
Thu Feb 23 22:28:47 2023 kern.info kernel: [   50.007428] device bat0 entered promiscuous mode
Thu Feb 23 22:28:47 2023 kern.info kernel: [   50.012222] br-client: port 3(bat0) entered blocking state
Thu Feb 23 22:28:47 2023 kern.info kernel: [   50.017830] br-client: port 3(bat0) entered forwarding state
Thu Feb 23 22:28:47 2023 daemon.notice netifd: Network device 'bat0' link is up
Thu Feb 23 22:28:47 2023 daemon.notice netifd: Interface 'bat0' has link connectivity
Thu Feb 23 22:28:47 2023 daemon.notice netifd: Interface 'bat0' is setting up now
Thu Feb 23 22:28:47 2023 daemon.notice netifd: Interface 'bat0' is now up
Thu Feb 23 22:28:47 2023 kern.info kernel: [   50.456272] batman_adv: bat0: No IGMP Querier present - multicast optimizations disabled
Thu Feb 23 22:28:47 2023 kern.info kernel: [   50.464486] batman_adv: bat0: No MLD Querier present - multicast optimizations disabled
Thu Feb 23 22:28:47 2023 user.notice firewall: Reloading firewall due to ifup of local_node (local-node)
Thu Feb 23 22:28:49 2023 daemon.notice netifd: wan (2270): udhcpc: broadcasting discover
Thu Feb 23 22:28:49 2023 daemon.err odhcp6c[2211]: Failed to send SOLICIT message to ff02::1:2 (Operation not permitted)
Thu Feb 23 22:28:50 2023 kern.debug kernel: [   53.394882] ath: EEPROM regdomain: 0x8114
Thu Feb 23 22:28:50 2023 kern.debug kernel: [   53.394893] ath: EEPROM indicates we should expect a country code
Thu Feb 23 22:28:50 2023 kern.debug kernel: [   53.394899] ath: doing EEPROM country->regdmn map search
Thu Feb 23 22:28:50 2023 kern.debug kernel: [   53.394905] ath: country maps to regdmn code: 0x37
Thu Feb 23 22:28:50 2023 kern.debug kernel: [   53.394911] ath: Country alpha2 being used: DE
Thu Feb 23 22:28:50 2023 kern.debug kernel: [   53.394916] ath: Regpair used: 0x37
Thu Feb 23 22:28:50 2023 kern.debug kernel: [   53.394922] ath: regdomain 0x8114 dynamically updated by user
Thu Feb 23 22:28:50 2023 kern.debug kernel: [   53.395005] ath: EEPROM regdomain: 0x8114
Thu Feb 23 22:28:50 2023 kern.debug kernel: [   53.395009] ath: EEPROM indicates we should expect a country code
Thu Feb 23 22:28:50 2023 kern.debug kernel: [   53.395014] ath: doing EEPROM country->regdmn map search
Thu Feb 23 22:28:50 2023 kern.debug kernel: [   53.395019] ath: country maps to regdmn code: 0x37
Thu Feb 23 22:28:50 2023 kern.debug kernel: [   53.395023] ath: Country alpha2 being used: DE
Thu Feb 23 22:28:50 2023 kern.debug kernel: [   53.395028] ath: Regpair used: 0x37
Thu Feb 23 22:28:50 2023 kern.debug kernel: [   53.395033] ath: regdomain 0x8114 dynamically updated by user
Thu Feb 23 22:28:51 2023 kern.info kernel: [   53.960920] batman_adv: bat0: Adding interface: primary0
Thu Feb 23 22:28:51 2023 kern.info kernel: [   53.966363] batman_adv: bat0: Interface activated: primary0
Thu Feb 23 22:28:51 2023 kern.info kernel: [   54.208646] batman_adv: bat0: Interface deactivated: primary0
Thu Feb 23 22:28:51 2023 kern.info kernel: [   54.260052] batman_adv: bat0: Interface activated: primary0
Thu Feb 23 22:28:51 2023 daemon.notice netifd: Interface 'gluon_bat0' is now up
Thu Feb 23 22:28:51 2023 daemon.notice netifd: Network device 'primary0' link is up
Thu Feb 23 22:28:52 2023 kern.info kernel: [   55.066292] batman_adv: bat0: IGMP Querier appeared
Thu Feb 23 22:28:52 2023 kern.info kernel: [   55.071251] batman_adv: bat0: MLD Querier appeared
Thu Feb 23 22:28:52 2023 daemon.notice netifd: wan (2270): udhcpc: broadcasting discover
Thu Feb 23 22:28:53 2023 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy1.conf (phy client1) --> new PHY
Thu Feb 23 22:28:53 2023 daemon.info dnsmasq[2957]: started, version 2.86 cachesize 150
Thu Feb 23 22:28:53 2023 daemon.info dnsmasq[2957]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile
Thu Feb 23 22:28:53 2023 daemon.warn dnsmasq[2957]: no servers found in /var/gluon/wan-dnsmasq/resolv.conf, will retry
Thu Feb 23 22:28:53 2023 daemon.info dnsmasq[2957]: cleared cache
Thu Feb 23 22:28:54 2023 kern.info kernel: [   57.022375] br-client: port 4(client1) entered blocking state
Thu Feb 23 22:28:54 2023 kern.info kernel: [   57.028253] br-client: port 4(client1) entered disabled state
Thu Feb 23 22:28:54 2023 kern.info kernel: [   57.034389] device client1 entered promiscuous mode
Thu Feb 23 22:28:54 2023 daemon.notice hostapd: client1: interface state UNINITIALIZED->COUNTRY_UPDATE
Thu Feb 23 22:28:54 2023 kern.info kernel: [   57.170080] IPv6: ADDRCONF(NETDEV_CHANGE): client1: link becomes ready
Thu Feb 23 22:28:54 2023 kern.info kernel: [   57.176923] br-client: port 4(client1) entered blocking state
Thu Feb 23 22:28:54 2023 kern.info kernel: [   57.182760] br-client: port 4(client1) entered forwarding state
Thu Feb 23 22:28:54 2023 daemon.notice procd: /etc/rc.d/S90tunneldigger: Not starting tunneldigger - missing uuid
Thu Feb 23 22:28:54 2023 daemon.notice hostapd: client1: interface state COUNTRY_UPDATE->ENABLED
Thu Feb 23 22:28:54 2023 daemon.notice hostapd: client1: AP-ENABLED
Thu Feb 23 22:28:54 2023 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy0.conf (phy client0) --> new PHY
Thu Feb 23 22:28:56 2023 kern.warn kernel: [   59.686852] ath10k_pci 0000:00:00.0: pdev param 0 not supported by firmware
Thu Feb 23 22:28:56 2023 kern.info kernel: [   59.730900] br-client: port 5(client0) entered blocking state
Thu Feb 23 22:28:56 2023 kern.info kernel: [   59.736798] br-client: port 5(client0) entered disabled state
Thu Feb 23 22:28:56 2023 kern.info kernel: [   59.742934] device client0 entered promiscuous mode
Thu Feb 23 22:28:56 2023 daemon.notice netifd: Interface 'client' is now up
Thu Feb 23 22:28:56 2023 daemon.notice hostapd: client0: interface state UNINITIALIZED->COUNTRY_UPDATE
Thu Feb 23 22:28:57 2023 kern.info kernel: [   59.923299] IPv6: ADDRCONF(NETDEV_CHANGE): client0: link becomes ready
Thu Feb 23 22:28:57 2023 kern.info kernel: [   59.930207] br-client: port 5(client0) entered blocking state
Thu Feb 23 22:28:57 2023 kern.info kernel: [   59.936043] br-client: port 5(client0) entered forwarding state
Thu Feb 23 22:28:57 2023 daemon.notice hostapd: client0: interface state COUNTRY_UPDATE->ENABLED
Thu Feb 23 22:28:57 2023 daemon.notice hostapd: client0: AP-ENABLED
Thu Feb 23 22:28:57 2023 daemon.notice netifd: Wireless device 'radio1' is now up
Thu Feb 23 22:28:57 2023 daemon.notice netifd: Network device 'client1' link is up
Thu Feb 23 22:28:57 2023 daemon.info procd: - init complete -
Thu Feb 23 22:28:58 2023 user.notice firewall: Reloading firewall due to ifup of client (br-client)
Thu Feb 23 22:28:59 2023 kern.info kernel: [   62.095844] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
Thu Feb 23 22:28:59 2023 daemon.err odhcp6c[2211]: Failed to send SOLICIT message to ff02::1:2 (Operation not permitted)
Thu Feb 23 22:28:59 2023 daemon.notice netifd: Wireless device 'radio0' is now up
Thu Feb 23 22:28:59 2023 daemon.notice netifd: Network device 'mesh0' link is up
Thu Feb 23 22:28:59 2023 daemon.notice netifd: Interface 'mesh_radio0' is enabled
Thu Feb 23 22:28:59 2023 daemon.notice netifd: Interface 'mesh_radio0' has link connectivity
Thu Feb 23 22:28:59 2023 daemon.notice netifd: Interface 'mesh_radio0' is setting up now
Thu Feb 23 22:28:59 2023 daemon.notice netifd: Network device 'client0' link is up
Thu Feb 23 22:28:59 2023 daemon.notice netifd: Interface 'mesh_radio0' is now up
Thu Feb 23 22:29:00 2023 kern.info kernel: [   63.265491] batman_adv: bat0: Adding interface: mesh0
Thu Feb 23 22:29:00 2023 kern.info kernel: [   63.270681] batman_adv: bat0: Interface activated: mesh0
Thu Feb 23 22:29:00 2023 user.notice firewall: Reloading firewall due to ifup of mesh_radio0 (mesh0)
Thu Feb 23 22:29:01 2023 daemon.err odhcp6c[2211]: Failed to send SOLICIT message to ff02::1:2 (Operation not permitted)
Thu Feb 23 22:29:21 2023 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
Thu Feb 23 22:29:21 2023 daemon.info dnsmasq[1]: using nameserver 2001:bf7:170:192::34#53
Thu Feb 23 22:29:21 2023 daemon.info dnsmasq[1]: using nameserver 2001:bf7:170:192::b#53
Thu Feb 23 22:29:21 2023 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Thu Feb 23 22:29:21 2023 user.notice firewall: Reloading firewall due to ifupdate of client (br-client)
Thu Feb 23 22:29:28 2023 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
Thu Feb 23 22:29:28 2023 daemon.info dnsmasq[1]: using nameserver 2001:bf7:170:192::34#53
Thu Feb 23 22:29:28 2023 daemon.info dnsmasq[1]: using nameserver 2001:bf7:170:192::b#53
Thu Feb 23 22:29:28 2023 daemon.info dnsmasq[1]: using nameserver 2001:bf7:170:192::4#53
Thu Feb 23 22:29:28 2023 daemon.info dnsmasq[1]: using nameserver 2001:bf7:170:192::a#53
Thu Feb 23 22:29:28 2023 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Thu Feb 23 22:29:32 2023 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
Thu Feb 23 22:29:32 2023 daemon.info dnsmasq[1]: using nameserver 2001:bf7:170:192::34#53
Thu Feb 23 22:29:32 2023 daemon.info dnsmasq[1]: using nameserver 2001:bf7:170:192::b#53
Thu Feb 23 22:29:32 2023 daemon.info dnsmasq[1]: using nameserver 2001:bf7:170:192::4#53
Thu Feb 23 22:29:32 2023 daemon.info dnsmasq[1]: using nameserver 2001:bf7:170:192::a#53
Thu Feb 23 22:29:32 2023 daemon.info dnsmasq[1]: using nameserver 2001:bf7:170:192::36#53
Thu Feb 23 22:29:32 2023 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Thu Feb 23 22:29:34 2023 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
Thu Feb 23 22:29:34 2023 daemon.info dnsmasq[1]: using nameserver 2001:bf7:170:192::34#53
Thu Feb 23 22:29:34 2023 daemon.info dnsmasq[1]: using nameserver 2001:bf7:170:192::b#53
Thu Feb 23 22:29:34 2023 daemon.info dnsmasq[1]: using nameserver 2001:bf7:170:192::4#53
Thu Feb 23 22:29:34 2023 daemon.info dnsmasq[1]: using nameserver 2001:bf7:170:192::a#53
Thu Feb 23 22:29:34 2023 daemon.info dnsmasq[1]: using nameserver 2001:bf7:170:192::36#53
Thu Feb 23 22:29:34 2023 daemon.info dnsmasq[1]: using nameserver 2001:bf7:170:192::e#53
Thu Feb 23 22:29:34 2023 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Thu Feb 23 22:29:37 2023 daemon.err micrond[2437]: Chain 'RADV_FILTER' doesn't exist.
Thu Feb 23 22:29:37 2023 user.notice radv_filter_simple: ebtables chain RADV_FILTER does not exist
Thu Feb 23 22:29:37 2023 user.notice radv_filter_simple: Setting IPv6 Gateway to 02:ca:ff:ee:05:14
Thu Feb 23 22:29:42 2023 authpriv.info dropbear[4005]: Child connection from 2001:bf7:170:192:8170:7f87:9296:1aa6:50430
Sun Feb 26 09:13:31 2023 daemon.info hostapd: client0: STA 12:94:82:98:16:45 IEEE 802.11: authenticated
Sun Feb 26 09:13:31 2023 daemon.info hostapd: client0: STA 12:94:82:98:16:45 IEEE 802.11: associated (aid 1)
Sun Feb 26 09:13:31 2023 daemon.notice hostapd: client0: AP-STA-CONNECTED 12:94:82:98:16:45
Sun Feb 26 09:13:31 2023 daemon.info hostapd: client0: STA 12:94:82:98:16:45 RADIUS: starting accounting session 43743079C992BFD0
Sun Feb 26 09:13:50 2023 daemon.notice hostapd: client0: AP-STA-DISCONNECTED 12:94:82:98:16:45
Sun Feb 26 09:13:52 2023 daemon.info hostapd: client0: STA 12:94:82:98:16:45 IEEE 802.11: authenticated
Sun Feb 26 09:13:52 2023 daemon.info hostapd: client0: STA 12:94:82:98:16:45 IEEE 802.11: associated (aid 1)
Sun Feb 26 09:13:52 2023 daemon.notice hostapd: client0: AP-STA-CONNECTED 12:94:82:98:16:45
Sun Feb 26 09:13:52 2023 daemon.info hostapd: client0: STA 12:94:82:98:16:45 RADIUS: starting accounting session 01D4C84C0EC0EA30
Sun Feb 26 09:14:10 2023 daemon.notice hostapd: client0: AP-STA-DISCONNECTED 12:94:82:98:16:45
Sun Feb 26 09:14:13 2023 daemon.info hostapd: client0: STA 12:94:82:98:16:45 IEEE 802.11: authenticated
Sun Feb 26 09:14:13 2023 daemon.info hostapd: client0: STA 12:94:82:98:16:45 IEEE 802.11: associated (aid 1)
Sun Feb 26 09:14:13 2023 daemon.notice hostapd: client0: AP-STA-CONNECTED 12:94:82:98:16:45
Sun Feb 26 09:14:13 2023 daemon.info hostapd: client0: STA 12:94:82:98:16:45 RADIUS: starting accounting session 2B89A87E56492386
Sun Feb 26 09:14:31 2023 daemon.notice hostapd: client0: AP-STA-DISCONNECTED 12:94:82:98:16:45
Sun Feb 26 09:14:35 2023 daemon.info hostapd: client0: STA 12:94:82:98:16:45 IEEE 802.11: authenticated
Sun Feb 26 09:14:35 2023 daemon.info hostapd: client0: STA 12:94:82:98:16:45 IEEE 802.11: associated (aid 1)
Sun Feb 26 09:14:35 2023 daemon.notice hostapd: client0: AP-STA-CONNECTED 12:94:82:98:16:45
Sun Feb 26 09:14:35 2023 daemon.info hostapd: client0: STA 12:94:82:98:16:45 RADIUS: starting accounting session D7913748F03AE3D9
Sun Feb 26 09:14:36 2023 daemon.notice hostapd: client0: AP-STA-DISCONNECTED 12:94:82:98:16:45

-DIeses Problem (es konnte keine IP-Adresse zugewiesen werden) habe ich mit meinem tng Knoten (1.4.0~17) derzeit aber auch manchmal. https://map03.4830.org/map01/#!v:m;n:e894f66304a2-

Offenbar ein lokales Problem meines Laptops… geht wieder. die Obstgeräte hatten auch vorher keine Probleme.

1.4 ist aber nicht tng?

Hmm. Dazu nix im Milestone zu 2022.1.3 … Der JoyIT ist ath79, die haben in v2022.1.2 demnach wenn, dann Bootprobleme.

Ja, doch, war’s initial mal — sorry für die Konfusion; Ich habe für 1.4.0 nun einen eigenen Thread aufgemacht, …

… und für 1.5.0 geht’s hier weiter.

Nur zur Verfollständigung, der Fehler muss man Kartenserver gelegen haben. Ich hatte den Knoten jetzt über 30 Tage vom Netz. Dem zufolge ist er aus der Karte gelöscht. Jetzt passt es. Hat scheinbar mit den Häufigen neu aufsetzen zu tun gehabt.

1 Like