On Thu, Aug 12, 2021 at 09:04:40PM +0200, Pali Rohár wrote: > The point here is that there is application (pppd) which allows > specifying custom unit id as an option argument. Also it allows to call > external applications (at some events) with sharing file descriptors. > And it is one of the options how to touch part of ppp connection via > external scripts / applications. You start pppd for /dev/ttyUSB<N> with > unit id <N> and then in external script you use <N> for ioctls. And I do > not know if there is a way how to retrieve unit id in those external > scripts. There was already discussion about marking all file descriptors > in pppd as close-on-exec and it was somehow rejected as it will broke > custom scripts / applications which pppd invokes on events. So looks > like that people are using these "features" of pppd. Potential external pppd scripts, that depend on the unit id, may be a valid use case for letting the netlink api define this identifier (if pppd ever gets netlink support). > Option "unit" in pppd specifies ppp unit id. And if new API (rtnl) would > not provide equivalent for allowing to specify it then migrating pppd > from ioctl to rtnl is not possible without breaking compatibility. > > As you already described, we can simulate setting default interface name > in pppd application. But above usage or any other which expose pppd API > to other application is not possible to simulate. If the pppd project is interested in adding support for the netlink api, then I'm fine with adding this feature. I just want to make sure that it'll have a real world use case. > So I think we need to first decide or solve issue if rtnl ppp API should > provide same functionality as ioctl ppp API. If answer is yes, then some > kind of specifying custom ppp unit id is required. If answer is no (e.g. > because we do not want ppp unit id in rtnl API as it looks legacy and > has issues) then rtnl ppp API cannot be used by ppp as it cannot provide > all existing / supported features without breaking legacy compatibility. > > I see pros & cons for both answers. Not supporting legacy code paths in > new code/API is the way how to clean up code and prevent repeating old > historic issues. But if new code/API is not fully suitable for pppd -- > which is de-facto standard Linux userspace implementation -- does it > make sense to have it? Or does it mean to also implement new userspace > part of implementation (e.g. pppd2) to avoid these legacy / historic > issues? Or... is not whole ppp protocol just legacy part of our history > which should not be used in new modern setups? And for "legacy usage" is > current implementation enough and it does not make sense to invest time > into this area? I cannot answer to these questions, but I think it is > something quite important as it can show what should be direction and > future of ppp subsystem. PPP isn't legacy, but very few people are interested in working on and maintaining the code. Do you have plans for adding netlink support to pppd? If so, is the project ready to accept such code? BTW, sorry for the delay.
