Hello Michael,
sorry for going the short way. Usually I know the process and try to adher to it.
My intention was to add a little issue to the main bug discussion of hostapd. In the meantime the issue has grown ( see community ), so I will add this error to bugzila.
Regards,
Bernhard
Gesendet: Montag, 2. Februar 2026 um 18:44
Von: "Michael Tremer" <[email protected]>
An: "Bernhard Bitsch" <[email protected]>
Betreff: Re: Core 199 - hostapd-f747ae0-70 - running but no connection to ap repeater
Could we have a bug report for things like this if you discover them, please?
Otherwise they will just get lost in a never ending stream of emails.
-Michael
> On 8 Jan 2026, at 14:34, Bernhard Bitsch <[email protected]> wrote:
>
> 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
>
>
