public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Bernhard Bitsch <bbitsch@ipfire.org>
To: Michael Tremer <michael.tremer@ipfire.org>,
	IPFire Development <development@lists.ipfire.org>
Subject: Re: IPFire 2.29 - Core Update 199 released
Date: Wed, 7 Jan 2026 16:45:57 +0100	[thread overview]
Message-ID: <dc07f425-63c1-473d-bbdd-0d8e8a479801@ipfire.org> (raw)
In-Reply-To: <b32e0ab2-7967-40f9-8ac0-87a6200af9cf@ipfire.org>

I found the reason for the bulk of messages.
It was my homedale app on the Windows PC to watch the WLAN.
But nevertheless there are other such communications logged.

- Bernhard

On 07.01.26 16:28, Bernhard Bitsch <bbitsch@ipfire.org> wrote:
> A little excerpt, including a restart of hostapd.
> 
> 
> On 07.01.26 16:09, Michael Tremer <michael.tremer@ipfire.org> wrote:
> > Hello Bernard,
> >
> > No, it is not intended that there are a lot of log messages being 
> > written.
> >
> > Could you post what you are getting in your logs?
> >
> > -Michael
> >
> > > On 7 Jan 2026, at 14:59, Bernhard Bitsch <bbitsch@ipfire.org> wrote:
> > >
> > > After updating (hostapd also) syslogs are flooded with 
> > hostapd(nl80211) messages.
> > > Is this intended?
> > >
> > > BR
> > > Bernhard
> > >
> >
> >
> >
> 


      parent reply	other threads:[~2026-01-07 15:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <176779447271.3006246.11894699794282768600.ipfire@ipfire.org>
2026-01-07 14:59 ` Bernhard Bitsch
2026-01-07 15:09   ` Michael Tremer
2026-01-07 15:45     ` Bernhard Bitsch
     [not found]     ` <b32e0ab2-7967-40f9-8ac0-87a6200af9cf@ipfire.org>
2026-01-07 15:45       ` Bernhard Bitsch [this message]

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=dc07f425-63c1-473d-bbdd-0d8e8a479801@ipfire.org \
    --to=bbitsch@ipfire.org \
    --cc=development@lists.ipfire.org \
    --cc=michael.tremer@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