linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rémy DZIEMIASZKO" <remy.dziemiaszko@smile.fr>
To: linux-can@vger.kernel.org
Subject: How to statically set J1939 addresses and names
Date: Tue, 8 Jun 2021 17:27:45 +0200	[thread overview]
Message-ID: <CAEWvZg2rvR=9kE_wcm-KtzMvDtnqTEXSLF56zrB=3TgqZbEs1w@mail.gmail.com> (raw)

Hello,

I need that my applications do not care about J1939 node addresses but
directly bind / connect to socket based on node name only and the
kernel takes care of the conversion to addresses.

I know this is possible if addresses are dynamically assigned through
the Address Claiming protocol that is implemented in the kernel. The
kernel keeps track of its own address and name as well as the
addresses and names of other ECUs on the network and convert name to
adresse when requested by the applications.

But I don't want to use the Address Claiming protocol. I want to
statically set all addresses and names.

Is there a way to assign J1939 addresses and names to a CAN interface
without using the J1939 address claim protocol?

I found in old j1939 kernel documentation something like
ip addr add dev canX j1939 0xXX
ip addr add dev canX j1939 name 0xXX
See https://www.spinics.net/lists/netdev/msg162350.html

But in the latest j1939 kernel documentation I do not find any
reference to these commands.

Thanks for your help
--
Rémy Dziemiaszko
Tech Manager
Smile Embedded & Connected Systems

             reply	other threads:[~2021-06-08 15:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08 15:27 Rémy DZIEMIASZKO [this message]
2021-06-11  4:12 ` How to statically set J1939 addresses and names Oleksij Rempel
2021-06-11  6:57   ` Kurt Van Dijck
2021-06-12 10:02     ` Patrick Menschel
2021-06-14  8:32     ` Rémy DZIEMIASZKO
2021-06-14  9:10       ` Kurt Van Dijck

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='CAEWvZg2rvR=9kE_wcm-KtzMvDtnqTEXSLF56zrB=3TgqZbEs1w@mail.gmail.com' \
    --to=remy.dziemiaszko@smile.fr \
    --cc=linux-can@vger.kernel.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).