netdev - Re: Network device driver with PPP

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 28 Feb 2008 09:27:03 +0000
From:	James Chapman <jchapman@...alix.com>
To:	Dan Williams <dcbw@...hat.com>
CC:	Kevin Lloyd <klloyd@...rrawireless.com>, netdev@...r.kernel.org
Subject: Re: Network device driver with PPP

Dan Williams wrote:
> On Wed, 2008-02-27 at 17:28 -0800, Kevin Lloyd wrote:
>> Hi all,
>>
>> I have a device that is currently supported via a combination of loading the device with usb-serial (drivers/usb/serial/sierra) to expose the serial ports and connecting by manually launching pppd.
>> I would like to support this device in a network driver as opposed to a serial driver in an effort to offer a seamless always-on device, such as an Ethernet device.
>>
>> From what I understand the ppp support in the kernel is only for ppp framing and that all control (e.g., IPCP) is done in user-space via pppd. Are there any network drivers that currently manage the ppp connection (entirely, IPCP included) internally to the driver and expose either a raw ip or ethernet stream to the user-space?
> 
> That seems quite icky to do all in kernel space and a pile of code
> running in the kernel.  What's so wrong with userspace?  Don't you need
> to push values to the driver like username/password and get IP config
> out of it (which would involve userspace anyway)?  It just seems like
> there's a different solution to your actual problem here than stuff all
> off pppd into kernel space.

I agree.

Kevin mentions manually launching pppd and the desire for a seamless 
always-on device. I think this could be done using udev/hotplug rules to 
launch/stop pppd automatically when the usb device is hot-plugged. No 
additional kernel support needed.

-- 
James Chapman
Katalix Systems Ltd
http://www.katalix.com
Catalysts for your Embedded Linux software development

--
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