Michael Vanbastelaer

Hi Eivind, Thank you for your explanation. I was able to fix the issue and establish connection! As it turns out, it is due to lack of authentication. With some changes to the iptable I was also able to browse the Internet. Best, Mike

Hi Eivind, Hmmm. I am still confused (through no fault of your explanation, of course!). If authentication failed, why would PPP connection be established after all? From other dicussions in this forum, I saw sstp-client would output something like this: ... May 28 04:31:33 sstpc[8073]: Sending Connected Message May 28 04:31:33 sstpc[8073]: SSTP CRTL PKT(112) May 28 04:31:33 sstpc[8073]: TYPE(4): CONNECTED, ATTR(1): May 28 04:31:33 sstpc[8073]: CRYPTO BIND(3): 104 May 28 04:31:33 sstpc[8073]: Connection...

Hi Eivind, Thank you for your quick response. I am not sure I completely understand your suggestion (mostly likely due to my lack of thorough understanding of this topic, so I apologize). Are you suggesting that: 1. SSTP connection was never established because sstp-client failed to send SSTP_CONNECTED message? or 2. SSTP connection was indeed established, but PPP link negotiation (through LCP I presume) did not succeed because the client and the server cannot agree on the MAGIC option? I suspect...

Hi, First of all, thanks for your application. I am working on a research project and running this SSTP server. The server is running on a Ubuntu VM. I then use sstp-client (1.0.15 from Homebrew) on my Mac to connect to it: sudo /usr/local/sbin/sstpc --log-level 6 --log-stderr --cert-warn --user user --password 'password' 192.168.33.10:443 usepeerdns noauth noipdefault nodefaultroute refuse-eap noccp debug logfile tmp.log The output seems to suggest that PPP link negotiation did not succeed because...