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]

Message-ID: <3415E2A2AB26944B9159CDB22001004D0252D1B7@nestea.sierrawireless.local>
Date:	Fri, 29 Feb 2008 17:41:14 -0800
From:	"Kevin Lloyd" <klloyd@...rrawireless.com>
To:	"James Chapman" <jchapman@...alix.com>
Cc:	"Dan Williams" <dcbw@...hat.com>, <netdev@...r.kernel.org>
Subject: RE: Network device driver with PPP

James Chapman wrote:
> > Actually we provide a method for the driver to obtain the
> > username/password information needed for the CHAP authentication so
in
> > theory the driver has the information needed to create the
connection.
> > I'm not sure how it would go about setting the DNS and IP addresses,
but
> > that's a separate issue further down the road.
> 
> Can you explain why you need the driver to be involved in any of this?
I'm trying to evaluate what level of consistency can be maintained for
our drivers across operating systems and whether there is precedence for
such a design. Looking like it's not going to happen...

> Control protocols live in userspace, datapath in the kernel.
Okay. I have a question about the datapath actually: If I have a serial
device and I establish a connection with pppd does it configure the
generic ppp driver to talk to the ttyUSBx port and then route the
control (e.g. NCP and LCP) packets to /dev/ppp for control by pppd and
the data (IP) packets somewhere else? Also is it pppd that directly sets
up the network interface in ifconfig? I'm a little confused/lost here...

> Can't you implement a private interface to your kernel driver so that
> userspace can ask it for the username/password and userspace then
starts
> pppd with those parameters?
Yes I suppose I could do that, how would you recommend approaching this,
ioctl?

Also, is Documentation\networking\ppp_generic.txt up-to-date (says
edited 2002) or is there a better resource explaining ppp architecture
on Linux?

Thanks for your help,
-Kevin
--
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