Topic: PPTP and PPPOE problems

[Boris]

Has anyone had problems connecting to a PPTP server going through a PPPOE connection? The PPPoE uses the PPPD daemon to connect to the internet. That is no problem. Whenever I try to connect to my server remotely, It connects but drops the connects, it stops working. I was looking through the logs and it seems and it looks like it cant start another PPP session. Heres what the logs say.

Sep  1 20:04:09 e-smith pptpd[2052]: MGR: Launching /usr/sbin/pptpctrl to handle client
Sep  1 20:04:09 e-smith pptpd[2052]: CTRL: local address = 192.168.0.1
Sep  1 20:04:09 e-smith pptpd[2052]: CTRL: remote address = 192.168.0.248
Sep  1 20:04:09 e-smith pptpd[2052]: CTRL: pppd speed = 460800
Sep  1 20:04:09 e-smith pptpd[2052]: CTRL: pppd options file = /etc/ppp/options.pptpd
Sep  1 20:04:09 e-smith pptpd[2052]: CTRL: Client 24.xx.xx.xx control connection started
Sep  1 20:04:09 e-smith pptpd[2052]: CTRL: Received PPTP Control Message (type: 1)
Sep  1 20:04:09 e-smith pptpd[2052]: CTRL: Made a START CTRL CONN RPLY packet
Sep  1 20:04:09 e-smith pptpd[2052]: CTRL: I wrote 156 bytes to the client.
Sep  1 20:04:09 e-smith pptpd[2052]: CTRL: Sent packet to client
Sep  1 20:04:09 e-smith pptpd[2052]: CTRL: Received PPTP Control Message (type: 7)
Sep  1 20:04:09 e-smith pptpd[2052]: CTRL: 0 min_bps, 1525 max_bps, 32 window size
Sep  1 20:04:09 e-smith pptpd[2052]: CTRL: Made a OUT CALL RPLY packet
Sep  1 20:04:09 e-smith pptpd[2052]: CTRL: Starting call (launching pppd, opening GRE)
Sep  1 20:04:09 e-smith pptpd[2052]: CTRL: pty_fd = 5
Sep  1 20:04:09 e-smith pptpd[2052]: CTRL: tty_fd = 6
Sep  1 20:04:09 e-smith pptpd[2052]: CTRL: I wrote 32 bytes to the client.
Sep  1 20:04:09 e-smith pptpd[2053]: CTRL (PPPD Launcher): Connection speed = 460800
Sep  1 20:04:09 e-smith pptpd[2052]: CTRL: Sent packet to client
Sep  1 20:04:09 e-smith pptpd[2053]: CTRL (PPPD Launcher): local address = 192.168.0.1
Sep  1 20:04:09 e-smith pptpd[2053]: CTRL (PPPD Launcher): remote address = 192.168.0.248
Sep  1 20:04:09 e-smith pptpd[2052]: CTRL: Received PPTP Control Message (type: 15)
Sep  1 20:04:09 e-smith pptpd[2052]: CTRL: Got a SET LINK INFO packet with standard ACCMs
Sep  1 20:04:10 e-smith pptpd[2052]: CTRL: Received PPTP Control Message (type: 15)
Sep  1 20:04:10 e-smith pptpd[2052]: CTRL: Ignored a SET LINK INFO packet with real ACCMs!
Sep  1 20:04:11 e-smith pptpd[2052]: CTRL: Received PPTP Control Message (type: 15)
Sep  1 20:04:11 e-smith pptpd[2052]: CTRL: Got a SET LINK INFO packet with standard ACCMs
Sep  1 20:04:11 e-smith pptpd[2052]: CTRL: Received PPTP Control Message (type: 12)
Sep  1 20:04:11 e-smith pptpd[2052]: CTRL: Made a CALL DISCONNECT RPLY packet
Sep  1 20:04:11 e-smith pptpd[2052]: CTRL: Received CALL CLR request (closing call)
Sep  1 20:04:11 e-smith pptpd[2052]: CTRL: I wrote 148 bytes to the client.
Sep  1 20:04:11 e-smith pptpd[2052]: CTRL: Sent packet to client
Sep  1 20:04:11 e-smith pptpd[2052]: GRE: read error: Bad file descriptor
Sep  1 20:04:11 e-smith pptpd[2052]: CTRL: PTY read or GRE write failed (pty,gre)=(-1,-1)
Sep  1 20:04:11 e-smith pptpd[2052]: CTRL: Client 24.xx.xx.xx control connection finished
Sep  1 20:04:11 e-smith pptpd[2052]: CTRL: Exiting now
Sep  1 20:04:11 e-smith pptpd[1912]: MGR: Reaped child 2052


This happens both on e-smith 5.5 and 5.6beta. Any ideas?

[Shad Lords]

I have PPPOE and can successfully connect via PPTP.

To me it looks like whatever client you are using isn't sending a set of protocols that SME supports.  Ex. client trying to talk 40-bit, SME only wants to talk 128-bit.

- Shad

[Arkman]

Or, possibly that a firewall is blocking GRE traffic somewhere between your client and SME.