Ken Ambrose wrote:
>
> While we're on this topic... I'm tyring to get PoPToP running on my work
> machine, and failing (maybe). I guess the real problem is client-side --
> the documentation on how to set up the pptp client is sparse at best (the
> entire "USING" file is 19 lines long, and amazingly uninformative). Maybe
> I'm just lacking the experience that would make it all obvious, but when I
> try to kick off pptp, I use:
>
> pptp ip.address.of.host
>
> and it seems to work -- pppd gets kicked off, happy things are said... but
> ppp0 never comes up, nor gets an IP, and finally dies with
>
> LCP: timeout sending Config-Requests
This is usually because there is a firewall between the client and
server that is either blocking or NATing the traffic. If it is a NAT
situation, then you need the VPN Masquerade patch for linux
(http://www.wolfenet.com/~jhardin). If it is just blocing the traffic,
then you need to open up port 1723 for tcp and protocol 47 (GRE).
> Then, when I try to kick it off to try some other command-line syntax, I
> get:
>
> warn[open_unixsock:pptp_callmgr.c:308]: Call manager for 64.65.199.186 is already
>running.
You need to rm /var/run/pptp/*
> lsof | grep socket
>
> doesn't show anything apparent, and there aren't any pppd nor pptp
> processes showing. Any of you VPN gurus got any pointers? (And, yes, I'm
> reasonably sure that my PoPToP/pppd server is configured properly, though,
> obviously, not certain. PoPToP has great documentation, though, so I'm
> fairly confident; the client side, OTOH, has me grasping at straws.)
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
