netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: daniel@braunwarth.dev
To: "Stephen Hemminger" <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next 1/2] lib: add profinet and ethercat as link layer protocol names
Date: Tue, 01 Mar 2022 18:26:10 +0000	[thread overview]
Message-ID: <d928314fccec204c36979e253b8fc4ae@braunwarth.dev> (raw)
In-Reply-To: <20220228092133.59909985@hermes.local>

February 28, 2022 6:21 PM, "Stephen Hemminger" <stephen@networkplumber.org> wrote:
> This is legacy table. Original author did choose to use stanard
> file /etc/ethertypes. Not sure why??

I tried to extend /etc/ethertypes with the following line:
ETHERCAT        88A4    ethercat

I would expect the following command to successfully run:
tc filter add dev eno1 protocol ethercat matchall action drop

Unfortunately all I get is:
Error: argument "ethercat" is wrong: invalid protocol

With my patches applied, the command runs without any error.


I wasn't able to find any hint in the code, where /etc/ethertypes is supposed to be parsed. Could you give me a hint?


Thanks

Daniel

  reply	other threads:[~2022-03-01 18:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-28 13:45 [PATCH iproute2-next 0/2] lib: add profinet and ethercat as link layer protocol Daniel Braunwarth
2022-02-28 13:45 ` [PATCH iproute2-next 1/2] lib: add profinet and ethercat as link layer protocol names Daniel Braunwarth
2022-02-28 17:21   ` Stephen Hemminger
2022-03-01 18:26     ` daniel [this message]
2022-03-01 19:58       ` Stephen Hemminger
2022-02-28 13:45 ` [PATCH iproute2-next 2/2] tc: bash-completion: Add profinet and ethercat to procotol completion list Daniel Braunwarth
2022-03-04 16:30 ` [PATCH iproute2-next 0/2] lib: add profinet and ethercat as link layer protocol patchwork-bot+netdevbpf

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=d928314fccec204c36979e253b8fc4ae@braunwarth.dev \
    --to=daniel@braunwarth.dev \
    --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).