From: Andrew Lunn <andrew@lunn.ch>
To: Gaoyang Wei <yhyxwgy@gmail.com>
Cc: netdev@vger.kernel.org, pbs05 <xuziyougm@gmail.com>,
Matheus Sampaio Queiroga <srherobrine20@gmail.com>,
Benjamin Larsson <benjamin.larsson@genexis.eu>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Russell King <linux@armlinux.org.uk>
Subject: Re: [RFC] net: towards a generic PON framework
Date: Sun, 27 Sep 2026 21:47:06 +0200 [thread overview]
Message-ID: <3d5e9f9f-09e0-41a2-aa3a-e3bcfcecbef3@lunn.ch> (raw)
In-Reply-To: <92d9c8a9-ef43-45ce-a599-2c00d0a2fa61@gmail.com>
On Mon, Sep 28, 2026 at 01:22:13AM +0800, Gaoyang Wei wrote:
> Hi Andrew,
>
> Thanks, the hostapd/wpa_supplicant analogy is useful.
>
> > But having a dedicated net_device seems wrong to me. However what
> > you mentioned made me think of hostapd and wpa_supplicant. Can that
> > sort of model be used? It does not require an additional interface
> > by the side of the wifi interface.
>
> Yes, I think that is worth considering.
>
> One reason I initially found a packet net_device attractive was that
> OMCI itself is a packet-oriented protocol, and an ARPHRD_NONE device
> would give userspace a natural AF_PACKET interface without pretending
> that OMCI is Ethernet.
As i said, i know very little about PON, so i will likely ask lots of
dumb questions...
With hostapd/wpa_supplicant, the PDUs it needs to exchange between the
Wireless client and the access point have normal 802.11 headers.
Do raw OMCI PDUs not have headers? How can you tell apart a OMCI PDU
from a user data PDU?
Is there a PON header before the OMCI and data PDUs? Tools like pcap &
wireshark do allow for protocol specific headers, so you can have
802.3 headers, or 802.11 headers. You can even have fake headers, like
wifi RSS, and more accurate time stamps from the hardware, etc.
Andrew
next prev parent reply other threads:[~2026-09-27 19:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 17:46 [RFC] net: towards a generic PON framework Gaoyang Wei
2026-09-26 19:28 ` Matheus Sampaio Queiroga
2026-09-26 20:21 ` Gaoyang Wei
2026-09-26 21:55 ` Matheus Sampaio Queiroga
2026-09-26 22:15 ` Gaoyang Wei
2026-09-27 0:05 ` Matheus Sampaio Queiroga
2026-09-27 4:38 ` Gaoyang Wei
2026-09-27 17:47 ` Matheus Sampaio Queiroga
2026-09-27 18:27 ` Gaoyang Wei
2026-09-27 16:57 ` Andrew Lunn
2026-09-27 17:22 ` Gaoyang Wei
2026-09-27 19:24 ` Ziyou Xu
2026-09-27 19:47 ` Andrew Lunn [this message]
2026-09-27 20:29 ` Ziyou Xu
2026-09-27 22:30 ` Andrew Lunn
2026-09-27 22:49 ` Andrew Lunn
2026-09-27 23:11 ` Gaoyang Wei
2026-09-28 1:25 ` Andrew Lunn
2026-09-28 8:37 ` John Crispin
2026-09-28 10:54 ` Benjamin Larsson
2026-09-28 14:10 ` Andrew Lunn
2026-10-01 12:25 ` Benjamin Larsson
2026-09-28 11:23 ` Gaoyang Wei
2026-09-28 14:05 ` Andrew Lunn
2026-09-27 20:47 ` Benjamin Larsson
2026-09-27 20:58 ` Gaoyang Wei
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=3d5e9f9f-09e0-41a2-aa3a-e3bcfcecbef3@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew+netdev@lunn.ch \
--cc=benjamin.larsson@genexis.eu \
--cc=linux@armlinux.org.uk \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=srherobrine20@gmail.com \
--cc=xuziyougm@gmail.com \
--cc=yhyxwgy@gmail.com \
/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