linux-ppp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guillaume Nault <gnault@redhat.com>
To: "Pali Rohár" <pali@kernel.org>
Cc: James Carlson <carlsonj@workingcode.com>,
	Chris Fowler <cfowler@outpostsentinel.com>,
	Jakub Kicinski <kuba@kernel.org>,
	Paul Mackerras <paulus@samba.org>,
	"David S. Miller" <davem@davemloft.net>,
	"linux-ppp@vger.kernel.org" <linux-ppp@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ppp: Add rtnl attribute IFLA_PPP_UNIT_ID for specifying ppp unit id
Date: Tue, 12 Jul 2022 19:34:03 +0200	[thread overview]
Message-ID: <20220712173403.GC3794@localhost.localdomain> (raw)
In-Reply-To: <20220709120906.ymkhn5diywadgrka@pali>

On Sat, Jul 09, 2022 at 02:09:06PM +0200, Pali Rohár wrote:
> On Tuesday 17 August 2021 18:21:55 Pali Rohár wrote:
> > On Tuesday 17 August 2021 18:05:25 Guillaume Nault wrote:
> > > On Mon, Aug 16, 2021 at 06:23:55PM +0200, Pali Rohár wrote:
> > > > On Monday 16 August 2021 18:11:14 Guillaume Nault wrote:
> > > > > Do you have plans for adding netlink support to pppd? If so, is the
> > > > > project ready to accept such code?
> > > > 
> > > > Yes, I have already some WIP code and I'm planning to send a pull
> > > > request to pppd on github for it. I guess that it could be accepted,
> > > 
> > > I guess you can easily use the netlink api for cases where the "unit"
> > > option isn't specified and fall back to the ioctl api when it is. If
> > > all goes well, then we can extend the netlink api to accept a unit id.
> > > 
> > > But what about the lack of netlink feedback about the created
> > > interface? Are you restricted to use netlink only when the "ifname"
> > > option is provided?
> > 
> > Exactly, this is how I wrote my WIP code...
> 
> Sorry for a long delay (I forgot about it). Now I created pull request
> for pppd https://github.com/ppp-project/ppp/pull/354 which adds support
> for creating ppp interface via rtnetlink. rtnetlink is used only when
> ppp unit id was not provided and interface name was provided.

Interesting work. Thanks for working on it!

> > > > specially if there still would be backward compatibility via ioctl for
> > > > kernels which do not support rtnl API.
> > > 
> > > Indeed, I'd expect keeping compatiblitity with old kernels that only
> > > have the ioctl api to be a must (but I have no experience contributing
> > > to the pppd project).
> > > 
> > > > One of the argument which can be
> > > > used why rtnl API is better, is fixing issue: atomic creating of
> > > > interface with specific name.
> > > 
> > > Yes, that looks useful.
> > > 
> 


      reply	other threads:[~2022-07-12 17:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-07 16:37 [PATCH] ppp: Add rtnl attribute IFLA_PPP_UNIT_ID for specifying ppp unit id Pali Rohár
2021-08-09 19:25 ` Jakub Kicinski
2021-08-09 19:31   ` Pali Rohár
2021-08-10 15:39     ` Guillaume Nault
2021-08-10 16:04       ` Pali Rohár
2021-08-11 17:19         ` Guillaume Nault
2021-08-11 17:54           ` Pali Rohár
2021-08-12  9:19             ` Guillaume Nault
2021-08-12 14:09               ` Pali Rohár
2021-08-12 19:12                 ` Guillaume Nault
     [not found]       ` <BN0P223MB0327A247724B7AE211D2E84EA7F79@BN0P223MB0327.NAMP223.PROD.OUTLOOK.COM>
2021-08-10 17:16         ` Pali Rohár
2021-08-10 18:11           ` James Carlson
2021-08-11 17:38             ` Guillaume Nault
2021-08-11 18:04               ` Pali Rohár
2021-08-12  9:28                 ` Guillaume Nault
2021-08-12 13:48                   ` Pali Rohár
2021-08-12 18:26                     ` Guillaume Nault
2021-08-12 19:04                       ` Pali Rohár
2021-08-16 16:11                         ` Guillaume Nault
2021-08-16 16:23                           ` Pali Rohár
2021-08-17 16:05                             ` Guillaume Nault
2021-08-17 16:21                               ` Pali Rohár
2022-07-09 12:09                                 ` Pali Rohár
2022-07-12 17:34                                   ` Guillaume Nault [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=20220712173403.GC3794@localhost.localdomain \
    --to=gnault@redhat.com \
    --cc=carlsonj@workingcode.com \
    --cc=cfowler@outpostsentinel.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ppp@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pali@kernel.org \
    --cc=paulus@samba.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).