Linux PPP protocol development
 help / color / mirror / Atom feed
From: tony.chamberlain@lemko.com
To: linux-ppp@vger.kernel.org
Subject: PPTP VPN, PPTP CONFIG
Date: Tue, 01 Jul 2008 14:56:36 +0000	[thread overview]
Message-ID: <W2416827856326101214924196@webmail30> (raw)





I installed the PPTP VPN on a client to connect via pptpvpn to a server
which is running it. I used pptpconfig to config the network. When I
connect, the VPN runs fine. I looked in pptpconfig and saw it does a

usr sbin pppd call myserver logfd 1 updetach persist

(I used "myserver" in this mail instead of the actual name). So I made a file
etc init.d pptpvpn where under start) I do the above (along with some checking,
etc). This also works nicely, when I but (after chkconfig on) the VPN comes
up and I can connect.

Problem is, if somehow the pptp process dies, if it is in etc init.d it won't start up
automatically again (which I need), so instead I transfered to etc inittab:

 vp:35:respawn: usr sbin pppd call myserver logfd 1 updetach persist

A "kill -1 1" or reboot will start this, but a ps just shows two processes with that
but I can't ping. A few minutes later it shows two processes again but with new
PIDs. Then a few minutes later two new processes with the same parameters
(there are only 2 at a time). I can't ping anything on the VPN either (and I do
add the routes in ip-up.local so from the etc rc5.d script it starts up the route).

Anyway how can I either modify my script in etc init.d (linked to etc rc*.d) to respawn
in the (unlikely but possible) case the process dies, or modify etc inittab to work
correctly?

Thanks











             reply	other threads:[~2008-07-01 14:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01 14:56 tony.chamberlain [this message]
2008-07-02  3:38 ` PPTP VPN, PPTP CONFIG James Cameron

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=W2416827856326101214924196@webmail30 \
    --to=tony.chamberlain@lemko.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