Page 1 of 1

OSX SE-VPN Client

Posted: Mon Jan 20, 2014 10:16 am
by dragon2611
Has anyone had any luck getting the SE-VPN client working on OSX

I can get Ovpn or L2tp/IPSEC to work, but I thought I'd give the SE-VPN client a try

Seemingly the client compiles ok from the recently released sourcecode and I can run it but I can't seem to create the vpn interface

VPN Client>niccreate
NicCreate command - Create New Virtual Network Adapter
Virtual Network Adapter Name: vpn1

Error occurred. (Error code: 33)
Unsupported.
VPN Client>

Re: OSX SE-VPN Client

Posted: Tue Jan 21, 2014 7:50 pm
by dnobori

Re: OSX SE-VPN Client

Posted: Fri Feb 07, 2014 6:04 pm
by calimansi
I tried the patch last night.

Everything compiles, but I cannot create a virtual network adapter. Same error as the OP.

Please advise as it seems the client only works through windows. I'd rather use softether compared to openvpn.

Thanks.

Re: OSX SE-VPN Client

Posted: Sun Mar 02, 2014 9:03 am
by calimansi
If anyone has gotten the OSX softether client working, please post a tutorial here. Hopefully the client does not only work in Windows.

Thanks.

Re: OSX SE-VPN Client

Posted: Fri Mar 21, 2014 1:50 am
by theplacetobe
I tested today with the just released 4.06 package. After installing the tun driver I was able to create a nic but then after creating the vpn it hangs on "Connecting".

Then when inspecting the virtual nic using the nicgetsetting command it gives met the "error code: 33 unsupported" also.

Re: OSX SE-VPN Client

Posted: Wed Mar 26, 2014 1:10 am
by calimansi
The last post gave me some guidance. The OSX tuntap driver needs to be installed. I installed this one:

http://tuntaposx.sourceforge.net

I am able to run the niccreate command successfully as long as everything is started with 'sudo.'

Everything connects so far, but still isn't routing through the client. I believe I need to use pfctl to change how everything is routed. Does anyone know how to do this?

Also, once connected, I noticed that vpnclient uses 100% cpu resources. Is there a reason for this? I'm using version 4.06.

Re: OSX SE-VPN Client

Posted: Fri Feb 20, 2015 5:13 am
by aubble
Did you ever figure it out? How to route?

Re: OSX SE-VPN Client

Posted: Tue Oct 27, 2015 12:15 pm
by brokenglish
Has this been resolved? I used the built-in MacOS VPN client flawlessly.

Re: OSX SE-VPN Client

Posted: Tue Oct 27, 2015 12:48 pm
by aubble
It's still experimental so I don't believe so, I just use OpenVPN with tunnelblick. I made my own proxy in the middle to tunnel it through pure TLS so it is functionally equivelent to softether (you can probably just use stunnel but it was fun). https://github.com/nhooyr/TunneLS