[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZD5RSOrpUusamkQv@debian>
Date: Tue, 18 Apr 2023 10:14:00 +0200
From: Guillaume Nault <gnault@...hat.com>
To: Dominique Martinet <asmadeus@...ewreck.org>
Cc: Samuel Thibault <samuel.thibault@...-lyon.org>,
James Chapman <jchapman@...alix.com>, tparkin@...alix.com,
edumazet@...gle.com, davem@...emloft.net, kuba@...nel.org,
pabeni@...hat.com, corbet@....net, netdev@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] PPPoL2TP: Add more code snippets
On Mon, Apr 17, 2023 at 07:26:41AM +0900, Dominique Martinet wrote:
> Samuel Thibault wrote on Mon, Apr 17, 2023 at 12:07:04AM +0200:
> (That somewhat makes it sounds like the "new" netlink interface cannot
> be used (e.g. ip command); although I guess sommeone implementing this
> would be more likely to use the ioctls than not so having the names can
> be a timesaver?)
I don't understand what you mean by 'the "new" netlink interface'. You
can create a PPP interface either with the PPPIOCNEWUNIT ioctl or with
netlink. But no matter how you create it, you need a /dev/ppp file
descriptor associated to the PPP network device. Other than that, and
no matter how you create them, PPP network devices can be used and
configured like any other network interface. You absolutely can use
"ip link" to manage you ppp interfaces.
Powered by blists - more mailing lists