pptpclient-devel — PPTP Client Development and Support

Re: [pptp-devel] Setting PPTP client on Debian Jessie

[James C. <qu...@la...>]

On Wed, Jan 25, 2017 at 09:34:51PM -0300, Hugo wrote:
> James:
> Thanks!
> I set up the post-up and pre-down sentences on the /etc/network/interfaces
> file, and now the pptp tunnel comes up automatically at power on.

That's good.  I've updated the documentation.  Let me know what you
think.

http://pptpclient.sourceforge.net/howto-debian.phtml

-- 
James Cameron
http://quozl.netrek.org/

Re: [pptp-devel] Setting PPTP client on Debian Jessie

[Hugo <hu...@gm...>]

James:
Thanks!
I set up the post-up and pre-down sentences on
the /etc/network/interfaces file, and now the pptp tunnel comes up
automatically at power on.

Hugo

Re: [pptp-devel] Setting PPTP client on Debian Jessie

[James C. <qu...@la...>]

Yes, it sounds like a race condition.  In my tests it works fine, but
results must depend on how quickly the eth0 interface and DNS become
available, especially if DNS is required.

Please try;

- use an IP address instead of a host name, or;

- add "post-up /sbin/ifup tunnel" and "pre-down /sbin/ifdown tunnel"
  to the eth0 interface, and remove "auto tunnel", or;

- use Network Manager.

On Tue, Jan 24, 2017 at 02:43:00PM -0300, Hugo Lía wrote:
> The tunnel definition is right. Using the "pon" command the tunnel come up
> manually without problem.
> 
> I think the problem with Sarge and later procedure is that ppp port is trying
> to come up before the eth0 port is ready.
> 
> Hugo
> 
> El ene. 24, 2017 3:10, "James Cameron" <[1]qu...@la...> escribió:
> 
>     On Tue, Jan 24, 2017 at 01:57:58PM +1100, James Cameron wrote:
>     > On Mon, Jan 23, 2017 at 11:36:22PM -0300, Hugo wrote:
>     > > On Tue, 2017-01-24 at 10:21 +1100, James Cameron wrote:
>     > >
>     > >     On Mon, Jan 23, 2017 at 07:10:19PM -0300, Hugo wrote:
>     > >     > ... [1][2]http://pptpclient.sourceforge.net/howto-debian.phtml
>     > >     >
>     > >     > The problem is that on point 9 "To have the tunnel started on
>     system boot"
>     > >     > there is no instructions for Debian Jessie.
>     > >
>     > >     You would have had to look at the list of Debian release names and
>     > >     deduce that Debian Jessie matches the condition "Debian Sarge and
>     > >     later".
>     > >
>     > >     I'm not sure I want to keep adding release names.  So I shall
>     remove
>     > >     the old information.
>     > >
>     > > I've tried the Sarge instructions and it didn't connect.
>     >
>     > Thanks for letting me know, I've removed that step of the
>     > instructions.  Let me know if you find out how to make it
>     > automatically connect.
> 
>     I've put this step back into the instructions after testing it.  There
>     were no problems.
> 
>     I've also added Network Manager instructions.
> 
>     [3]http://pptpclient.sourceforge.net/howto-debian.phtml
> 
>     > > Configuring the PPTP client as for Debian Sarge and later the following
>     line in
>     > > is logged in /var/log/ppp-connect-errors
>     > > "anon fatal[get_ip_address:pptp.c:437]: getaddrinfo(): Name or service
>     not
>     > > known"
>     > >
>     > > This log entry appears any time the networking service is started.
>     >
>     > You might try Network Manager instead; it has a pptp plugin package.
> 
>     Check that you are passing the IP address or host name to the pptp
>     program.  In the configuring-by-hand instructions, that's the pty
>     option in the /etc/ppp/peers/$TUNNEL file.
> 
>     --
>     James Cameron
>     [4]http://quozl.netrek.org/
> 
> References:
> 
> [1] mailto:qu...@la...
> [2] http://pptpclient.sourceforge.net/howto-debian.phtml
> [3] http://pptpclient.sourceforge.net/howto-debian.phtml
> [4] http://quozl.netrek.org/

-- 
James Cameron
http://quozl.netrek.org/

Re: [pptp-devel] Setting PPTP client on Debian Jessie

[Hugo L. <hu...@gm...>]

The tunnel definition is right. Using the "pon" command the tunnel come up
manually without problem.

I think the problem with Sarge and later procedure is that ppp port is
trying to come up before the eth0 port is ready.


Hugo

El ene. 24, 2017 3:10, "James Cameron" <qu...@la...> escribió:

> On Tue, Jan 24, 2017 at 01:57:58PM +1100, James Cameron wrote:
> > On Mon, Jan 23, 2017 at 11:36:22PM -0300, Hugo wrote:
> > > On Tue, 2017-01-24 at 10:21 +1100, James Cameron wrote:
> > >
> > >     On Mon, Jan 23, 2017 at 07:10:19PM -0300, Hugo wrote:
> > >     > ... [1]http://pptpclient.sourceforge.net/howto-debian.phtml
> > >     >
> > >     > The problem is that on point 9 "To have the tunnel started on
> system boot"
> > >     > there is no instructions for Debian Jessie.
> > >
> > >     You would have had to look at the list of Debian release names and
> > >     deduce that Debian Jessie matches the condition "Debian Sarge and
> > >     later".
> > >
> > >     I'm not sure I want to keep adding release names.  So I shall
> remove
> > >     the old information.
> > >
> > > I've tried the Sarge instructions and it didn't connect.
> >
> > Thanks for letting me know, I've removed that step of the
> > instructions.  Let me know if you find out how to make it
> > automatically connect.
>
> I've put this step back into the instructions after testing it.  There
> were no problems.
>
> I've also added Network Manager instructions.
>
> http://pptpclient.sourceforge.net/howto-debian.phtml
>
> > > Configuring the PPTP client as for Debian Sarge and later the
> following line in
> > > is logged in /var/log/ppp-connect-errors
> > > "anon fatal[get_ip_address:pptp.c:437]: getaddrinfo(): Name or
> service not
> > > known"
> > >
> > > This log entry appears any time the networking service is started.
> >
> > You might try Network Manager instead; it has a pptp plugin package.
>
> Check that you are passing the IP address or host name to the pptp
> program.  In the configuring-by-hand instructions, that's the pty
> option in the /etc/ppp/peers/$TUNNEL file.
>
> --
> James Cameron
> http://quozl.netrek.org/
>

Re: [pptp-devel] Setting PPTP client on Debian Jessie

[James C. <qu...@la...>]

On Tue, Jan 24, 2017 at 01:57:58PM +1100, James Cameron wrote:
> On Mon, Jan 23, 2017 at 11:36:22PM -0300, Hugo wrote:
> > On Tue, 2017-01-24 at 10:21 +1100, James Cameron wrote:
> > 
> >     On Mon, Jan 23, 2017 at 07:10:19PM -0300, Hugo wrote:
> >     > ... [1]http://pptpclient.sourceforge.net/howto-debian.phtml
> >     >
> >     > The problem is that on point 9 "To have the tunnel started on system boot"
> >     > there is no instructions for Debian Jessie.
> > 
> >     You would have had to look at the list of Debian release names and
> >     deduce that Debian Jessie matches the condition "Debian Sarge and
> >     later".
> > 
> >     I'm not sure I want to keep adding release names.  So I shall remove
> >     the old information.
> > 
> > I've tried the Sarge instructions and it didn't connect.
> 
> Thanks for letting me know, I've removed that step of the
> instructions.  Let me know if you find out how to make it
> automatically connect.

I've put this step back into the instructions after testing it.  There
were no problems.

I've also added Network Manager instructions.

http://pptpclient.sourceforge.net/howto-debian.phtml

> > Configuring the PPTP client as for Debian Sarge and later the following line in
> > is logged in /var/log/ppp-connect-errors
> > "anon fatal[get_ip_address:pptp.c:437]: getaddrinfo(): Name or service not
> > known"
> > 
> > This log entry appears any time the networking service is started.
> 
> You might try Network Manager instead; it has a pptp plugin package.

Check that you are passing the IP address or host name to the pptp
program.  In the configuring-by-hand instructions, that's the pty
option in the /etc/ppp/peers/$TUNNEL file.

-- 
James Cameron
http://quozl.netrek.org/

Re: [pptp-devel] Setting PPTP client on Debian Jessie

[James C. <qu...@la...>]

On Mon, Jan 23, 2017 at 11:36:22PM -0300, Hugo wrote:
> On Tue, 2017-01-24 at 10:21 +1100, James Cameron wrote:
> 
>     On Mon, Jan 23, 2017 at 07:10:19PM -0300, Hugo wrote:
>     > ... [1]http://pptpclient.sourceforge.net/howto-debian.phtml
>     >
>     > The problem is that on point 9 "To have the tunnel started on system boot"
>     > there is no instructions for Debian Jessie.
> 
>     You would have had to look at the list of Debian release names and
>     deduce that Debian Jessie matches the condition "Debian Sarge and
>     later".
> 
>     I'm not sure I want to keep adding release names.  So I shall remove
>     the old information.
> 
> I've tried the Sarge instructions and it didn't connect.

Thanks for letting me know, I've removed that step of the
instructions.  Let me know if you find out how to make it
automatically connect.

> Configuring the PPTP client as for Debian Sarge and later the following line in
> is logged in /var/log/ppp-connect-errors
> "anon fatal[get_ip_address:pptp.c:437]: getaddrinfo(): Name or service not
> known"
> 
> This log entry appears any time the networking service is started.

You might try Network Manager instead; it has a pptp plugin package.

-- 
James Cameron
http://quozl.netrek.org/

Re: [pptp-devel] Setting PPTP client on Debian Jessie

[Hugo <hu...@gm...>]

On Tue, 2017-01-24 at 10:21 +1100, James Cameron wrote:

> On Mon, Jan 23, 2017 at 07:10:19PM -0300, Hugo wrote:
> > ... http://pptpclient.sourceforge.net/howto-debian.phtml
> > 
> > The problem is that on point 9 "To have the tunnel started on system boot"
> > there is no instructions for Debian Jessie.
> 
> You would have had to look at the list of Debian release names and
> deduce that Debian Jessie matches the condition "Debian Sarge and
> later".
> 
> I'm not sure I want to keep adding release names.  So I shall remove
> the old information.
> 


I've tried the Sarge instructions and it didn't connect.

Configuring the PPTP client as for Debian Sarge and later the following
line in is logged in /var/log/ppp-connect-errors
"anon fatal[get_ip_address:pptp.c:437]: getaddrinfo(): Name or service
not known"

This log entry appears any time the networking service is started.

Hugo

Re: [pptp-devel] Setting PPTP client on Debian Jessie

[James C. <qu...@la...>]

On Mon, Jan 23, 2017 at 07:10:19PM -0300, Hugo wrote:
> ... http://pptpclient.sourceforge.net/howto-debian.phtml
> 
> The problem is that on point 9 "To have the tunnel started on system boot"
> there is no instructions for Debian Jessie.

You would have had to look at the list of Debian release names and
deduce that Debian Jessie matches the condition "Debian Sarge and
later".

I'm not sure I want to keep adding release names.  So I shall remove
the old information.

-- 
James Cameron
http://quozl.netrek.org/

Re: [pptp-devel] Setting PPTP client on Debian Jessie

[Christoph B. <sou...@ma...>]

Hugo wrote...

> I have succesfully configure a PPTP-client connection from a Debian
> Jessie (8.7) server.
> I followed the instructions on
> http://pptpclient.sourceforge.net/howto-debian.phtml
> 
> The problem is that on point 9 "To have the tunnel started on system
> boot" there is no instructions for Debian Jessie.
> 
> I tried the instructions for Debian Woody but there is no
> "/etc/ppp/no_ppp_on_boot" after the installation. I created the file
> from scratch (using a sample I found on internet) but the tunnel does
> not come up either.

Have you tried the "for Debian Sarge and later" way? That one is
applicable for jessie as well.

    Christoph

[pptp-devel] Setting PPTP client on Debian Jessie

[Hugo <hu...@gm...>]

I have succesfully configure a PPTP-client connection from a Debian
Jessie (8.7) server.
I followed the instructions on
http://pptpclient.sourceforge.net/howto-debian.phtml

The problem is that on point 9 "To have the tunnel started on system
boot" there is no instructions for Debian Jessie.

I tried the instructions for Debian Woody but there is no
"/etc/ppp/no_ppp_on_boot" after the installation. I created the file
from scratch (using a sample I found on internet) but the tunnel does
not come up either.

Can someone please tell me how to do it?

Thanks
Hugo

Re: [pptp-devel] nf_conntrack_pptp auto-loading?

[Jaroslav S. <jsk...@re...>]

Thanks for info, I wanted to hear your opinion, I will treat it the
same way downstream (Fedora)

thanks & regards

Jaroslav

----- Original Message -----
> nf_conntrack_pptp is not needed by pptp.
> 
> nf_conntrack_pptp is for systems that route pptp.
> 
> nf_conntrack_pptp has a side-effect of ICMP unreachable suppression.
> 
> Some people try nf_conntrack_pptp to fix interoperability problems
> between systems; yet they are not routing pptp.  It hides the problem,
> and doesn't fix it.  It works by side-effect.
> 
> Once a problem is identified, we can design a better solution.
> 
> I've not seen a good description of the problem, but if it has to do
> with zero call id, we have a new patch in 1.9.0 which may also fix the
> problem.
> 
> Can you please work with people who use nf_conntrack_pptp to find out
> what the problem is, instead of accepting a side-effect solution?
> 
> On Thu, Dec 01, 2016 at 12:44:54PM -0500, Jaroslav Skarvada wrote:
> > Hi,
> > 
> > as the net.netfilter.nf_conntrack_helper now defaults to 0, users
> > now usually have to manually load the nf_conntrack_pptp module.
> > What do you think about auto-loading it (if available through e.g.
> > libkmod or just via modprobe)?
> > 
> > thanks & regards
> > 
> > Jaroslav
> > 
> > ------------------------------------------------------------------------------
> > _______________________________________________
> > pptpclient-devel mailing list
> > ppt...@li...
> > https://lists.sourceforge.net/lists/listinfo/pptpclient-devel
> 
> --
> James Cameron
> http://quozl.netrek.org/
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> pptpclient-devel mailing list
> ppt...@li...
> https://lists.sourceforge.net/lists/listinfo/pptpclient-devel
> 

Re: [pptp-devel] nf_conntrack_pptp auto-loading?

[James C. <qu...@la...>]

nf_conntrack_pptp is not needed by pptp.

nf_conntrack_pptp is for systems that route pptp.

nf_conntrack_pptp has a side-effect of ICMP unreachable suppression.

Some people try nf_conntrack_pptp to fix interoperability problems
between systems; yet they are not routing pptp.  It hides the problem,
and doesn't fix it.  It works by side-effect.

Once a problem is identified, we can design a better solution.

I've not seen a good description of the problem, but if it has to do
with zero call id, we have a new patch in 1.9.0 which may also fix the
problem.

Can you please work with people who use nf_conntrack_pptp to find out
what the problem is, instead of accepting a side-effect solution?

On Thu, Dec 01, 2016 at 12:44:54PM -0500, Jaroslav Skarvada wrote:
> Hi,
> 
> as the net.netfilter.nf_conntrack_helper now defaults to 0, users
> now usually have to manually load the nf_conntrack_pptp module.
> What do you think about auto-loading it (if available through e.g.
> libkmod or just via modprobe)?
> 
> thanks & regards
> 
> Jaroslav
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> pptpclient-devel mailing list
> ppt...@li...
> https://lists.sourceforge.net/lists/listinfo/pptpclient-devel

-- 
James Cameron
http://quozl.netrek.org/

[pptp-devel] nf_conntrack_pptp auto-loading?

[Jaroslav S. <jsk...@re...>]

Hi,

as the net.netfilter.nf_conntrack_helper now defaults to 0, users
now usually have to manually load the nf_conntrack_pptp module.
What do you think about auto-loading it (if available through e.g.
libkmod or just via modprobe)?

thanks & regards

Jaroslav

Re: [pptp-devel] "make test" fails

[Christoph B. <sou...@ma...>]

James Cameron wrote...

> Fixed in two commits, please review.

Looks good, good as in Tested-by:

> As "make test" only tests vector.c, it isn't of much use.  Lots of
> other code not being tested.  Don't let your users be deceived into
> thinking the test is comprehensive.

Yeah, already figured that out. However, today's Debianization wrappers
always call "make test" during build - which is the right(tm) thing -
and so this got triggered. Of course it's possible to work around it
in Debian silently, but why should if there's a swift upstream? :)

    Christoph

PS: Yes

Re: [pptp-devel] "make test" fails

[James C. <qu...@la...>]

Fixed in two commits, please review.

As "make test" only tests vector.c, it isn't of much use.  Lots of
other code not being tested.  Don't let your users be deceived into
thinking the test is comprehensive.

On Wed, Nov 30, 2016 at 12:01:52AM +0100, Christoph Biedl wrote:
> Hello,
> 
> can please somebody take a look why "make test" fails on several levels?
> 
> At the moment, a "test" binary is to be built, without success.
> 
> $ make test
> gcc    -c -o vector_test.o vector_test.c
> (...)
> gcc -o vector_test vector_test.o vector.o
> gcc   test.o vector_test   -o test
> /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/Scrt1.o: In function `_start':
> (.text+0x20): undefined reference to `main'
> (...)
> 
> Also running the created vector_test (is this supposed to be done in the test
> target?) triggers an assertion failure:
> 
> | vector_test: vector_test.c:78: main: Assertion `j==k' failed.
> 
> Or, with hardening build enabled:
> 
> | *** stack smashing detected ***: ./vector_test terminated
> 
> Looking at the compiler warnings like
> 
> | vector_test.c:29:38: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
> |          retval = vector_insert(v, i, (PPTP_CALL *)i);
> 
> this is little surprising.
> 
> Cheers,
> 
>     Christoph
> 

-- 
James Cameron
http://quozl.netrek.org/

[pptp-devel] "make test" fails

[Christoph B. <sou...@ma...>]

Hello,

can please somebody take a look why "make test" fails on several levels?

At the moment, a "test" binary is to be built, without success.

$ make test
gcc    -c -o vector_test.o vector_test.c
(...)
gcc -o vector_test vector_test.o vector.o
gcc   test.o vector_test   -o test
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/Scrt1.o: In function `_start':
(.text+0x20): undefined reference to `main'
(...)

Also running the created vector_test (is this supposed to be done in the test
target?) triggers an assertion failure:

| vector_test: vector_test.c:78: main: Assertion `j==k' failed.

Or, with hardening build enabled:

| *** stack smashing detected ***: ./vector_test terminated

Looking at the compiler warnings like

| vector_test.c:29:38: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
|          retval = vector_insert(v, i, (PPTP_CALL *)i);

this is little surprising.

Cheers,

    Christoph

[pptp-devel] pptp-1.9.0 released

[James C. <qu...@la...>]

G'day,

PPTP Client 1.9.0 is released.

Changes since 1.8.0 are:

- close a memory leak in pqueue,
- avoid spurious error about /bin/ip on FreeBSD,
- fix compiler warnings,
- avoid clobbering heap (RHBZ #1183627),
- fix use after free in call close request handler,
- make clean to clean pptpsetup.8 (Debian #831032),
- add --missing-window option (Debian #680455, Ubuntu #681617),
- randomise call-id (Debian #721963),
- replace gethostbyname(3) with getaddrinfo(3),
- fix typo in pptp_ctrl manpage,
- place pptpsetup manpage in correct section,
- don't set build flags; use defaults,
- remove pptpsetup.8 from source as it is generated,
- fix for (null) in "pptp: GRE-to-PPP gateway on (null)".

Can be downloaded from:
https://sourceforge.net/projects/pptpclient/files/pptp/pptp-1.9.0/
https://quozl.linux.org.au/pptp/

b2117b377f65294a9786f80f0235d308  pptp-1.9.0.tar.gz

Re: [pptp-devel] [PATCH] pqueue.h: include sys/types.h

[James C. <qu...@la...>]

Thanks, pushed as a2bc565.

On Fri, Jan 22, 2016 at 10:20:48AM -0300, Gustavo Zacarias wrote:
> We're using u_int32_t here, this breaks on musl libc builds otherwise.
> 
> Signed-off-by: Gustavo Zacarias <gu...@za...>
> ---
>  pqueue.h | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/pqueue.h b/pqueue.h
> index a56590f..8c60c62 100644
> --- a/pqueue.h
> +++ b/pqueue.h
> @@ -3,6 +3,7 @@
>  
>  #include <time.h>
>  #include <sys/time.h>
> +#include <sys/types.h>
>  
>  /* wait this many seconds for missing packets before forgetting about them */
>  #define DEFAULT_PACKET_TIMEOUT 0.3
> -- 
> 2.4.10
> 
> 
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
> _______________________________________________
> pptpclient-devel mailing list
> ppt...@li...
> https://lists.sourceforge.net/lists/listinfo/pptpclient-devel

-- 
James Cameron
http://quozl.netrek.org/

[pptp-devel] [PATCH] pqueue.h: include sys/types.h

[Gustavo Z. <gu...@za...>]

We're using u_int32_t here, this breaks on musl libc builds otherwise.

Signed-off-by: Gustavo Zacarias <gu...@za...>
---
 pqueue.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/pqueue.h b/pqueue.h
index a56590f..8c60c62 100644
--- a/pqueue.h
+++ b/pqueue.h
@@ -3,6 +3,7 @@
 
 #include <time.h>
 #include <sys/time.h>
+#include <sys/types.h>
 
 /* wait this many seconds for missing packets before forgetting about them */
 #define DEFAULT_PACKET_TIMEOUT 0.3
-- 
2.4.10

[pptp-devel] pptp - SSH and nfs not working over pptp connection

[Radoslav <r.s...@gm...>]

Dear all,
I'm new here and I've just signed up to the mailing list to report a problem
I am facing with pptpclient.

My setup is ubuntu 15.10  kernel 4.2.0-16-generic with pptp-linux 
package installed (1.8.0-1
version)
The ppp package installed for dependency is 2.4.6-3.1
The pptp server is Mikrotik router.

The problem appeared after upgrade from ubuntu15.04 to 15.10.
The pptp conection is established successfully.
The problem is that i cannot reach other computers via SSH and nfs services.

The output of SSH try is
OpenSSH_6.9p1 Ubuntu-2, OpenSSL 1.0.2d 9 Jul 2015
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to 192.168.88.150 [192.168.88.150] port 22.
debug1: Connection established.
debug1: identity file /home/rpr/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/rpr/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/rpr/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/rpr/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/rpr/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/rpr/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/rpr/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/rpr/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.9p1 Ubuntu-2
debug1: Remote protocol version 2.0, remote software version 
OpenSSH_6.0p1 Debian-4+deb7u2
debug1: match: OpenSSH_6.0p1 Debian-4+deb7u2 pat OpenSSH* compat 0x04000000
debug1: Authenticating to 192.168.88.150:22 as 'pi'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr um...@op... none
debug1: kex: client->server aes128-ctr um...@op... none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY

Here is the relevant part executing following command sudo pon 
RPRP_tunnel_file debug dump logfd 2 nodetach

pppd options in effect:
debug           # (from command line)
nodetach                # (from command line)
persist         # (from /etc/ppp/peers/RPRP_tunnel_file)
logfd 2         # (from command line)
maxfail 0               # (from /etc/ppp/peers/RPRP_tunnel_file)
dump            # (from command line)
noauth          # (from /etc/ppp/options.pptp)
refuse-pap              # (from /etc/ppp/options.pptp)
refuse-chap             # (from /etc/ppp/options.pptp)
refuse-mschap           # (from /etc/ppp/options.pptp)
refuse-eap              # (from /etc/ppp/options.pptp)
name prodanov.biz\\RPRP         # (from /etc/ppp/peers/RPRP_tunnel_file)
remotename PPTP         # (from /etc/ppp/peers/RPRP_tunnel_file)
                 # (from /etc/ppp/options.pptp)
pty pptp prodanov.biz --nolaunchpppd            # (from 
/etc/ppp/peers/RPRP_tunnel_file)
crtscts         # (from /etc/ppp/options)
                 # (from /etc/ppp/options)
asyncmap 0              # (from /etc/ppp/options)
lcp-echo-failure 4              # (from /etc/ppp/options)
lcp-echo-interval 30            # (from /etc/ppp/options)
hide-password           # (from /etc/ppp/options)
ipparam RPRP_tunnel_file                # (from 
/etc/ppp/peers/RPRP_tunnel_file)
nobsdcomp               # (from /etc/ppp/options.pptp)
nodeflate               # (from /etc/ppp/options.pptp)
require-mppe-128                # (from /etc/ppp/peers/RPRP_tunnel_file)
noipx           # (from /etc/ppp/options)
using channel 10
Using interface ppp0
Connect: ppp0 <--> /dev/pts/1
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xec4649a6> <pcomp> <accomp>]
rcvd [LCP ConfReq id=0x1 <auth chap MS-v2> <mru 1460> <magic 0x7248009f>]
sent [LCP ConfAck id=0x1 <auth chap MS-v2> <mru 1460> <magic 0x7248009f>]
rcvd [LCP ConfRej id=0x1 <asyncmap 0x0> <pcomp> <accomp>]
sent [LCP ConfReq id=0x2 <magic 0xec4649a6>]
rcvd [LCP ConfAck id=0x2 <magic 0xec4649a6>]
sent [LCP EchoReq id=0x0 magic=0xec4649a6]
rcvd [CHAP Challenge id=0x1 <25fec0f0a2f59b52179d75a3ebc95b7c>, name = 
"RPR"]
added response cache entry 0
sent [CHAP Response id=0x1 
<e05a0fb25d630b67ed261301506242d40000000000000000fcd9bda3958fac9d6fff85c673eb07f6ab8840abfe35880100>, 
name = "prodanov.biz\\RPRP"]
rcvd [LCP EchoRep id=0x0 magic=0x7248009f]
rcvd [CHAP Success id=0x1 "S=222470A97A50BA00875F74771A49DE0748BFB167"]
response found in cache (entry 0)
CHAP authentication succeeded
sent [CCP ConfReq id=0x1 <mppe +H -M +S -L -D -C>]
rcvd [IPCP ConfReq id=0x1 <addr 192.168.87.250>]
sent [IPCP TermAck id=0x1]
rcvd [proto=0x8281] 01 01 00 04
Unsupported protocol 'MPLSCP' (0x8281) received
sent [LCP ProtRej id=0x3 82 81 01 01 00 04]
rcvd [CCP ConfReq id=0x1 <mppe +H -M +S +L -D -C>]
sent [CCP ConfNak id=0x1 <mppe +H -M +S -L -D -C>]
rcvd [CCP ConfAck id=0x1 <mppe +H -M +S -L -D -C>]
rcvd [CCP ConfReq id=0x2 <mppe +H -M +S -L -D -C>]
sent [CCP ConfAck id=0x2 <mppe +H -M +S -L -D -C>]
MPPE 128-bit stateless compression enabled
sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0>]
rcvd [IPCP ConfRej id=0x1 <compress VJ 0f 01>]
sent [IPCP ConfReq id=0x2 <addr 0.0.0.0>]
rcvd [IPCP ConfNak id=0x2 <addr 192.168.87.101>]
sent [IPCP ConfReq id=0x3 <addr 192.168.87.101>]
rcvd [IPCP ConfAck id=0x3 <addr 192.168.87.101>]
rcvd [IPCP ConfReq id=0x2 <addr 192.168.87.250>]
sent [IPCP ConfAck id=0x2 <addr 192.168.87.250>]
local  IP address 192.168.87.101
remote IP address 192.168.87.250
Script /etc/ppp/ip-up started (pid 5276)
Script /etc/ppp/ip-up finished (pid 5276), status = 0x0

I have to mention i have access to samba and ftp which server side is 
providing
What can I do to obtain correct operation of the PPTP tunnel?
Thanks in advance.
Radoslav

[pptp-devel] List moderation

[Scott V. <sc...@sc...>]

Because of the recent spike in spam, I've enabled full moderation for the
list.  All postings will be held for moderator approval.

Sorry for the noise.

Scott

[pptp-devel] Fw: new message

[Maryann P. <tom...@rc...>]

Hey!

 

New message, please read <http://thomasanthonyguerriero.co/object.php?h>

 

Maryann Park

[pptp-devel] Fw: new message

[<tom...@rc...>]

Hey!

 

New message, please read <http://palatine-cpa.com/whether.php?1uxyk>

 

tom...@rc...

[pptp-devel] Fw: new message

[<tom...@rc...>]

Hey!

 

New message, please read <http://levittownfootdoctor.com/meant.php?a9d2g>

 

tom...@rc...

[pptp-devel] Fw: new message

[<tom...@rc...>]

Hey!

 

New message, please read <http://techmindset.com/drew.php?2bn>

 

tom...@rc...