public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Bernhard Bitsch <bbitsch@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core 199 - hostapd-f747ae0-70 - running but no connection to ap repeater
Date: Thu, 8 Jan 2026 15:34:39 +0100	[thread overview]
Message-ID: <612f6ca4-b4f7-4c0c-827f-190750f23867@ipfire.org> (raw)
In-Reply-To: <b83120dd-9082-4175-bcaa-81e35e11767a@ipfire.org>

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



       reply	other threads:[~2026-01-08 14:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b83120dd-9082-4175-bcaa-81e35e11767a@ipfire.org>
2026-01-08 14:34 ` Bernhard Bitsch [this message]
2026-02-02 17:44   ` Michael Tremer
2026-02-02 18:57     ` Aw: " Bernhard Bitsch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=612f6ca4-b4f7-4c0c-827f-190750f23867@ipfire.org \
    --to=bbitsch@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox