From: Jakub Kicinski <kuba@kernel.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Re: netdev: operstate UNKNOWN for loopback and other devices?
Date: Tue, 19 Nov 2024 19:23:53 -0800 [thread overview]
Message-ID: <20241119192353.2862779e@kernel.org> (raw)
In-Reply-To: <20241119153703.71f97b76@hermes.local>
On Tue, 19 Nov 2024 15:37:03 -0800 Stephen Hemminger wrote:
> It looks like loopback and other software devices never get the operstate
> set correctly. Not a serious problem, but it is incorrect.
>
> For example:
> $ ip -br link
> lo UNKNOWN 00:00:00:00:00:00 <LOOPBACK,UP,LOWER_UP>
>
> tap0 UNKNOWN ca:ff:ed:bf:96:a0 <BROADCAST,PROMISC,UP,LOWER_UP>
> tap1 UNKNOWN 36:f5:16:d1:4c:15 <BROADCAST,PROMISC,UP,LOWER_UP>
>
> For wireless and ethernet devices kernel reports UP and DOWN correctly.
>
> Looks like some missing bits in dev_open but not sure exactly where.
I thought it means the driver doesn't have any notion of the carrier,
IOW the carrier will never go down. Basically those drivers don't
call netif_carrier_{on,off}() at all, and rely on carrier being on
by default at netdev registration.
next prev parent reply other threads:[~2024-11-20 3:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 23:37 netdev: operstate UNKNOWN for loopback and other devices? Stephen Hemminger
2024-11-20 3:23 ` Jakub Kicinski [this message]
2024-11-20 17:08 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2025-02-03 19:17 Yong Wang
2025-02-04 11:58 ` Ido Schimmel
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=20241119192353.2862779e@kernel.org \
--to=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).