Hi,
I am a beginner with SoftEther.
I wanted to setup a L2TP/IPSec config for my Android mobile. I think it is a very simple situation.
I can connect to the server but it was written in the log no DHCP server and no IP address for PPP session so the connection was terminated. It is true because I don't have any DHCP server on the VPN server machine.
I want a machine-to-machine setup now and I thought I can use the built in VirtualDHCP server. It is enabled and with the DhcpGet command I can see the DHCP range (192.168.30.0/24). The DHCP server is enabled.
Why I can't get IP address from that DHCP server then?
TIA,
VirtualDHCP cannot work
-
theodisbutler
- Posts: 31
- Joined: Mon Feb 24, 2014 12:12 am
Re: VirtualDHCP cannot work
I have found that some commands I executed using the vpncmd program didn't get executed on the server. I would verify with the GUI that the VirtualDHCP server is actually running and check the log file.
However, more than likely, maybe you have a firewall or antivirus blocking the connection.
However, more than likely, maybe you have a firewall or antivirus blocking the connection.
-
aruzsi
- Posts: 18
- Joined: Mon Oct 05, 2015 11:00 am
Re: VirtualDHCP cannot work
The server is running on Linux machine, so no antivirus.
There is firewall! What do I have to check? I don't have any rules for the server? Do I heed any new virtual interfaces?
There is firewall! What do I have to check? I don't have any rules for the server? Do I heed any new virtual interfaces?
-
bbk1674
- Posts: 23
- Joined: Wed Apr 08, 2015 4:33 am
Re: VirtualDHCP cannot work
try opening port UDP 1701 in your firewall, and as well I recommend Using the windows server manager tool for all servers you have for GUI. you can have it for 10 soft-ether servers on your laptop.
if that port didn't help. for IPsec you may have to open UDP 500 and 4500 but do some googling on that.
if you are using a VPS like myself, I had to Use the SecureNAT and DHCP together even though it isn't recommended, but creating a local bridge didn't help/work on a VPS with a virtual network interface and I have a question open on this subject in this Forum waiting for Final Resolution.
http://www.vpnusers.com/viewtopic.php?f=7&t=4952
it is possible enabling SecureNAT slows down some functions, that is the information I am also waiting for confirmation of.
I hope I could helps
if that port didn't help. for IPsec you may have to open UDP 500 and 4500 but do some googling on that.
if you are using a VPS like myself, I had to Use the SecureNAT and DHCP together even though it isn't recommended, but creating a local bridge didn't help/work on a VPS with a virtual network interface and I have a question open on this subject in this Forum waiting for Final Resolution.
http://www.vpnusers.com/viewtopic.php?f=7&t=4952
it is possible enabling SecureNAT slows down some functions, that is the information I am also waiting for confirmation of.
I hope I could helps
-
aruzsi
- Posts: 18
- Joined: Mon Oct 05, 2015 11:00 am
Re: VirtualDHCP cannot work
I think UDP 1701 is closed. Who uses this port?
UDP 500 and 4500 are open so I can connect to the server except no IP from VirtualDHCP server.
How can I use windows GUI with a remote Linux server? On which port will be communicate each other?
My server is running on a DO VM. Do I have to install dnsmasq for DHCP instead of the built in VirtualDHCP?
TIA,
UDP 500 and 4500 are open so I can connect to the server except no IP from VirtualDHCP server.
How can I use windows GUI with a remote Linux server? On which port will be communicate each other?
My server is running on a DO VM. Do I have to install dnsmasq for DHCP instead of the built in VirtualDHCP?
TIA,
-
bbk1674
- Posts: 23
- Joined: Wed Apr 08, 2015 4:33 am
Re: VirtualDHCP cannot work
1701 UDP port is used for l2tp
You can use the graphic interface from Windows by using almost any port 443 or 992 and 5555
Just install it on your Windows computer and a day server to manage it's very easy to set up
You can use the graphic interface from Windows by using almost any port 443 or 992 and 5555
Just install it on your Windows computer and a day server to manage it's very easy to set up
-
aruzsi
- Posts: 18
- Joined: Mon Oct 05, 2015 11:00 am
Re: VirtualDHCP cannot work
Then UDP 1701 is open.
443 (https) is used by web server. Maybe 992 or 5555. Do I have to configure something (except firewall!) using win GUI?
I don't understand why there is a WEB config interface. I use Windows very rarely.
TIA,
443 (https) is used by web server. Maybe 992 or 5555. Do I have to configure something (except firewall!) using win GUI?
I don't understand why there is a WEB config interface. I use Windows very rarely.
TIA,
-
bbk1674
- Posts: 23
- Joined: Wed Apr 08, 2015 4:33 am
Re: VirtualDHCP cannot work
Yes you can use 992 or any other port that is open on the receiving end on the server.
The Windows GUI makes it very easy to use and while nothing beats soft ether in my opinion since it does so many functions that no other software does in one place for Vpn specially if you want something for Vpn and with A Web interface you can try pfSense or opensense
The Windows GUI makes it very easy to use and while nothing beats soft ether in my opinion since it does so many functions that no other software does in one place for Vpn specially if you want something for Vpn and with A Web interface you can try pfSense or opensense
-
aruzsi
- Posts: 18
- Joined: Mon Oct 05, 2015 11:00 am
Re: VirtualDHCP cannot work
The communication is not clear for me now but first of all what do I have to download for Win GUI Manager?
TIA,
TIA,
-
aruzsi
- Posts: 18
- Joined: Mon Oct 05, 2015 11:00 am
Re: VirtualDHCP cannot work
I checked my VPN machine.
UDP 1701 is not open! Instead of this fact L2TP/IPSec was able to connect but no IP address because of missing DHCP server or VirtualDHCP problem:
2015-10-05 12:43:33.980 IPsec Client 2 (my_client:500 -> my_server:500): A new IPsec client is created.
2015-10-05 12:43:33.980 IPsec IKE Session (IKE SA) 2 (Client: 2) (my_client:500 -> my_server:500): A new IKE SA (Main Mode) is created. Initiator Cookie: 0x62BD167CD2AF92A7, Responder Cookie: 0x42873C8C8B9CD5B3, DH Group: MODP 1024 (Group 2), Hash Algorithm: SHA-1, Cipher Algorithm: AES-CBC, Cipher Key Size: 256 bits, Lifetime: 4294967295 Kbytes or 28800 seconds
2015-10-05 12:43:37.521 IPsec Client 3 (my_client:500 -> my_server:500): A new IPsec client is created.
2015-10-05 12:43:37.521 IPsec IKE Session (IKE SA) 3 (Client: 3) (my_client:500 -> my_server:500): A new IKE SA (Main Mode) is created. Initiator Cookie: 0x62BD167CD2AF92A7, Responder Cookie: 0x8B89F962CD9443B5, DH Group: MODP 1024 (Group 2), Hash Algorithm: SHA-1, Cipher Algorithm: AES-CBC, Cipher Key Size: 256 bits, Lifetime: 4294967295 Kbytes or 28800 seconds
2015-10-05 12:43:37.771 IPsec Client 2 (my_client:4500 -> my_server:4500): The port number information of this client is updated.
2015-10-05 12:43:37.771 IPsec Client 2 (my_client:4500 -> my_server:4500):
2015-10-05 12:43:37.771 IPsec IKE Session (IKE SA) 2 (Client: 2) (my_client:4500 -> my_server:4500): This IKE SA is established between the server and the client.
2015-10-05 12:43:38.984 IPsec IKE Session (IKE SA) 2 (Client: 2) (my_client:4500 -> my_server:4500): The client initiates a QuickMode negotiation.
2015-10-05 12:43:38.984 IPsec ESP Session (IPsec SA) 2 (Client: 2) (my_client:4500 -> my_server:4500): A new IPsec SA (Direction: Client -> Server) is created. SPI: 0x4CECBAF0, DH Group: (null), Hash Algorithm: SHA-1, Cipher Algorithm: AES-CBC, Cipher Key Size: 256 bits, Lifetime: 4294967295 Kbytes or 28800 seconds
2015-10-05 12:43:38.984 IPsec ESP Session (IPsec SA) 2 (Client: 2) (my_client:4500 -> my_server:4500): A new IPsec SA (Direction: Server -> Client) is created. SPI: 0xA7F6099, DH Group: (null), Hash Algorithm: SHA-1, Cipher Algorithm: AES-CBC, Cipher Key Size: 256 bits, Lifetime: 4294967295 Kbytes or 28800 seconds
2015-10-05 12:43:39.776 IPsec IKE Session (IKE SA) 2 (Client: 2) (my_client:4500 -> my_server:4500): The server initiates a QuickMode negotiation.
2015-10-05 12:43:39.776 IPsec ESP Session (IPsec SA) 3 (Client: 2) (my_client:4500 -> my_server:4500): A new IPsec SA (Direction: Client -> Server) is created. SPI: 0x5F4C2286, DH Group: (null), Hash Algorithm: SHA-1, Cipher Algorithm: AES-CBC, Cipher Key Size: 256 bits, Lifetime: 4294967295 Kbytes or 28800 seconds
2015-10-05 12:43:39.776 IPsec ESP Session (IPsec SA) 3 (Client: 2) (my_client:4500 -> my_server:4500): A new IPsec SA (Direction: Server -> Client) is created. SPI: 0x0, DH Group: (null), Hash Algorithm: SHA-1, Cipher Algorithm: AES-CBC, Cipher Key Size: 256 bits, Lifetime: 4294967295 Kbytes or 28800 seconds
2015-10-05 12:43:41.776 IPsec IKE Session (IKE SA) 2 (Client: 2) (my_client:4500 -> my_server:4500): The server initiates a QuickMode negotiation.
2015-10-05 12:43:41.776 IPsec ESP Session (IPsec SA) 4 (Client: 2) (my_client:4500 -> my_server:4500): A new IPsec SA (Direction: Client -> Server) is created. SPI: 0x9EB3AABD, DH Group: (null), Hash Algorithm: SHA-1, Cipher Algorithm: AES-CBC, Cipher Key Size: 256 bits, Lifetime: 4294967295 Kbytes or 28800 seconds
2015-10-05 12:43:41.776 IPsec ESP Session (IPsec SA) 4 (Client: 2) (my_client:4500 -> my_server:4500): A new IPsec SA (Direction: Server -> Client) is created. SPI: 0x0, DH Group: (null), Hash Algorithm: SHA-1, Cipher Algorithm: AES-CBC, Cipher Key Size: 256 bits, Lifetime: 4294967295 Kbytes or 28800 seconds
2015-10-05 12:43:42.566 IPsec Client 2 (my_client:4500 -> my_server:4500): The L2TP Server Module is started.
2015-10-05 12:43:42.717 IPsec ESP Session (IPsec SA) 3 (Client: 2) (my_client:4500 -> my_server:4500): The SPI which has been pending is now set. New SPI: 0x4722B13
2015-10-05 12:43:42.717 IPsec ESP Session (IPsec SA) 3 (Client: 2) (my_client:4500 -> my_server:4500): This IPsec SA is established between the server and the client.
2015-10-05 12:43:42.729 IPsec ESP Session (IPsec SA) 2 (Client: 2) (my_client:4500 -> my_server:4500): This IPsec SA is established between the server and the client.
2015-10-05 12:43:42.759 IPsec ESP Session (IPsec SA) 4 (Client: 2) (my_client:4500 -> my_server:4500): The SPI which has been pending is now set. New SPI: 0xB236848
2015-10-05 12:43:42.759 IPsec ESP Session (IPsec SA) 4 (Client: 2) (my_client:4500 -> my_server:4500): This IPsec SA is established between the server and the client.
2015-10-05 12:43:43.092 L2TP PPP Session [my_client:1701]: A new PPP session (Upper protocol: L2TP) is started. IP Address of PPP Client: my_client (Hostname: "anonymous"), Port Number of PPP Client: 1701, IP Address of PPP Server: my_server, Port Number of PPP Server: 1701, Client Software Name: "L2TP VPN Client", IPv4 TCP MSS (Max Segment Size): 1314 bytes
2015-10-05 12:43:43.344 On the TCP Listener (Port 0), a Client (IP address my_client, Host name "BC9C057B.mobile.mydomain", Port number 1701) has connected.
2015-10-05 12:43:43.344 For the client (IP address: my_client, host name: "BC9C057B.mobile.mydomain", port number: 1701), connection "CID-44" has been created.
2015-10-05 12:43:43.344 SSL communication for connection "CID-44" has been started. The encryption algorithm name is "(null)".
2015-10-05 12:43:43.344 [HUB "MY_HUB"] The connection "CID-44" (IP address: my_client, Host name: BC9C057B.mobile.mydomain, Port number: 1701, Client name: "L2TP VPN Client", Version: 4.08, Build: 9449) is attempting to connect to the Virtual Hub. The auth type provided is "External server authentication" and the user name is "MY_USERNAME".
2015-10-05 12:43:43.344 [HUB "MY_HUB"] Connection "CID-44": Successfully authenticated as user "MY_USERNAME".
2015-10-05 12:43:43.344 [HUB "MY_HUB"] Connection "CID-44": The new session "SID-MY_USERNAME-[L2TP]-2" has been created. (IP address: my_client, Port number: 1701, Physical underlying protocol: "Legacy VPN - L2TP")
2015-10-05 12:43:43.344 [HUB "MY_HUB"] Session "SID-MY_USERNAME-[L2TP]-2": The parameter has been set. Max number of TCP connections: 1, Use of encryption: No, Use of compression: No, Use of Half duplex communication: No, Timeout: 20 seconds.
2015-10-05 12:43:43.344 [HUB "MY_HUB"] Session "SID-MY_USERNAME-[L2TP]-2": VPN Client details: (Client product name: "L2TP VPN Client", Client version: 408, Client build number: 9449, Server product name: "SoftEther VPN Server (32 bit) (Open Source)", Server version: 408, Server build number: 9449, Client OS name: "L2TP VPN Client", Client OS version: "-", Client product ID: "-", Client host name: "anonymous", Client IP address: "my_client", Client port number: 1701, Server host name: "my_server", Server IP address: "my_server", Server port number: 1701, Proxy host name: "", Proxy IP address: "0.0.0.0", Proxy port number: 0, Virtual Hub name: "MY_HUB", Client unique ID: "AC3CA4B1E312EB33811C86A069C0FB99")
2015-10-05 12:43:43.435 L2TP PPP Session [my_client:1701]: Trying to request an IP address from the DHCP server.
2015-10-05 12:43:47.529 IPsec IKE Session (IKE SA) 3 (Client: 3) (my_client:500 -> my_server:500): This IKE SA is deleted.
2015-10-05 12:43:47.529 IPsec Client 3 (my_client:500 -> my_server:500): This IPsec Client is deleted.
2015-10-05 12:43:48.441 L2TP PPP Session [my_client:1701]: Acquiring an IP address from the DHCP server failed. To accept a PPP session, you need to have a DHCP server. Make sure that a DHCP server is working normally in the Ethernet segment which the Virtual Hub belongs to. If you do not have a DHCP server, you can use the Virtual DHCP function of the SecureNAT on the Virtual Hub instead.
2015-10-05 12:43:55.004 L2TP PPP Session [my_client:1701]: The VPN Client sent a packet though an IP address of the VPN Client hasn't been determined.
2015-10-05 12:43:55.004 L2TP PPP Session [my_client:1701]: A PPP protocol error occurred, or the PPP session has been disconnected.
2015-10-05 12:43:55.269 [HUB "MY_HUB"] Session "SID-MY_USERNAME-[L2TP]-2": The session has been terminated. The statistical information is as follows: Total outgoing data size: 0 bytes, Total incoming data size: 1320 bytes.
2015-10-05 12:43:55.289 Connection "CID-44" terminated by the cause "The VPN session has been deleted. It is possible that either the administrator disconnected the session or the connection from the client to the VPN Server has been disconnected." (code 11).
2015-10-05 12:43:55.289 Connection "CID-44" has been terminated.
2015-10-05 12:43:55.289 The connection with the client (IP address my_client, Port number 1701) has been disconnected.
TIA,
UDP 1701 is not open! Instead of this fact L2TP/IPSec was able to connect but no IP address because of missing DHCP server or VirtualDHCP problem:
2015-10-05 12:43:33.980 IPsec Client 2 (my_client:500 -> my_server:500): A new IPsec client is created.
2015-10-05 12:43:33.980 IPsec IKE Session (IKE SA) 2 (Client: 2) (my_client:500 -> my_server:500): A new IKE SA (Main Mode) is created. Initiator Cookie: 0x62BD167CD2AF92A7, Responder Cookie: 0x42873C8C8B9CD5B3, DH Group: MODP 1024 (Group 2), Hash Algorithm: SHA-1, Cipher Algorithm: AES-CBC, Cipher Key Size: 256 bits, Lifetime: 4294967295 Kbytes or 28800 seconds
2015-10-05 12:43:37.521 IPsec Client 3 (my_client:500 -> my_server:500): A new IPsec client is created.
2015-10-05 12:43:37.521 IPsec IKE Session (IKE SA) 3 (Client: 3) (my_client:500 -> my_server:500): A new IKE SA (Main Mode) is created. Initiator Cookie: 0x62BD167CD2AF92A7, Responder Cookie: 0x8B89F962CD9443B5, DH Group: MODP 1024 (Group 2), Hash Algorithm: SHA-1, Cipher Algorithm: AES-CBC, Cipher Key Size: 256 bits, Lifetime: 4294967295 Kbytes or 28800 seconds
2015-10-05 12:43:37.771 IPsec Client 2 (my_client:4500 -> my_server:4500): The port number information of this client is updated.
2015-10-05 12:43:37.771 IPsec Client 2 (my_client:4500 -> my_server:4500):
2015-10-05 12:43:37.771 IPsec IKE Session (IKE SA) 2 (Client: 2) (my_client:4500 -> my_server:4500): This IKE SA is established between the server and the client.
2015-10-05 12:43:38.984 IPsec IKE Session (IKE SA) 2 (Client: 2) (my_client:4500 -> my_server:4500): The client initiates a QuickMode negotiation.
2015-10-05 12:43:38.984 IPsec ESP Session (IPsec SA) 2 (Client: 2) (my_client:4500 -> my_server:4500): A new IPsec SA (Direction: Client -> Server) is created. SPI: 0x4CECBAF0, DH Group: (null), Hash Algorithm: SHA-1, Cipher Algorithm: AES-CBC, Cipher Key Size: 256 bits, Lifetime: 4294967295 Kbytes or 28800 seconds
2015-10-05 12:43:38.984 IPsec ESP Session (IPsec SA) 2 (Client: 2) (my_client:4500 -> my_server:4500): A new IPsec SA (Direction: Server -> Client) is created. SPI: 0xA7F6099, DH Group: (null), Hash Algorithm: SHA-1, Cipher Algorithm: AES-CBC, Cipher Key Size: 256 bits, Lifetime: 4294967295 Kbytes or 28800 seconds
2015-10-05 12:43:39.776 IPsec IKE Session (IKE SA) 2 (Client: 2) (my_client:4500 -> my_server:4500): The server initiates a QuickMode negotiation.
2015-10-05 12:43:39.776 IPsec ESP Session (IPsec SA) 3 (Client: 2) (my_client:4500 -> my_server:4500): A new IPsec SA (Direction: Client -> Server) is created. SPI: 0x5F4C2286, DH Group: (null), Hash Algorithm: SHA-1, Cipher Algorithm: AES-CBC, Cipher Key Size: 256 bits, Lifetime: 4294967295 Kbytes or 28800 seconds
2015-10-05 12:43:39.776 IPsec ESP Session (IPsec SA) 3 (Client: 2) (my_client:4500 -> my_server:4500): A new IPsec SA (Direction: Server -> Client) is created. SPI: 0x0, DH Group: (null), Hash Algorithm: SHA-1, Cipher Algorithm: AES-CBC, Cipher Key Size: 256 bits, Lifetime: 4294967295 Kbytes or 28800 seconds
2015-10-05 12:43:41.776 IPsec IKE Session (IKE SA) 2 (Client: 2) (my_client:4500 -> my_server:4500): The server initiates a QuickMode negotiation.
2015-10-05 12:43:41.776 IPsec ESP Session (IPsec SA) 4 (Client: 2) (my_client:4500 -> my_server:4500): A new IPsec SA (Direction: Client -> Server) is created. SPI: 0x9EB3AABD, DH Group: (null), Hash Algorithm: SHA-1, Cipher Algorithm: AES-CBC, Cipher Key Size: 256 bits, Lifetime: 4294967295 Kbytes or 28800 seconds
2015-10-05 12:43:41.776 IPsec ESP Session (IPsec SA) 4 (Client: 2) (my_client:4500 -> my_server:4500): A new IPsec SA (Direction: Server -> Client) is created. SPI: 0x0, DH Group: (null), Hash Algorithm: SHA-1, Cipher Algorithm: AES-CBC, Cipher Key Size: 256 bits, Lifetime: 4294967295 Kbytes or 28800 seconds
2015-10-05 12:43:42.566 IPsec Client 2 (my_client:4500 -> my_server:4500): The L2TP Server Module is started.
2015-10-05 12:43:42.717 IPsec ESP Session (IPsec SA) 3 (Client: 2) (my_client:4500 -> my_server:4500): The SPI which has been pending is now set. New SPI: 0x4722B13
2015-10-05 12:43:42.717 IPsec ESP Session (IPsec SA) 3 (Client: 2) (my_client:4500 -> my_server:4500): This IPsec SA is established between the server and the client.
2015-10-05 12:43:42.729 IPsec ESP Session (IPsec SA) 2 (Client: 2) (my_client:4500 -> my_server:4500): This IPsec SA is established between the server and the client.
2015-10-05 12:43:42.759 IPsec ESP Session (IPsec SA) 4 (Client: 2) (my_client:4500 -> my_server:4500): The SPI which has been pending is now set. New SPI: 0xB236848
2015-10-05 12:43:42.759 IPsec ESP Session (IPsec SA) 4 (Client: 2) (my_client:4500 -> my_server:4500): This IPsec SA is established between the server and the client.
2015-10-05 12:43:43.092 L2TP PPP Session [my_client:1701]: A new PPP session (Upper protocol: L2TP) is started. IP Address of PPP Client: my_client (Hostname: "anonymous"), Port Number of PPP Client: 1701, IP Address of PPP Server: my_server, Port Number of PPP Server: 1701, Client Software Name: "L2TP VPN Client", IPv4 TCP MSS (Max Segment Size): 1314 bytes
2015-10-05 12:43:43.344 On the TCP Listener (Port 0), a Client (IP address my_client, Host name "BC9C057B.mobile.mydomain", Port number 1701) has connected.
2015-10-05 12:43:43.344 For the client (IP address: my_client, host name: "BC9C057B.mobile.mydomain", port number: 1701), connection "CID-44" has been created.
2015-10-05 12:43:43.344 SSL communication for connection "CID-44" has been started. The encryption algorithm name is "(null)".
2015-10-05 12:43:43.344 [HUB "MY_HUB"] The connection "CID-44" (IP address: my_client, Host name: BC9C057B.mobile.mydomain, Port number: 1701, Client name: "L2TP VPN Client", Version: 4.08, Build: 9449) is attempting to connect to the Virtual Hub. The auth type provided is "External server authentication" and the user name is "MY_USERNAME".
2015-10-05 12:43:43.344 [HUB "MY_HUB"] Connection "CID-44": Successfully authenticated as user "MY_USERNAME".
2015-10-05 12:43:43.344 [HUB "MY_HUB"] Connection "CID-44": The new session "SID-MY_USERNAME-[L2TP]-2" has been created. (IP address: my_client, Port number: 1701, Physical underlying protocol: "Legacy VPN - L2TP")
2015-10-05 12:43:43.344 [HUB "MY_HUB"] Session "SID-MY_USERNAME-[L2TP]-2": The parameter has been set. Max number of TCP connections: 1, Use of encryption: No, Use of compression: No, Use of Half duplex communication: No, Timeout: 20 seconds.
2015-10-05 12:43:43.344 [HUB "MY_HUB"] Session "SID-MY_USERNAME-[L2TP]-2": VPN Client details: (Client product name: "L2TP VPN Client", Client version: 408, Client build number: 9449, Server product name: "SoftEther VPN Server (32 bit) (Open Source)", Server version: 408, Server build number: 9449, Client OS name: "L2TP VPN Client", Client OS version: "-", Client product ID: "-", Client host name: "anonymous", Client IP address: "my_client", Client port number: 1701, Server host name: "my_server", Server IP address: "my_server", Server port number: 1701, Proxy host name: "", Proxy IP address: "0.0.0.0", Proxy port number: 0, Virtual Hub name: "MY_HUB", Client unique ID: "AC3CA4B1E312EB33811C86A069C0FB99")
2015-10-05 12:43:43.435 L2TP PPP Session [my_client:1701]: Trying to request an IP address from the DHCP server.
2015-10-05 12:43:47.529 IPsec IKE Session (IKE SA) 3 (Client: 3) (my_client:500 -> my_server:500): This IKE SA is deleted.
2015-10-05 12:43:47.529 IPsec Client 3 (my_client:500 -> my_server:500): This IPsec Client is deleted.
2015-10-05 12:43:48.441 L2TP PPP Session [my_client:1701]: Acquiring an IP address from the DHCP server failed. To accept a PPP session, you need to have a DHCP server. Make sure that a DHCP server is working normally in the Ethernet segment which the Virtual Hub belongs to. If you do not have a DHCP server, you can use the Virtual DHCP function of the SecureNAT on the Virtual Hub instead.
2015-10-05 12:43:55.004 L2TP PPP Session [my_client:1701]: The VPN Client sent a packet though an IP address of the VPN Client hasn't been determined.
2015-10-05 12:43:55.004 L2TP PPP Session [my_client:1701]: A PPP protocol error occurred, or the PPP session has been disconnected.
2015-10-05 12:43:55.269 [HUB "MY_HUB"] Session "SID-MY_USERNAME-[L2TP]-2": The session has been terminated. The statistical information is as follows: Total outgoing data size: 0 bytes, Total incoming data size: 1320 bytes.
2015-10-05 12:43:55.289 Connection "CID-44" terminated by the cause "The VPN session has been deleted. It is possible that either the administrator disconnected the session or the connection from the client to the VPN Server has been disconnected." (code 11).
2015-10-05 12:43:55.289 Connection "CID-44" has been terminated.
2015-10-05 12:43:55.289 The connection with the client (IP address my_client, Port number 1701) has been disconnected.
TIA,
-
aruzsi
- Posts: 18
- Joined: Mon Oct 05, 2015 11:00 am
Re: VirtualDHCP cannot work
My question is: how can I check the VirtualDHCP function is working on my VPN server?
TIA,
TIA,
-
aruzsi
- Posts: 18
- Joined: Mon Oct 05, 2015 11:00 am
Re: VirtualDHCP cannot work
What and when will create the tap or tun device?
I don't have either. :-(
TIA,
I don't have either. :-(
TIA,
-
bbk1674
- Posts: 23
- Joined: Wed Apr 08, 2015 4:33 am
Re: VirtualDHCP cannot work
Go to the Soft ether website and click on download, Then Choose windows as your OS, then yoou can download the server management tool
-
aruzsi
- Posts: 18
- Joined: Mon Oct 05, 2015 11:00 am
Re: VirtualDHCP cannot work
The manager software was downloaded and it was running under Linux with wine.
It was able to connect to my VPN server and I don't know why the VirtualDHCP function not working and who create the tap or tun device.
TIA,
It was able to connect to my VPN server and I don't know why the VirtualDHCP function not working and who create the tap or tun device.
TIA,
-
aruzsi
- Posts: 18
- Joined: Mon Oct 05, 2015 11:00 am
Re: VirtualDHCP cannot work
OK, it is working now! ;-)
The VirtualNAT was enabled and I think that's all.
No real tap or tun interface.
My mobile was able to connect with L2TP. I'll check the log on the server, soon.
I haven't checked ping or anything else, yet.
TIA,
The VirtualNAT was enabled and I think that's all.
No real tap or tun interface.
My mobile was able to connect with L2TP. I'll check the log on the server, soon.
I haven't checked ping or anything else, yet.
TIA,