We extensively use PPTP client in ROS 6.

Don't ask why. Yes, I feel ashamed, no I cannot stop using it.

And for a number of reasons I want to upgrade to ROS 7.

I am OK with the big red warning in ROS7 saying that PPTP is substandard. I agree, it is.

But it does not work.

This is what we have:

/interface pptp-client
add allow=mschap2 connect-to=xx.xx.xx.xx disabled=no \
name=pptp-out1 user=xxxxxx password=xxxxxx

No firewall. Nothing else, just an IP address on a single ethernet interface and a gateway set.

It works in 6. It doesn't in 7.
Tried in RB2011, RB3011, RB433, hap ac lite, hap ac2, RBLHGR, vmware/x86. I will try on RBLHGGR as soon as it arrives (well, probably not, I got the message already).
It is the same on any hardware - works in 6, fails in 7.

What I get in the log:

jan/02/1970 00:09:54 system,info route 0.0.0.0 added by admin
jan/02/1970 00:14:06 pptp,ppp,info pptp-out1: initializing...
jan/02/1970 00:14:06 pptp,ppp,info pptp-out1: connecting...
jan/02/1970 00:14:06 system,info device added by admin
jan/02/1970 00:14:06 pptp,ppp,info pptp-out1: terminating...
jan/02/1970 00:14:06 pptp,ppp,info pptp-out1: disconnected
jan/02/1970 00:14:06 pptp,ppp,info pptp-out1: initializing...
jan/02/1970 00:14:06 pptp,ppp,info pptp-out1: connecting...
jan/02/1970 00:14:07 pptp,ppp,info pptp-out1: terminating...
jan/02/1970 00:14:07 pptp,ppp,info pptp-out1: disconnected

Where to debug next?

Looks like it is fixed in ROS 7.7 .

Let's upgrade!

thank you for sharing

I gave up.
Created an L2tp server on the side that had an ip4 address, set profile for the ip pool, created the secret
then created the client l2tp on the remote - dynamic ip, firewalled starlink setup - and it worked great. I didn't have time to dicker around with the PPTP issues between 6 and 7. I've already got my hands full trying to make V6 and V7 ospf play nice together.