From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4dn6qn0Dmrz333g for ; Thu, 08 Jan 2026 14:34:45 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519) (Client CN "mail01.haj.ipfire.org", Issuer "R12" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4dn6qj42T0z2xLt for ; Thu, 08 Jan 2026 14:34:41 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4dn6qh66SdzQC for ; Thu, 08 Jan 2026 14:34:40 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1767882880; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=80dT1rqPYA0mAmLJqO2Iagxz3TFmAYZrhJ9Bk/RB7MY=; b=aM3ktkiyRPRgn7m96QQ95VlDL0D8DWf0JQyWDwMJJQrTq8g4rBZTpDEFRD8MfxTIZdeT7o diMJ5Vg/8hVfa0Cw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1767882880; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=80dT1rqPYA0mAmLJqO2Iagxz3TFmAYZrhJ9Bk/RB7MY=; b=AXJUFhtUVNh64B8sLlAecqS9jqwjUsSbhL4alrc6O6nXP5Y/O1/M7C+0FYrfEJ2xmTqblC SYXQ4segzI+rlLcCHOUIBl9rnMrNjbrLKaJwihinfYw0FFsiJr0KVkx17au/a2p78Z5blm NrMpcXODDYxwmIifhVjTNXR+cqfN59rxpflmsk9jK5cNX5/V8qSk5q+8S9Rv+gFVLxmlfZ NZ1XoWLBRCnZByfvRG8JUWJIJ9UCB54jlg7P9xvXKQ4/PK/R9Kblrc5IO6lmua+rgZrmGu +D3Moe+pJKyyw2lpzJCn9fpQhgoxkAFjpv9UZh4qq3U1RzHLpav+08TRvcJdjw== Message-ID: <612f6ca4-b4f7-4c0c-827f-190750f23867@ipfire.org> Date: Thu, 8 Jan 2026 15:34:39 +0100 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Subject: Re: Core 199 - hostapd-f747ae0-70 - running but no connection to ap repeater To: development@lists.ipfire.org References: Content-Language: en-GB From: Bernhard Bitsch In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit BTW: The neighbourhood scan is inverted. If it is ticked, the scan is suppressed. Am 07.01.2026 um 18:33 schrieb Matthias Fischer: > Hi all, > > I asked on the list before sending a bug report - this is my second try > - I couldn't see this posting on the list, thats why I'm sending this CC > to Michael... > > My problem: > After the mandatory restart while upgrading from Core 198 to Core 199 I > can't get access to my wireless repeater anymore. > > 'hostapd' is running, but the wirelss log gets flodded with > hostapd(nl80211) messages as seen in the attached file and as Bernhard > wrote in a previous mail. > > Normally I get around ~10 lines in the log - now I stopped 'hostapd' > after ~17000 entries and while its running the list is getting longer > and longer... > > The wireless-log file and a screenshot from the access config are > attached. The wireless status is way too short. > > Right now one of my 'Devels' is running - I'll try a rollback to the > version from Core 198, which ran without any problems. And my blue > network is down... > > Can anyone confirm this behavior? > > Best > Matthias