Here goes - FC3 All Updates and the latest PoPToP installed and receiving requests. All the PoPToP installation steps have been followed as per instructions and versions checked. I do not honestly think the problem lies there.
The problem seems to stem from me running pppd in demand mode or the way I call pppd to dial my ISP (yes I'm on the most wonderful invention called dial-up).
PoPToP sees the incoming connection, but as it hands off to pppd, pppd seems to terminate unexpectantly, and I think it has to do with the way my dial-up is set up, because chat also gets called to dial my ISP when all this happens, even though this is obviously unnecessary, as I am already connected.
While all this is going on, my ppp0 internet connection remains live.
The related log below:
Apr 28 15:48:14 server pptpd[19849]: CTRL: local address = 192.168.0.234
Apr 28 15:48:14 server pptpd[19849]: CTRL: remote address = 192.168.1.234
Apr 28 15:48:14 server pptpd[19849]: CTRL: pppd options file = /etc/ppp/options.pptpd
Apr 28 15:48:14 server pptpd[19849]: CTRL: Client 192.168.0.12 control connection started
Apr 28 15:48:14 server pptpd[19849]: CTRL: Received PPTP Control Message (type:1)
Apr 28 15:48:14 server pptpd[19849]: CTRL: Made a START CTRL CONN RPLY packet
Apr 28 15:48:14 server pptpd[19849]: CTRL: I wrote 156 bytes to the client.
Apr 28 15:48:14 server pptpd[19849]: CTRL: Sent packet to client
Apr 28 15:48:14 server pptpd[19849]: CTRL: Received PPTP Control Message (type:7)
Apr 28 15:48:14 server pptpd[19849]: CTRL: Set parameters to 100000000 maxbps, 64 window size
Apr 28 15:48:14 server pptpd[19849]: CTRL: Made a OUT CALL RPLY packet
Apr 28 15:48:14 server pptpd[19849]: CTRL: Starting call (launching pppd, opening GRE)
Apr 28 15:48:14 server pptpd[19849]: CTRL: pty_fd = 6
Apr 28 15:48:14 server pptpd[19849]: CTRL: tty_fd = 7
Apr 28 15:48:14 server pptpd[19850]: CTRL (PPPD Launcher): program binary = /usr/sbin/pppd
Apr 28 15:48:14 server pptpd[19849]: CTRL: I wrote 32 bytes to the client.
Apr 28 15:48:14 server pptpd[19850]: CTRL (PPPD Launcher): local address = 192.168.0.234
Apr 28 15:48:14 server pptpd[19849]: CTRL: Sent packet to client
Apr 28 15:48:14 server pptpd[19850]: CTRL (PPPD Launcher): remote address = 192.168.1.234
Apr 28 15:48:14 server pptpd[19849]: CTRL: Received PPTP Control Message (type:15)
Apr 28 15:48:14 server pptpd[19849]: CTRL: Got a SET LINK INFO packet with standard ACCMs
Apr 28 15:48:15 server pppd[19850]: Plugin /usr/lib/pptpd/pptpd-logwtmp.so loaded.
Apr 28 15:48:15 server pppd[19850]: pptpd-logwtmp: $Version$
Apr 28 15:48:15 server pptpd[19849]: GRE: read(fd=6,buffer=804eb00,len=8196) from PTY failed: status = -1 error = Input/output error, usually caused by unexpected termination of pppd, check option syntax and pppd logs
Apr 28 15:48:15 server pppd[19851]: pppd 2.4.3 started by root, uid 0
Apr 28 15:48:15 server pptpd[19849]: CTRL: PTY read or GRE write failed (pty,gre)=(6,7)
Apr 28 15:48:15 server pptpd[19849]: CTRL: Reaping child PPP[19850]
Apr 28 15:48:15 server chat[19852]: abort on (BUSY)
Apr 28 15:48:15 server pptpd[19849]: CTRL: Client 192.168.0.12 control connection finished
Apr 28 15:48:15 server chat[19852]: abort on (NO CARRIER)
Apr 28 15:48:15 server pptpd[19849]: CTRL: Exiting now
Apr 28 15:48:15 server chat[19852]: send (ATZ^M)
Apr 28 15:48:15 server pptpd[19840]: MGR: Reaped child 19849
Apr 28 15:48:15 server chat[19852]: expect (OK)
Apr 28 15:49:00 server chat[19852]: alarm
Apr 28 15:49:00 server chat[19852]: Failed
Apr 28 15:49:00 server pppd[19851]: Connect script failed
Apr 28 15:49:00 server pppd[19851]: Exit.
Apparently I'm supposed to see a
Connect: ppp0 <--> /dev/pts/0
Or something like that somewhere (although in my case should it be ppp1?), but pppd dies before it hits that stage.
I don't seem to have a pppd log anywhere even though option DEBUG=yes is set.
Any ideas anyone? At this stage I'll take anything, otherwise I'm going to have to dump it in favour of some other VPN road warrior solution which is not going to be anywhere near as convenient when you consider PPTP is built into Windows XP clients.
Regards, Ed.
