| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 31 Dec 2015 13:58:18 +0100 From: Guillaume Nault <g.nault@...halink.fr> To: Sedat Dilek <sedat.dilek@...il.com> Cc: David Miller <davem@...emloft.net>, "netdev@...r.kernel.org" <netdev@...r.kernel.org> Subject: Re: [net-next] ppp: rtnetlink device handling On Thu, Dec 31, 2015 at 12:01:40PM +0100, Sedat Dilek wrote: > On Thu, Dec 31, 2015 at 11:41 AM, Guillaume Nault <g.nault@...halink.fr> wrote: > > On Thu, Dec 31, 2015 at 08:46:59AM +0100, Sedat Dilek wrote: > >> Hi Guillaume, > >> > >> can you explain why you moved ppp to rtnetlink device handling? > >> Benefits, etc.? > >> > > The objective is to bring all the flexibility of rtnetlink device > > creation to ppp interfaces. This is particularly useful for Network > > Access Servers which need to define device properties at creation > > time. My use case includes setting device name and netns, which is > > impossible with the ioctl-based interface without generating transient > > effects. > > > > What do you mean by "my use-case"? > Example? > A NAS that terminates connections of PPP clients (usually transported over PPPoE or L2TP). Clients may have different routing needs so each PPP device is created in the appropriate network namespace. Without rtnl the PPP device has to be created in the PPPoE/L2TP server's namespace and then moved to the client's one. With rtnl, the PPP device can be directly created in the right namespace. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists