From: Bernard Pidoux <bernard.pidoux@free.fr>
To: Eric Dumazet <edumazet@google.com>, rodgepritesh@gmail.com
Cc: netdev@vger.kernel.org, "David S . Miller" <davem@davemloft.net>,
kuba@kernel.org, pabeni@redhat.com, linux-hams@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/rose: Fix uninitialized values in rose_add_node
Date: Sun, 28 Sep 2025 14:59:47 +0200 [thread overview]
Message-ID: <02b4fa63-cf06-4138-8ae2-6ada09362706@free.fr> (raw)
In-Reply-To: <CANn89i+6naPhD_XJ-qjQ8mRGN1aQdSzMy1446d+0iOk_UjpMOw@mail.gmail.com>
ROSE protocole is extensively used for level 2 or level 3 networking
packet AX25 frames through neighbours and digipeaters stations in order
to exchange data or messages by radio or Internet links.
nodes and routes are most often managed by FPAC suite of applications.
fpad sets up local nodes and adjacent neighbours using fpac.conf,
fpac.nodes and fpac.routes configuration files.
Then at any time it is possible to add or delete rose nodes from the
list of previously defined nodes to help routing and connections using
ax25tools application rsparms:
# rsparms -nodes list
2080175520/0010 -> ax0 F6BVP-9
2080175526/0010 -> ax0 F6BVP-11
2080835201/0010 -> ??? RSLOOP-0
# rsparms -nodes add 2080444501/0 axudp F3KT-11 F6BVP-9
# rsparms -nodes list
2080175520/0010 -> ax0 F6BVP-9
2080175526/0010 -> ax0 F6BVP-11
2080835201/0010 -> ??? RSLOOP-0
*/0000 -> ax0 F3KT-11 via F6BVP-9
# rsparms -nodes d 2080444501/0 axudp F3KT-11 F6BVP-9
# rsparms -nodes list
2080175520/0010 -> ax0 F6BVP-9
2080175526/0010 -> ax0 F6BVP-11
2080835201/0010 -> ??? RSLOOP-0
Up to now no issues have been encountered during add or delete nodes
process.
Bernard Pidoux, F6BVP / AI7BG
https://github.com/ve7fet/linuxax25
prev parent reply other threads:[~2025-09-28 13:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 21:22 rodgepritesh
2025-09-13 8:10 ` Eric Dumazet
2025-09-28 12:59 ` Bernard Pidoux [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=02b4fa63-cf06-4138-8ae2-6ada09362706@free.fr \
--to=bernard.pidoux@free.fr \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rodgepritesh@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
all inboxes | Powered by JetHome®