Dear all,
I saw on the SE web pages that the sstp client for freebsd is supported so I installed softether5 to a freebsd 13 installed in a virtualbox environment.
When I try to connect to my MS server with sstp configured and tested with winndows and linux clietns I can see an error message:
The connection has either been disconnected or failed. Cause: Connection to the server failed. Check network connection to the server...
I tried to telnet to my MS server from the freebsd box, so I suppose it is not a freebsd problem.
I successfully created a virtual network device, account, set password. The one thing I'm not sure is the virtual HUB as on the other sstp clients I did not need this information.
Also tried to connect to an account from another post:
host: public-vpn-185.opengw.net/tcp
port: 443
vhub: VPNGATE
user: vpn
pass: vpn
but that either did not work.
Can anyone help me to see if this setup can work and if yes what did I do wrong.
Kind regards,
SE developer edition freebsd client
-
- Posts: 1486
- Joined: Sun Feb 14, 2021 10:31 am
Re: SE developer edition freebsd client
No, SE has no SSTP client to connect to a MS server. Perhaps you confuse it with SE server which can accept connections from SSTP clients.
FreeBSD SE client can connect to public-vpn-185 - is up and running, just verified...
FreeBSD SE client can connect to public-vpn-185 - is up and running, just verified...
Code: Select all
VPN Client>AccountStatusGet public-vpn-185
AccountStatusGet command - Get Current VPN Connection Setting Status
Item |Value
------------------------------------------+--------------------------------------------------------
VPN Connection Setting Name |public-vpn-185
Session Status |Connection Completed (Session Established)
VLAN ID |-
Server Name |public-vpn-185.opengw.net/tcp
Port Number |TCP Port 443
Server Product Name |SoftEther VPN Server (64 bit)
Server Version |4.32
Server Build |Build 9729
Connection Started at |2022-08-13 (Sat) 09:14:38
First Session has been Established since |2022-08-13 (Sat) 09:14:40
Current Session has been Established since|2022-08-13 (Sat) 09:14:40
Number of Established Sessions |1 Times
Half Duplex TCP Connection Mode |No (Full Duplex Mode)
VoIP / QoS Function |Disabled
Number of TCP Connections |1
Maximum Number of TCP Connections |1
Encryption |Enabled (Algorithm: AES128-SHA)
Use of Compression |No (No Compression)
Physical Underlay Protocol |Standard TCP/IP (IPv4)
|IPv4 UDPAccel_Ver=2 ChachaPoly_OpenSSL UDPAccel_MSS=1309
UDP Acceleration is Supported |Yes
UDP Acceleration is Active |Yes
...
Bridge / Router Mode |No
Monitoring Mode |No
Outgoing Data Size |16,264 bytes
Incoming Data Size |20,305 bytes
Outgoing Unicast Packets |2 packets
Outgoing Unicast Total Size |104 bytes
Outgoing Broadcast Packets |14 packets
Outgoing Broadcast Total Size |1,739 bytes
Incoming Unicast Packets |5 packets
Incoming Unicast Total Size |866 bytes
Incoming Broadcast Packets |13 packets
Incoming Broadcast Total Size |4,446 bytes
The command completed successfully.
-
- Posts: 5
- Joined: Fri Aug 12, 2022 5:06 pm
Re: SE developer edition freebsd client
Hi Solo,
Not confusing, thought that:
FreeBSD (32bit, 64bit) (Stable Edition: Server and Bridge only, Developer Edition: Client is also supported),
meant that SE had a client that can connect to an MS server via sstp.
Thank you for your clarification. I have to look for other options if there are any.
Kind regards,
Not confusing, thought that:
FreeBSD (32bit, 64bit) (Stable Edition: Server and Bridge only, Developer Edition: Client is also supported),
meant that SE had a client that can connect to an MS server via sstp.
Thank you for your clarification. I have to look for other options if there are any.
Kind regards,
-
- Posts: 5
- Joined: Fri Aug 12, 2022 5:06 pm
Re: SE developer edition freebsd client
Hi Solo,
Even doe I now know I can not connect to my MS server I wanted to check what did I do wrong as my connection to the public server.
After I issue an AccountConnect test command, I get:
So, I'm obviously doing something wrong. I'm using the developer edition in an virtualbox envirorment with freebsd 13.
Kind regards,
Even doe I now know I can not connect to my MS server I wanted to check what did I do wrong as my connection to the public server.
Code: Select all
VPN Client>accountget test
AccountGet command - Get Setting of VPN Connection Setting
Item |Value
-----------------------------------------------------+--------------------------------
VPN Connection Setting Name |test
Destination VPN Server Host Name |public-vpn-185.opengw.net/tcp
Destination VPN Server Port Number |443
Destination VPN Server Virtual Hub Name |VPNGATE
Proxy Server Type |Direct TCP/IP Connection
Verify Server Certificate |Disable
Device Name Used for Connection |vpn0
Authentication Type |Standard Password Authentication
User Name |vpn
Number of TCP Connections to Use in VPN Communication|1
Interval between Establishing Each TCP Connection |1
Connection Life of Each TCP Connection |Infinite
Use Half Duplex Mode |Disable
Encryption by SSL |Enable
Data Compression |Disable
Connect by Bridge / Router Mode |Disable
Connect by Monitoring Mode |Disable
No Adjustment for Routing Table |Disable
Do not Use QoS Control Function |Disable
Disable UDP Acceleration |Disable
The command completed successfully.
Code: Select all
VPN Client>accountstatusget test
AccountStatusGet command - Get Current VPN Connection Setting Status
Item |Value
----------------------------------------+-------------------------
VPN Connection Setting Name |test
Session Status |Retrying
Connection Started at |2022-08-13 (Sat) 19:23:05
First Session has been Established since|-
Number of Established Sessions |0 Times
The command completed successfully.
VPN Client>accountlist test
AccountList command - Get List of VPN Connection Settings
Item |Value
----------------------------+------------------------------------------------------------
VPN Connection Setting Name |Chipoteka
Status |Offline
VPN Server Hostname |sechip.dyndns.org:44300 (Direct TCP/IP Connection)
Virtual Hub |CHIPOTEKA
Virtual Network Adapter Name|vpn0
----------------------------+------------------------------------------------------------
VPN Connection Setting Name |test
Status |Connecting
VPN Server Hostname |public-vpn-185.opengw.net/tcp:443 (Direct TCP/IP Connection)
Virtual Hub |VPNGATE
Virtual Network Adapter Name|vpn0
The command completed successfully.
Kind regards,
-
- Posts: 1486
- Joined: Sun Feb 14, 2021 10:31 am
Re: SE developer edition freebsd client
Hello, I am searching SoftEtherVPN-5.02.5180.tar.xz change log for this groundbreaking feature. Please quote the section announcing support of MS-SSTP protocol in SoftEther's VPN client.
-
- Posts: 5
- Joined: Fri Aug 12, 2022 5:06 pm
-
- Posts: 5
- Joined: Fri Aug 12, 2022 5:06 pm
Re: SE developer edition freebsd client
This is not stated explicitly, I just assumed it, obviously not true.
Kind regards,
Kind regards,
-
- Posts: 1486
- Joined: Sun Feb 14, 2021 10:31 am
Re: SE developer edition freebsd client
You refer to this statement: "FreeBSD (32bit, 64bit) (Stable Edition: Server and Bridge only, Developer Edition: Client is also supported)". The client in this context is the SoftEther VPN protocol client and that's why you earlier wondered "the one thing I'm not sure is the virtual HUB as on the other sstp clients I did not need this information" - indeed not.
If SoftEther client had supported multiple VPN protocols then you'd have a selection of them to choose from in the setup instead of only a virtual HUB.
That settled, how's your public-vpn-185 test going?
If SoftEther client had supported multiple VPN protocols then you'd have a selection of them to choose from in the setup instead of only a virtual HUB.
That settled, how's your public-vpn-185 test going?