Koozali.org: home of the SME Server

PPTP flaky since upgrading to 5.6

Millsey

PPTP flaky since upgrading to 5.6
« on: January 21, 2003, 12:14:00 AM »
As subject .. PPTP connections from my W2K PC have become very erratic, and often disconnect. Has anyone else found this? Is it worth reinstalling from scratch to try to resolve this (the server is also running System monitor and SARG rpm's)

Thanks
Millsey

steve

Re: PPTP flaky since upgrading to 5.6
« Reply #1 on: January 21, 2003, 12:58:38 AM »
I too have a server that worked fine but right after the upgrade to  5.6, I could not connect and had to reboot the server.
also had a quake2 server running on it and it also could not be connected to, although it was still running and did not give any error messages.

steve

Steve Bush

Re: PPTP flaky since upgrading to 5.6
« Reply #2 on: January 21, 2003, 11:30:02 PM »
I am having a problem with a new 5.6b7 installation.
I use Windows XP Pro to connect using PPTP to the SME server.  The same PC connects to SME <=5.5 servers no problem.
The only way to make it semi-stable is to run a ping job on my pc to the internal ip of the server with the -t switch while I work.
If I don't run ping in the background, the DUN connection stays open but I lose connectivity to devices on the internal network. The external address remains visible.
I opened a bug ticket for this, but haven't been able to provide enough feedback for Mitel to fix the problem (my holdup, not theirs)
FYI - I have a Dell PE2600 dual Xeon server, so it is using the multiprocessor kernel, if that makes any difference.
I also have dual Intel Gigabit nics (e1000 driver).

rob wellesley

Re: PPTP flaky since upgrading to 5.6
« Reply #3 on: January 22, 2003, 03:03:56 AM »
Are you (all) connecting to or "thru" a 5.6 SME?

rob

Steve Bush

Re: PPTP flaky since upgrading to 5.6
« Reply #4 on: January 22, 2003, 03:29:20 AM »
I am connecting to a SME5.6b7 server through a SME5.0 server.

rob wellesley

Re: PPTP flaky since upgrading to 5.6
« Reply #5 on: January 22, 2003, 04:20:22 AM »
Steve Bush wrote:
>
> I am connecting to a SME5.6b7 server through a SME5.0 server.

What does the messages log say? the disconnect should be logged.

rob

Steve Bush

Re: PPTP flaky since upgrading to 5.6
« Reply #6 on: January 22, 2003, 06:59:36 AM »
I cleared the log file, closed putty, then ended my ping session.
I then tried to recreate the ping session but there was no response.
I then stopped and started the PPTP session, with a ping session
running in the background.  Mitel has asked for a log while in debug,
but I haven't been able to take the time to supply it to them.

Jan 21 21:38:03 server1 sshd(pam_unix)[3913]: session closed for user root
Jan 21 21:38:13 server1 pptpd[3893]: CTRL: Received PPTP Control Message (type: 5)
Jan 21 21:38:13 server1 pptpd[3893]: CTRL: Made a ECHO RPLY packet
Jan 21 21:38:13 server1 pptpd[3893]: CTRL: I wrote 20 bytes to the client.
Jan 21 21:38:13 server1 pptpd[3893]: CTRL: Sent packet to client
Jan 21 21:38:18 server1 pptpd[3893]: GRE: Discarding for incorrect call
Jan 21 21:38:33 server1 last message repeated 3 times
Jan 21 21:38:39 server1 pptpd[3893]: CTRL: Received PPTP Control Message (type: 15)
Jan 21 21:38:39 server1 pptpd[3893]: CTRL: Got a SET LINK INFO packet with standard ACCMs
Jan 21 21:38:39 server1 pptpd[3893]: GRE: Discarding for incorrect call
Jan 21 21:38:45 server1 last message repeated 3 times
Jan 21 21:38:46 server1 pptpd[3893]: CTRL: Received PPTP Control Message (type: 12)
Jan 21 21:38:46 server1 pptpd[3893]: CTRL: Made a CALL DISCONNECT RPLY packet
Jan 21 21:38:46 server1 pptpd[3893]: CTRL: Received CALL CLR request (closing call)
Jan 21 21:38:46 server1 pptpd[3893]: CTRL: I wrote 148 bytes to the client.
Jan 21 21:38:46 server1 pptpd[3893]: CTRL: Sent packet to client
Jan 21 21:38:46 server1 pppd[3894]: Modem hangup
Jan 21 21:38:46 server1 pppd[3894]: MPPE disabled
Jan 21 21:38:46 server1 pppd[3894]: Connection terminated.
Jan 21 21:38:46 server1 pppd[3894]: Connect time 1.6 minutes.
Jan 21 21:38:46 server1 pppd[3894]: Sent 43971 bytes, received 17915 bytes.
Jan 21 21:38:46 server1 /etc/hotplug/net.agent: NET unregister event not supported
Jan 21 21:38:46 server1 pppd[3894]: Connect time 1.6 minutes.
Jan 21 21:38:46 server1 pppd[3894]: Sent 43971 bytes, received 17915 bytes.
Jan 21 21:38:46 server1 pppd[3894]: Exit.
Jan 21 21:38:46 server1 pptpd[3893]: CTRL: Received PPTP Control Message (type: 3)
Jan 21 21:38:46 server1 pptpd[3893]: CTRL: Made a STOP CTRL CONN RPLY packet
Jan 21 21:38:46 server1 pptpd[3893]: CTRL: Received STOP CTRL CONN request (disconnecting)
Jan 21 21:38:46 server1 pptpd[3893]: CTRL: I wrote 16 bytes to the client.
Jan 21 21:38:46 server1 pptpd[3893]: CTRL: Sent packet to client
Jan 21 21:38:46 server1 pptpd[3893]: CTRL: Client 66.27.1.10 control connection finished
Jan 21 21:38:46 server1 pptpd[3893]: CTRL: Exiting now
Jan 21 21:38:46 server1 pptpd[3335]: MGR: Reaped child 3893
Jan 21 21:38:50 server1 pptpd[3981]: MGR: Launching /usr/sbin/pptpctrl to handle client
Jan 21 21:38:50 server1 pptpd[3981]: CTRL: local address = 10.10.10.1
Jan 21 21:38:50 server1 pptpd[3981]: CTRL: remote address = 10.10.10.246
Jan 21 21:38:50 server1 pptpd[3981]: CTRL: pppd speed = 460800
Jan 21 21:38:50 server1 pptpd[3981]: CTRL: pppd options file = /etc/ppp/options.pptpd
Jan 21 21:38:50 server1 pptpd[3981]: CTRL: Client 66.27.1.10 control connection started
Jan 21 21:38:50 server1 pptpd[3981]: CTRL: Received PPTP Control Message (type: 1)
Jan 21 21:38:50 server1 pptpd[3981]: CTRL: Made a START CTRL CONN RPLY packet
Jan 21 21:38:50 server1 pptpd[3981]: CTRL: I wrote 156 bytes to the client.
Jan 21 21:38:50 server1 pptpd[3981]: CTRL: Sent packet to client
Jan 21 21:38:50 server1 pptpd[3981]: CTRL: Received PPTP Control Message (type: 7)
Jan 21 21:38:50 server1 pptpd[3981]: CTRL: Set parameters to 1525 maxbps, 64 window size
Jan 21 21:38:50 server1 pptpd[3981]: CTRL: Made a OUT CALL RPLY packet
Jan 21 21:38:50 server1 pptpd[3981]: CTRL: Starting call (launching pppd, opening GRE)
Jan 21 21:38:50 server1 pptpd[3981]: CTRL: pty_fd = 5
Jan 21 21:38:50 server1 pptpd[3981]: CTRL: tty_fd = 6
Jan 21 21:38:50 server1 pptpd[3981]: CTRL: I wrote 32 bytes to the client.
Jan 21 21:38:50 server1 pptpd[3981]: CTRL: Sent packet to client
Jan 21 21:38:50 server1 pptpd[3982]: CTRL (PPPD Launcher): Connection speed = 460800
Jan 21 21:38:50 server1 pptpd[3982]: CTRL (PPPD Launcher): local address = 10.10.10.1
Jan 21 21:38:50 server1 pptpd[3982]: CTRL (PPPD Launcher): remote address = 10.10.10.246
Jan 21 21:38:50 server1 pppd[3982]: pppd 2.4.2b1 started by root, uid 0
Jan 21 21:38:50 server1 pppd[3982]: Using interface ppp0
Jan 21 21:38:50 server1 pppd[3982]: Connect: ppp0 <--> /dev/pts/0
Jan 21 21:38:50 server1 /etc/hotplug/net.agent: assuming ppp0 is already up
Jan 21 21:38:50 server1 pptpd[3981]: CTRL: Received PPTP Control Message (type: 15)
Jan 21 21:38:50 server1 pptpd[3981]: CTRL: Got a SET LINK INFO packet with standard ACCMs
Jan 21 21:38:51 server1 pptpd[3981]: GRE: Discarding duplicate packet
Jan 21 21:38:53 server1 pptpd[3981]: CTRL: Received PPTP Control Message (type: 15)
Jan 21 21:38:53 server1 pptpd[3981]: CTRL: Ignored a SET LINK INFO packet with real ACCMs!
Jan 21 21:38:54 server1 pppd[3982]: CHAP peer authentication succeeded for bush
Jan 21 21:38:54 server1 pppd[3982]: MPPE 128-bit stateless compression enabled
Jan 21 21:38:57 server1 pppd[3982]: found interface eth0 for proxy arp
Jan 21 21:38:57 server1 pppd[3982]: local  IP address 10.10.10.1
Jan 21 21:38:57 server1 pppd[3982]: remote IP address 10.10.10.246
Jan 21 21:38:57 server1 e-smith[3996]: Processing event: ip-up.pptpd ppp0 /dev/pts/0 460800 10.10.10.1 10.10.10.246 pptpd
Jan 21 21:38:57 server1 e-smith[3996]: Running event handler: /etc/e-smith/events/ip-up.pptpd/S70pptp-interface-access
Jan 21 21:38:57 server1 e-smith[3996]: S70pptp-interface-access=action|Event|ip-up.pptpd|Action|S70pptp-interface-access|Start|1043206737 153241|End|1043206737 265031|Elapsed|0.11179
Jan 21 21:39:09 server1 sshd(pam_unix)[3737]: session closed for user root
Jan 21 21:39:11 server1 sshd[4000]: Accepted password for root from 10.10.10.246 port 1064
Jan 21 21:39:11 server1 sshd(pam_unix)[4000]: session opened for user root by (uid=0)

rob wellesley

Re: PPTP flaky since upgrading to 5.6
« Reply #7 on: January 23, 2003, 12:01:23 AM »
All the posts on this topic here and else where seem to indicate Win2k client usage. Anyone having trouble with any other client connecting?

rob

Steve Bush

Re: PPTP flaky since upgrading to 5.6
« Reply #8 on: January 23, 2003, 12:33:01 AM »
Windows XP Pro SP1

steve

Re: PPTP flaky since upgrading to 5.6
« Reply #9 on: January 23, 2003, 12:46:11 AM »
win98 2nd ed.

rob wellesley

Re: PPTP flaky since upgrading to 5.6
« Reply #10 on: January 23, 2003, 05:48:02 AM »
I have emailed a link to this topic to bugs@e-smith.com

I will put our 5.6 test-bed "online" tonight and test it from the internet and let you know what i find

/etc/init.d/pptpd indicates that pptpd is started in debug mode by default? is this right - i.e.


  start)
        echo -n "Starting pptpd: "
        if [ -f /var/lock/subsys/pptpd ] ; then
                echo
                exit 1
        fi

        /usr/sbin/pptpd -d
        echo
        touch /var/lock/subsys/pptpd
        ;;

Steve Landers

Re: PPTP flaky since upgrading to 5.6
« Reply #11 on: January 23, 2003, 04:34:46 PM »
rob wellesley wrote:
>
> Are you (all) connecting to or "thru" a 5.6 SME?

Thru.

I used to connect through an SME 5.1.2 box, from a SuSE Linux box using pptp-client for Linux.

After the 5.6 upgrade the connections are flaky - sometimes connect, sometimes don't. Always disconnect within a minute or so.

Steve

---

Steve Landers                     Scripting Design Studio
Digital Smarties                  steve@digital-smarties.com
Perth, Western Australia          DigitalSmarties.com

Amazing Iceman

Re: PPTP flaky since upgrading to 5.6
« Reply #12 on: February 17, 2003, 10:22:50 PM »
I have a similar problem, but in this case, the clietn is an iPAQ H3975 PocketPC, using the included PPTP Client, with the MS Enhanced Encryption Pack loaded.
I was able to connect without any problems using version 5.0 somewhere in the upgrade path to 5.6 it stopped working.
This is what the file /var/log/messages reports when I try to connect.
Thank you...

Feb 17 14:19:20 sme-1 pptpd[2365]: MGR: Launching /usr/sbin/pptpctrl to handle client
Feb 17 14:19:20 sme-1 pptpd[2365]: CTRL: local address = 192.168.100.1
Feb 17 14:19:20 sme-1 pptpd[2365]: CTRL: remote address = 192.168.100.245
Feb 17 14:19:20 sme-1 pptpd[2365]: CTRL: pppd speed = 460800
Feb 17 14:19:20 sme-1 pptpd[2365]: CTRL: pppd options file = /etc/ppp/options.pptpd
Feb 17 14:19:20 sme-1 pptpd[2365]: CTRL: Client 66.176.237.166 control connection started
Feb 17 14:19:20 sme-1 pptpd[2365]: CTRL: Received PPTP Control Message (type: 1)
Feb 17 14:19:20 sme-1 pptpd[2365]: CTRL: Made a START CTRL CONN RPLY packet
Feb 17 14:19:20 sme-1 pptpd[2365]: CTRL: I wrote 156 bytes to the client.
Feb 17 14:19:20 sme-1 pptpd[2365]: CTRL: Sent packet to client
Feb 17 14:19:20 sme-1 pptpd[2365]: CTRL: Received PPTP Control Message (type: 7)
Feb 17 14:19:20 sme-1 pptpd[2365]: CTRL: Set parameters to 1525 maxbps, 64 window size
Feb 17 14:19:20 sme-1 pptpd[2365]: CTRL: Made a OUT CALL RPLY packet
Feb 17 14:19:20 sme-1 pptpd[2365]: CTRL: Starting call (launching pppd, opening GRE)
Feb 17 14:19:20 sme-1 pptpd[2365]: CTRL: pty_fd = 5
Feb 17 14:19:20 sme-1 pptpd[2365]: CTRL: tty_fd = 6
Feb 17 14:19:20 sme-1 pptpd[2365]: CTRL: I wrote 32 bytes to the client.
Feb 17 14:19:20 sme-1 pptpd[2365]: CTRL: Sent packet to client
Feb 17 14:19:20 sme-1 pptpd[2366]: CTRL (PPPD Launcher): Connection speed = 460800
Feb 17 14:19:20 sme-1 pptpd[2366]: CTRL (PPPD Launcher): local address = 192.168.100.1
Feb 17 14:19:20 sme-1 pptpd[2366]: CTRL (PPPD Launcher): remote address = 192.168.100.245
Feb 17 14:19:20 sme-1 pppd[2366]: pppd 2.4.2b1 started by root, uid 0
Feb 17 14:19:20 sme-1 pppd[2366]: Using interface ppp0
Feb 17 14:19:20 sme-1 /etc/hotplug/net.agent: assuming ppp0 is already up
Feb 17 14:19:20 sme-1 pppd[2366]: Connect: ppp0 <--> /dev/pts/1
Feb 17 14:19:20 sme-1 pptpd[2365]: GRE: Discarding duplicate packet
Feb 17 14:19:23 sme-1 pptpd[2365]: CTRL: Received PPTP Control Message (type: 15)
Feb 17 14:19:23 sme-1 pptpd[2365]: CTRL: Ignored a SET LINK INFO packet with real ACCMs!
Feb 17 14:19:23 sme-1 pppd[2366]: CHAP peer authentication succeeded for johnisler
Feb 17 14:19:23 sme-1 pppd[2366]: MPPE required but peer negotiation failed
Feb 17 14:19:23 sme-1 pppd[2366]: Connection terminated.
Feb 17 14:19:23 sme-1 pppd[2366]: Connect time 0.1 minutes.
Feb 17 14:19:23 sme-1 pppd[2366]: Sent 24 bytes, received 60 bytes.
Feb 17 14:19:23 sme-1 pppd[2366]: Connect time 0.1 minutes.
Feb 17 14:19:23 sme-1 pppd[2366]: Sent 24 bytes, received 60 bytes.
Feb 17 14:19:23 sme-1 pppd[2366]: Exit.
Feb 17 14:19:23 sme-1 pptpd[2365]: GRE: read(fd=5,buffer=804d940,len=8196) from PTY failed: status = -1 error = Input/output error
Feb 17 14:19:23 sme-1 pptpd[2365]: CTRL: PTY read or GRE write failed (pty,gre)=(5,6)
Feb 17 14:19:23 sme-1 pptpd[2365]: CTRL: Client 66.176.237.166 control connection finished
Feb 17 14:19:23 sme-1 pptpd[2365]: CTRL: Exiting now
Feb 17 14:19:24 sme-1 pptpd[2163]: MGR: Reaped child 2365
Feb 17 14:19:24 sme-1 /etc/hotplug/net.agent: NET unregister event not supported

rob Wellesley


Amazing Iceman

Re: PPTP flaky since upgrading to 5.6
« Reply #14 on: February 18, 2003, 12:05:22 AM »
Thanks Rob, but I already tried that without any success. I have 4 SME Servers at different locations/networks and all of them have the same problem.

Any other clues?


rob Wellesley wrote:
>
> http://www.e-smith.org/bugs/index.php3?op=showBug&bugID=93

rob Wellesley

Re: PPTP flaky since upgrading to 5.6
« Reply #15 on: February 18, 2003, 12:24:43 AM »
actually - the bug help is missing a line

after commenting out the template you need to rebuild the masq file

/sbin/e-smith/expand-template /etc/rc.d/init.d/masq

reboot

Steve Bush

Re: PPTP flaky since upgrading to 5.6
« Reply #16 on: February 18, 2003, 06:15:40 PM »
This has fixed my inbound PPTP problem.

Amazing Iceman

Re: PPTP flaky since upgrading to 5.6
« Reply #17 on: March 04, 2003, 02:03:50 AM »
I tried that , but it didn't help either.

Ian Baker

Re: PPTP flaky since upgrading to 5.6
« Reply #18 on: March 17, 2003, 03:17:09 PM »
Hi,
  I have exactly the same problem and symptoms as Steve and Iceman. The difference between 5.5 and 5.6, as far as I can see, is that in the log file, V5.6 has the line :

pppd[3982]: CHAP peer authentication succeeded for XXXX

whereas V5.5 had MSCHAP-v2 for the authentication.

  Comments anyone?

   Regards,
     Ian

Allen

Re: PPTP flaky since upgrading to 5.6
« Reply #19 on: June 17, 2003, 07:56:14 PM »
Ressurecting an old thread :)

Just tried the PPTP from my home system.

Was able to connect successfully to my SME box on our LAN (sits behind a DSL Router). I could ping it, but about 1.5 minutes later I get disconnected without warning or what not (similar to what users encountered above).

My home system: W2K, SP3
SME is 5.6

Any ideas? I'll keep poking around the site for info... :)

~Allen