| To: | Michal Ostrowski <mostrows@xxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: RFC: PPP over X |
| From: | Mark Spencer <markster@xxxxxxxxx> |
| Date: | Fri, 4 Feb 2000 18:34:11 -0600 (EST) |
| Cc: | jamal <hadi@xxxxxxxxxx>, Henner Eisen <eis@xxxxxxxxxxxxx>, netdev@xxxxxxxxxxx, axboe@xxxxxxx, mitch@xxxxxxxxxx, Andi Kleen <ak@xxxxxxx>, Marc Boucher <marc@xxxxxxx>, paulus@xxxxxxxxxxxxx, Ben LaHaise <bcrl@xxxxxxxxxx> |
| In-reply-to: | <14490.63167.969929.894420@xxxxxxxxxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
> Do you mean that the PPP daemon always negotiated PPP over a character > device? I think we've reached a consensus that pppd should not assume > what kind of device it is negotiating over --- and leave that instead > to one of the plugins that knows all of the details (e.g.: setting up > PPP line discipline for modem connections). pppd would run on /dev/ppp and would negotiate the PPP using that file descriptor. What would actually supply the PPP frames to the kernel (and thus eventually to /dev/ppp) is up to the kernel driver. That's just how I did it. Mark |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: RFC: PPP over X, Mitchell Blank Jr |
|---|---|
| Next by Date: | Re: RFC: PPP over X, Michal Ostrowski |
| Previous by Thread: | Re: RFC: PPP over X, Michal Ostrowski |
| Next by Thread: | Re: RFC: PPP over X, jamal |
| Indexes: | [Date] [Thread] [Top] [All Lists] |