linux-ppp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: carlsonj@workingcode.com
To: linux-ppp@vger.kernel.org
Subject: Re: pppd don't create ppp-network-device
Date: Wed, 15 Sep 2004 14:33:08 +0000	[thread overview]
Message-ID: <16712.21156.383528.76301@carlson.workingcode.com> (raw)
In-Reply-To: <OFA2465F60.5C52B06E-ONC1256F0B.0042177C@bln.d-trust.de>

p.boehm@d-trust.net writes:
> I ask me why ppp does not create a new ppp-device, although it starts correctly (automatically
> loaded into
> kernel after start of pppd):

Use the 'debug' option and make sure that either /etc/syslog.conf has
daemon.debug directed to a file, or that you use the 'updetach' option
to send the debug information to your tty.

strace doesn't really record the needed information to debug the
problem.

> 1207  read(0, "\x54\x5a\x69\x66\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00"..., 4096) = 837

It seems like the peer said "TZif".  Not sure why, as you've not
included debug information.

> In kernel-config CONFIG_PPP Switches are set (as modules) and will supported by my kernel (out of
> CONFIG_PPP_MULTILINK)
> Any ideas where the problem could be? Or how I can find it?
> 
> Currently I study the ppp_generic sources to understand how it works, and that's my study-results so
> far ...

You shouldn't need to stare at the code to configure a PPP link.  Just
what exactly are you trying to do?

Are you trying to modify pppd's source code or are you trying to set
up a PPP link?

-- 
James Carlson                                 <carlsonj@workingcode.com>

      parent reply	other threads:[~2004-09-15 14:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-10 12:46 pppd don't create ppp-network-device p.boehm
2004-09-10 16:02 ` Bill Unruh
2004-09-15 14:14 ` p.boehm
2004-09-15 14:33 ` carlsonj [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16712.21156.383528.76301@carlson.workingcode.com \
    --to=carlsonj@workingcode.com \
    --cc=linux-ppp@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).