From: Bill Woodcock <woody@pch.net>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: "Dave Täht" <dave.taht@gmail.com>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] can bus attack
Date: Fri, 14 Apr 2023 08:25:07 +0200 [thread overview]
Message-ID: <27D60D19-9C24-4E66-BE3D-A478C5BA05AA@pch.net> (raw)
In-Reply-To: <9232C347-0DAD-478E-AA98-9BFFEDCB5773@gmx.de>
> On Apr 14, 2023, at 8:08 AM, Sebastian Moeller via Cerowrt-devel <cerowrt-devel@lists.bufferbloat.net> wrote:
>> there were a few years there where
>> fq_codel was the default for can, in openwrt, which sometimes keeps me
>> awake at night.
>
> [SM] How many critical CAN bus implementations actually use OpenWrt? I thought CAN is big in automobiles, so if any of those use OpenWrt that would be interesting news ;)
It’s also widely used in factory-floor and assembly-line automation.
-Bill
prev parent reply other threads:[~2023-04-14 6:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 4:04 Dave Taht
2023-04-14 6:08 ` Sebastian Moeller
2023-04-14 6:25 ` Bill Woodcock [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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27D60D19-9C24-4E66-BE3D-A478C5BA05AA@pch.net \
--to=woody@pch.net \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=moeller0@gmx.de \
/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