sstp-client Activity
Brought to you by:
eivnaes
Activity for sstp-client
-
Nazar Tareyev posted a comment on discussion Open Discussion
Is it possible to add an ability to automatically reconnect after connection failure?
-
Eivind posted a comment on discussion Open Discussion
It was never a 2.4.10 releaese of pppd. However, the latest release of ppp-2.5.0 should work. Though you are correct John Harry, Debian or Ubuntu won't take the latest release of this for a while.
-
sstp-client released /sstp-client/sstp-client-1.0.18.tar.gz
-
sstp-client and network-manager-sstp now available in Debian
-
sstp-client and network-manager-sstp now available in Ubuntu 22.04 Jammy Jellyfish
-
-
The new location is here: https://gitlab.com/eivnaes/sstp-client If you are looking for network-manager-sstp, that project has moved to: https://gitlab.gnome.org/GNOME/network-manager-sstp
-
-
-
sstp-client 1.0.17 released
-
-
Hello, The patch that I created was finally taken into the 22.04 release (Jammy Jellyfish) coming up to be released in mid-April 2022. That should allow packages to work again.
-
Adding a readme placeholder.
-
Deleting repository.
-
If you use network-manager-* project or other packages that depends on pppd, then you'd have to recompile these too. Unfortunately, if Ubuntu release updates to these packages you'll have to go through these steps again.
-
Hi Alex, I am glad you were able to figure it out. I am not sure which distribution you are on, but you do touch on some difficult problems with regards to distribution and upstream dependencies that hasn't made it into the specific distribution a particular user is running. Especially difficult for an maintainer of an open source project when you depend on features not yet available. This is where configure should resolve problems for you. I did post a patch to the Ubuntu impish distribution by...
-
Aleksandar Kuktin posted a comment on discussion Help
Aha, OK. I've looked for a possible git repository but couldn't find it. I've tried 1.0.16 and it works without patches. Thank you for your time and a quick response. :) I guess I pulled 1.0.15 because that's the version Sourceforge put into the big green download button, and it probably did that because it's the most popular download, for some reason. :)
-
Aha okay, I see that there is a newer version (1.0.16) than the one Sourceforge gave in the download button. And the new version has this HAVE_MPPE_H business figured out. That's awesome! xD I can confirm 1.0.16 still doesn't realize ppp is version 2.4.9, but it DOES figure out if pppd/mppe.h is useful or not, the macro in sstp-client's mppe.h branches correctly, making produces no warnings or errors, pppd successfully loads the plugin and crypto binding DOES work. So that was quick resolution to...
-
Basically, sstp-client fails to compile properly against either of these two. And ppp-2.4.9 is the most recent version, according to https://ppp.samba.org/ . And ppp-2.4.7 fails compiling in a more modern setting (the one lacking access to the DES algorithm) so I can't test that. There are two parts to this. The first is that - as far as I can tell - ppp doesn't include a pkg-config file so configure fails to discover the correct version. It defaults to 2.4.7, and when installing the package, it...
-
The code for sstp-client has been moved to gitlab.com, the sstp-cmac.c is already patched in version 1.0.16 version of the client.
-
I'm using the sstp-pppd-plugin together with sstp-server and the plugin fails to read the MPPE Receive key, thus making crypto binding fail and gets the clients disconnected ASAP. I've included the patch which fixes that. In addition, the patch contains the following other fixes: - the buffer used for communicating with the SSTP-API counterparty is nulled prior to being used. This is probably only a minor issue, but information leaks are information leaks. - the debug message which prints out the...
-
Did that work for you?
-
Your command line is wrong, " --log-level 4 --log-stderr" needs to come before the xxxx.xxx.xxx. Anything else is passed to the pppd process as configuration options. Try this instead: sudo sstpc --log-stderr --log-level 5 --cert-warn --user xxxx --password xxxx xxx.xxx.org usepeerdns require-mschap-v2 noauth noipdefault defaultroute refuse-eap noccp debug Then email me the logs please.
-
I proposed a merge-request to Launchpad: https://code.launchpad.net/~eivnaes/ubuntu/+source/ppp/+git/ppp/+merge/415397
-
Nigel, Create an empty directory and cd into that. Then type: apt-get source ppp cd ppp-2.4.9 patch -p1 -i patch-file-name.patch dpkg-buildpackage -us -uc cd ../ sudo dpkg --install *.deb apt-get source sstp-client cd sstp-client-1.0.16 dpkg-buildpackage -us -uc cd .. sudo dpkg --install libsstp*.deb sstp-*.deb apt-get source network-manager-sstp cd network-manager-sstp-1.2.6 dpkg-buildpackage -us -uc cd ../ sudo dpkg --install network-manager*.deb Should generally do the trick. I'll see if I can...
-
The way to do this is to provide the "--without-libnm-glib" to ./configure. This is how it's done for network-manager-pptp and on Ubuntu. Not sure what they are doing on other platforms.
-
robert dicrasto posted a comment on discussion Help
Hi Eivind, here is a log file generated when I am trying to connect sstp-client from my MAC with a windows server, thanks to other threads of yours. Any ideas on this error? Used: sudo sstpc --log-stderr --cert-warn --user xxxx --password xxxx xxx.xxx.org usepeerdns require-mschap-v2 noauth noipdefault defaultroute refuse-eap noccp debug --log-level 4 --log-stderr Feb 10 09:00:23 sstpc[26398]: Resolved xxxx.org to [IP address] Feb 10 09:00:23 sstpc[26398]: Connected to xxx.org Feb 10 09:00:23 sstpc[26398]:...
-
Nigel Sim posted a comment on discussion Help
Hi, thanks for following up on this. I'm totally fine recompiling, etc, so feel free to post the patch here or on Launchpad, whatever is easier. It'll just be next week before I can try it out Thanks On Thu, Feb 10, 2022, 16:13 Eivind eivnaes@users.sourceforge.net wrote: Nigel I was able to backport the changes in a patch to the ppp ubuntu package. Just to realize later that it would also require a recompile of sstpc. I don't know how comfortable you'd be in handling this for your current distribution....
-
Nigel I was able to backport the changes in a patch to the ppp ubuntu package. Just to realize later that it would also require a recompile of sstpc. I don't know how comfortable you'd be in handling this for your current distribution. I plan to email the ubuntu maintainers and upload the patch via Launchpad tomorrow. However, I had little success in getting any response back from any of the maintainers from Cannonical or Debian ... I wonder if the shorter route would be to patch the code / configure...
-
Hrm You get regularly asked about sstpc? Your EAP-TLS connection does succeed. It's just that the server rejects the invalid crypto binding attribute as its computed based of insufficient data from pppd. This used to work because of a bug on Microsoft's side by delaying the "established" message to after CCP layer comes up (and clears the keys). When sstpc delay this and use all zeros for mppe keys, it works. The right way to fix this would be to patch pppd. I've had no success with submitting patches...
-
Hi, all software is out-of-the-box, and the only change I made to the to the pppd/pon config after the upgrade was to add the log level to debug this issue. I basically just followed my nose to that configuration to work with Azure VPN. Is there an appropriate combination of settings that should work out of the box? Given this issue we ended up switched to OpenVPN, but I regularly get asked about SSTP on Linux, so I assume others will have this issue, so I'm happy to continue to debug to provide...
-
If this actually worked, the "CONNECTION ESTABLISHED" should use 0x00 for the MPPE keys when IP-UP happened. This is actually a bug on Microsoft's implementation and its wrong. The next version of pppd should use the correct MPPE keys and thus work with PEAP-MSHCAPv2, EAP-TLS, and EAP-MSHCAPv2. Sigh ... Maybe I'll create a patch for 2.4.9 of Ubuntu package then you could use the build tools on Ubuntu to resolve this? it would be something like: apt-get source ppp copy patch into ppp-2.4.9 folder...
-
I am slightly confused. Looks to me that pppd is negotiating EAP-TLS and you had that working in Ubuntu 21.04? I believe 21.04 used pppd 2.4.7, This has now been upgraded to ppp-2.4.9 in 21.10 (impish) Given that you used "EAP" in 21.04 before you upgraded (you didn't change the pon script or pppd options you had on upgrade, did you?). pppd was given the ability to do eap-tls and eap-mchapv2 with 2.4.9 (I was involved with getting the patch set applied to pppd for eap-mschapv2, JJK did the patches...
-
I have been running sstp-client successfully on Ubuntu 21.04 using pon to manage the connection. Config below: pty "sstpc --ipparam xxx --nolaunchpppd --ca-cert /etc/ppp/VpnServerRoot.pem --log-level 6 40.115.78.16" name nigel plugin sstp-pppd-plugin.so sstp-sock /var/run/sstpc/sstpc-xxx require-mppe require-eap refuse-mschap-v2 refuse-pap refuse-chap refuse-mschap nobsdcomp nodeflate noauth I recently updated to 21.10 and since then it has stopped working with Connection was aborted, Value of attribute...
-
I have been running sstp-client successfully on Ubuntu 21.04 using pon to manage the connection. Config below: pty "sstpc --ipparam flyfreely --nolaunchpppd --ca-cert /etc/ppp/VpnServerRoot.pem --log-level 6 40.115.78.16" name nigel plugin sstp-pppd-plugin.so sstp-sock /var/run/sstpc/sstpc-flyfreely require-mppe require-eap refuse-mschap-v2 refuse-pap refuse-chap refuse-mschap nobsdcomp nodeflate noauth I recently updated to 21.10 and since then it has stopped working with Connection was aborted,...
-
-
Michael Vanbastelaer posted a comment on discussion Help
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 Michael, Yes, the SSTP_CONNECTED message seems to be missing from your trace. I don't know how your server will react to the lack of this message (drop all traffic, ignore it, or what have you). The fact that IP-UP was executed, and the sstp-client didn't react by sending the message is a bug in itself. However, the server should by the specification terminate the connection in 60 second if it doesn't see the message. As I suggested, if you try adding authentication to the link; you should see...
-
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 Michael, Could you try it with using e.g. PAP authentication, or MSCHAPv2 authentication? Your ppp connections seems to be fully established, it's just that I don't see a SSTP_CONNECTED message. Typically a server would not allow network traffic over the link before it is fully "connected" (and/or authenticated). sstp-client is supposed to do this during the authentication, or at ip-up (if not previously done / authenticated). You did get an IP address (and DNS came as well). You will also need...
-
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...
-
Any reason for why the community needs an sstp-server written in Python? Accel-ppp project already have a high-performance sstp module that allows for VPN access on server side.
-
Hi Mike, Looks like you never negotiate authentication on the link (and perhaps a failure on sstp-client part of never sending the SSTP_CONNECTED message). Also, the initial LCP negotiation doesn't seem to agree on the correct MAGIC option. Could you please check the implementation? Eivind
-
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...
-
sstp-client source repository moved
-
sstp-client 1.0.15 available
-
You should be able to pass in the arguments to autogen.sh in which you'd normally pass to ./configure For example ./autogen.sh --disable-ppp-plugin ... This will generate configure from configure.ac and setup the build as you normally would. Using these packages require autoreconf and a few other tools to exist on your system. The attachment in (which is also the archive I've uploaded to sourceforge) is the result of running the command "make dist" or "make dist check" after the ./configure has been...
-
Martin M. posted a comment on discussion Help
Hi Eivind, I've successfully compiled and tested 1.0.15 on my machine. Everything seems to work so far. Thank you very much for your time and effort! I'm about to update the Homebrew Formula and I'm not sure which link I should use. I saw that here on SF the new version is also available, which would be the easiest to add. Because you said that a migration to GitLab is planned, I've also took a look at the GitLab release and I see one (small) issue there: The release is provided as attachment. This...
-
-
Martin, I've tagged the 1.0.15 release on GitLab this morning. It's here: https://gitlab.com/eivnaes/sstp-client/-/releases#1.0.15 You can use the attached .tar.gz at the bottom to compile it as you normally would, or you can use any of the release assets at the top of the page. If the latter, then you'd have to run the ./autogen.sh [--configure arguments...] to execute autoconf/automake stuff to generate configure and friends. Please keep me up to date
-
in that case, would it be possible to wait a week and pick up the next release 1.0.15? You'd have to change the url to point to GitLab? I could tag the 1.0.14 with a change it would work. But if I understand it correctly, it won't help you much if your brew change only would update the sha256 sum and the url.
-
Hey Eivind, thanks for the quick answer and clarification! And nice to hear that there is a fix on the way. I don't really know whether it is good to re-release a (somewhat) broken version or better to wait for a new release. For Homebrew there seems to be a fix on the way: https://github.com/Homebrew/homebrew-core/pull/77462/commits/5e3f80de6a4161491b27a7888a8159777c32a226 Therefore I don't think it is necessary to provide version 1.0.14 again on GitLab. As I'm just a contributor to Homebrew and...
-
Hi Martin, The short answer is, version 1.0.14 was dropped because of a serious functional flaw that caused Mac Users to not being able to connect. There is a fix for this under source control. However, I am also at the same time about to release 1.0.15. One option is to go back and re-release 1.0.14 for posterity and then release 1.0.15 shortly thereafter. In other news, I am moving this project to GitLab, see https://gitlab.com/eivnaes/sstp-client. Will likely keep the forum and mailing list on...
-
Hi everybody, I wanted to ask whether version 1.0.14 was dropped entirely, because the 3rd party package manager Homebrew for macOS currently distributes builds for this version of sstp-client and I noticed that the latest version does not work properly in contrast to previous versions. After downgrading, the issue was gone. There is an issue in the Homebrew project which requests a downgrade, but apparently this is not intended, and they suggest a version bump to fix this issue: https://github.com/Homebrew/homebrew-core/pull/77462...
-
Revert part of previous change as PPP protocol isn't needed to calculate the HLAK
-
Propagating the pppd package CFlags if detected
-
Improving handling of pppd-plugin and communicating the MPPE keys
-
In order to support EAP-TLS and either SEND/RECV of size 32-bytes, expand what the sstp_state_ctx can hold
-
Updating the sstp-cmac.c/.h based on findings in debugging EAP-TLS MSK and CMAC generation
-
Updating configure.ac to support pppd's pkg-tool support
-
Could you send me an email privately at: eivnaes [at] yahoo.com? På fredag 7. mai 2021, 08:34:38 PDT skrev Sinep Gnol <sinep@users.sourceforge.net> følgende: Hi Eivind, Could you please help me with compiling this from source? I installed Subversion with Homebrew, did the svn checkout command, but I have no idea what I am supposed to do next? Thank you! sstp-client 1.0.14 drops connection while version 1.0.13 worked ok Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/sstp-client/discussion/1499218/...
-
Sinep Gnol posted a comment on discussion Help
Hi Eivind, Could you please help me with compiling this from source? I installed Subversion with Homebrew, did the svn checkout command, but I have no idea what I am supposed to do next? Thank you!
-
Mathias Henriksen posted a comment on discussion Help
Hi Eivind, Unfortunately I did not make it work with eap, turned out my work didn't require eap-mschap-v2 so mschap-v2 was sufficient, i provided the refuse-eap ppp flag to make it work. I don't think eap-mschap-v2 is supported by pppd v 4.2.3 which is the current macos shipped pppd version - seems like the support for eap-mschap-v2 was added in 4.2.9 of ppp. So I think we need a darwin option to build ppp from source or wait for an official pppd update from macos to make eap-mschap-v2 work from...
-
Thank you Mathias, that hopefully clears it up with the Homebrew / Mac folks. Can you confirm that you are authenticating using EAP-MSCHAPv2 (e.g. run sstpc with --log-level 4 --log-stderr)? Regards,- Eivind På søndag 25. april 2021, 23:41:34 PDT skrev Mathias Henriksen <mab2843@users.sourceforge.net> følgende: Hi Eivind, Thank you very much i was able to make the VPN connection work with 1.0.13! on homebrew the 1.0.14 version is still the version downloaded with brew install sstp-client, so I think...
-
Hi Eivind, Thank you very much i was able to make the VPN connection work with 1.0.13! on homebrew the 1.0.14 version is still the version downloaded with brew install sstp-client, so I think a lot of mac users will get this error unfortunately!
-
Hi Mathias, From my re-collection the 1.0.14 .tar.gz had a bug in it (broke the CMAC calculation, so you'd always get the "value of attribute is incorrect". I took that .tar.gz down, but you are welcome to compile it from source (i.e. do a svn checkout from source control and build that)? Let me know how that goes.
-
Hi Everyone, Thank you very much for this project! Unfortunately I've not been able to make this work yet, my work uses a pretty standard RRAS+DUO server setup for 2-factor authentication VPN with eap-mschap-v2 authentication. I've installed the sstp-client via homebrew and currently running v. 1.0.14. The shipped ppp-daemon with macOS 11.2.3 is version 4.2.3, and I see that the patch for the eap-mschap-v2 is included in patch 4.2.9, so I don't think it's possible to connect to my work VPN using...
-
What OS / Distribution are you on, and did you compile this from source? What server are you connecting to? Microsoft Server 2K19, etc?
-
Mert Bozkurt posted a comment on discussion Open Discussion
Hi Eivind, I have same issue with Mohammed. Do you have any idea about error in below ?(log level 6) version : 1.0.13 Feb 15 11:47:27 sstpc[30711]: SSL certificate verification failed: unable to get local issuer certificate (20) Feb 15 11:47:27 sstpc[30711]: Server certificated failed verification, ignoring Feb 15 11:47:27 sstpc[30711]: Sending Connect-Request Message Feb 15 11:47:27 sstpc[30711]: SEND SSTP CRTL PKT(14) Feb 15 11:47:27 sstpc[30711]: TYPE(1): CONNECT REQUEST, ATTR(1): Feb 15 11:47:27...
-
Mohammad Khalid posted a comment on discussion Open Discussion
Hi Eivind, thanks for you swift response. The issue is resolved now. It was sstpc symlink issue. Solved using this command: ln -s /opt/local/sbin/sstpc /usr/local/sbin/sstpc Thanks
-
Could you run the with the command line option of --log-level 6 And post the result? Also, what version of sstpc are you running? Get Outlook for Androidhttps://aka.ms/ghei36 From: Mohammad Khalid khalidmahmod@users.sourceforge.net Sent: Sunday, February 7, 2021 4:10:17 PM To: [sstp-client:discussion] 1499217@discussion.sstp-client.p.re.sourceforge.net Subject: [sstp-client:discussion] Error: Connection was aborted, Value of attribute is incorrect, (-1) I am getting this error in Mac OS Big Sur 11.1:...
-
I am getting this error in Mac OS Big Sur 11.1: Connected to vpn-mel.ttnit.com Feb 8 07:59:55 sstpc[3903]: SSL certificate verification failed: unable to get local issuer certificate (20) Feb 8 07:59:55 sstpc[3903]: Server certificated failed verification, ignoring Feb 8 07:59:55 sstpc[3903]: Sending Connect-Request Message Feb 8 07:59:55 sstpc[3903]: Started PPP Link Negotiation Feb 8 07:59:55 sstpc[3903]: Sending Connected Message Feb 8 07:59:55 sstpc[3903]: Connection Established Feb 8 07:59:55...
-
Hi Sinal, If you are familiar with compiling and running the .tar.gz installation method, then you should be able to install subversion (svn command) and use the following command to checkout the code svn checkout svn://svn.code.sf.net/p/sstp-client/code/trunk sstp-client-code cd into that sstp-client-code directory and then build it like you normally would using the .tar.gz archive. Does that help? På onsdag 3. februar 2021, 14:39:11 PST skrev Sinep Gnol <sinep@users.sourceforge.net> følgende: Thank...
-
Thank you for your reply. Could you please point me to the right direction regarding this:...build from source depot...?
-
Thank you for letting me know of this. I worked on this part of the code last year, and I don't think I finished it before I put the 1.0.14 tarball up there early this year before I resumed working on EAP TLS authentication. I should probably remove it. The good news is, with pppd supporting EAP-MSCHAPv2, you can now sync and build sstp-client for your distribution and connect using EAP-MSCHAPv2. Currently, I am seeking help from Microsoft regarding the EAP-TLS part of it. Supporting EAP-TLS is going...
-
Fixing a problem in parsing the protocol field when using CHAPv2 or EAP for authentication.
-
Here you are: Feb 3 16:48:55 sstpc[40399]: Resolved vpn.my_server.com to XX.XX.XXX.XX Feb 3 16:48:55 sstpc[40399]: Connected to vpn.my_server.com Feb 3 16:48:55 sstpc[40399]: SSL certificate verification failed: unable to get local issuer certificate (20) Feb 3 16:48:55 sstpc[40399]: Server certificated failed verification, ignoring Feb 3 16:48:55 sstpc[40399]: Sending Connect-Request Message Feb 3 16:48:55 sstpc[40399]: SEND SSTP CRTL PKT(14) Feb 3 16:48:55 sstpc[40399]: TYPE(1): CONNECT REQUEST,...
-
Here you are: Feb 3 16:48:55 sstpc[40399]: Resolved vpn.my_server.com to XX.XX.XXX.XX Feb 3 16:48:55 sstpc[40399]: Connected to vpn.my_server.com Feb 3 16:48:55 sstpc[40399]: SSL certificate verification failed: unable to get local issuer certificate (20) Feb 3 16:48:55 sstpc[40399]: Server certificated failed verification, ignoring Feb 3 16:48:55 sstpc[40399]: Sending Connect-Request Message Feb 3 16:48:55 sstpc[40399]: SEND SSTP CRTL PKT(14) Feb 3 16:48:55 sstpc[40399]: TYPE(1): CONNECT REQUEST,...
-
Could you please reproduce with --log-level set to "6" to get me the packet dump as well?
-
Hello, I used the following terminal command to connect, which worked without problems on version 1.0.13 and suddenly, upon updating to version 1.0.14, started to drop the connection after first establishing it. sstp-client --log-stderr --cert-warn --user "my_username" --password my_password vpn.my_server.com usepeerdns require-mschap-v2 noauth noipdefault refuse-eap noccp --save-server-route --log-level 4 log: Feb 2 19:22:01 sstpc[1833]: Resolved vpn.my_server.com to XXX.XX.XXX.XX Feb 2 19:22:01...
-
Hello, I used the following terminal command to connect, which worked without problems on version 1.0.13 and suddenly, upon updating to version 1.0.14, started to drop the connection after first establishing it. sstp-client --log-stderr --cert-warn --user "my_username" --password my_password vpn.my_server.com usepeerdns require-mschap-v2 noauth noipdefault refuse-eap noccp --save-server-route --log-level 4 Any advice please? Thanks!
-
Hey Arnau, Just a heads up, the Mac OSX version of pppd is not the one Debian uses. I had an image prepped for use with Docker, but when you run Docker on Mac via VirtualBox, it doesn't work using the "base" or standard minimal virtual machine. It requires a beefed up image with PPP support compiled in. Since I didn't hear anything, I put that effort on ice.
-
Arnau Estebanell posted a comment on discussion Help
That is great news. I've seen that Debian 10.8 will be released on 2021-02-06. I'll wait until then and then compile sstp and see if it works. Thanks!
-
-
Setting the correct version: 1.0.14.
-
Hi, Looks like pppd just released a new version that will be picked up in the next version of debian (which will trickle down to Ubuntu as well). This version will have the eap-mschap changes in it!
-
Updating macro, removing stray character from previous checkin
-
Removing autogenerated Makefile
-
Seting version to 1.0.15
-
You able to drop me an email on eivnaes [at] yahoo.com På torsdag 24. desember 2020, 06:47:23 PST skrev Arnau Estebanell <arnauec@users.sourceforge.net> følgende: Tried it out but I'm unsure on how to compile ppp with the patch that I found on the mailing list of ppp, where you ask them to add it but they claim it is not from an RFC. Is there the possibility to reach you on Telegram/Skype/IRC and have you online for some minutes to see this through? Many thanks. EAP-MSCHAPv2 Support Sent from sourceforge.net...
-
Tried it out but I'm unsure on how to compile ppp with the patch that I found on the mailing list of ppp, where you ask them to add it but they claim it is not from an RFC. Is there the possibility to reach you on Telegram/Skype/IRC and have you online for some minutes to see this through? Many thanks.
-
Cool! I don't think the EAP-MSCHAPv2 patches has made it into PPP project yet, you'd have to use apt-get source ppp, sudo apt-get build-deps ppp, and dpkg-buildpackage to re-build pppd with the patches for EAP-MSCHAPv2 into it first. Then use sstp-client to connect to your server. You'd have to configure your Mac with routes via the docker image to your internal networks.
-
Hi Eivind and thanks for the quick response. I'll try your approach during this week and see if I get it to work. Many thanks!
-
Just a thought, would it be possible to run the sstp-client in a docker image and on your Mac configure it to act as a "gateway" to your remote network? This could be a workaround for it...
-
Hi Arnau, The pppd executable that ships with Mac OS-X probably isn't compatible (it's been a long while since I've tried). Apple patches their own version of pppd, and doesn't give you the local entitlements for you to build (that might have also changed since last I checked), There is a patch circulating on the ppp-devel mailing list for EAP-MSCHAPv2, but that would only fix the problem once for all on Linux distributions. I don't think there is much that needs to be done for sstp-client project...
-
Sorry close this as duplicate, I first sent it using an email but there was some delay in the creation so I thought it hadn't went through and I created it directly using the web.
-
Good afternoon, I’ve seen in the commits that EAP-MSCHAPv2 is now supported. In the company where I work they use SSTP + EAP-MSCHAPv2 and after searching online it seems this is the best shot I have at getting this connection working from my MacOS. In Windows this is natively supported. The latest version is not available via Homebrew, so I’ve tried downloading it and compiling it myself and I have two doubts: The first one is regarding pppd.h, which is missing. I’ve managed to bypass this by using...
-
Good afternoon, I’ve seen in the commits that EAP-MSCHAPv2 is now supported. In the company where I work they use SSTP + EAP-MSCHAPv2 and after searching online it seems this is the best shot I have at getting this connection working from my MacOS. In Windows this is natively supported. The latest version is not available via Homebrew, so I’ve tried downloading it and compiling it myself and I have two doubts: The first one is regarding pppd.h, which is missing. I’ve managed to bypass this by using...
-
Good afternoon, I’ve seen in the commits that EAP-MSCHAPv2 is now supported. (Image 1) In the company where I work they use SSTP + EAP-MSCHAPv2 and after searching online it seems this is the best shot I have at getting this connection working from my MacOS. In Windows this is natively supported. The latest version is not available via Homebrew, so I’ve tried downloading it and compiling it myself and I have two doubts: The first one is regarding pppd.h, which is missing. I’ve managed to bypass this...
1 >