All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Lindner <marek.lindner@mailbox.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: suppressing warning about unavailable link speed
Date: Thu, 12 Jun 2025 07:45:12 +0200	[thread overview]
Message-ID: <6296400.MhkbZ0Pkbq@voltaire> (raw)
In-Reply-To: <CAPzS6u_U+BgkE+Unc_nmikEb45QeN7TVF7MFu=6ckAu-c44=Rw@mail.gmail.com>

On Monday, June 9, 2025 9:08:07 PM Central European Summer Time Rustam wrote:
> It seems there is no way to suppress it.
> 
> I could do `batctl hardif br0.100 to 100000` but only *after* I add the
> interface and get the above warning.

By default batman-adv attempts to determine the link speed automagically. That 
is why you see a warning every time that magic fails.


> So here's a suggestion - maybe there could be a "default link speed"
> setting, which, when set, would also suppress the warning?
> And/or allow setting the link speed override *before* adding the interface.
> Then we could patch systemd-networkd to make it configurable.

Having a default setting for manual link speed is not a bad idea. You'd have 
to document well whether this default speed comes into effect only when the 
auto-link-speed detection has failed or always.

Feel free to propose a patch.


> Or perhaps expand link speed detection to descend into bridges and grab the
> underlying link speeds?

Afaik br0.100 is a VLAN interface which does not provide link speeds on its 
down.

Automatic link detection on the underlying bridge interface will be tricky. If 
the bride contains multiple slave interfaces which link speed should be used?

Cheers,
Marek




      reply	other threads:[~2025-06-12  5:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-09 19:08 suppressing warning about unavailable link speed Rustam
2025-06-12  5:45 ` Marek Lindner [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=6296400.MhkbZ0Pkbq@voltaire \
    --to=marek.lindner@mailbox.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.