LAN TO LAN

Post your questions about SoftEther VPN software here. Please answer questions if you can afford.
Locked
daveco1966
Posts: 11
Joined: Wed Oct 11, 2023 12:19 pm

LAN TO LAN

Post by daveco1966 » Mon Oct 23, 2023 1:17 pm

Hi, I need to create a VPN with static ip host (server) and dynamic ip on clients, I need to connect client and host via RDP and send information from rdp to client ( local lan ip ).

This is more or less the project
HOST lan 192.168.10.x 255.255.255.0
CLIENT1 lan 192.168.1.x 255.255.255.0

host server 192.168.10.250 with w10 and software to run from client (via vpn/rdp)

the issue I cannot acheive is to ping 192.168.1.72 that is lan device I need to send information to

solo
Posts: 1193
Joined: Sun Feb 14, 2021 10:31 am

Re: LAN TO LAN

Post by solo » Mon Oct 23, 2023 10:52 pm

Disable firewalls, connect VPN and post as code:

Code: Select all

VPN server:
netstat -r
ipconfig /all
vpncmd localhost:port /server /password:*** /cmd BridgeList
vpncmd localhost:port /server /password:*** /cmd RouterList
vpncmd localhost:port /server /password:*** /adminhub:@@@ /cmd StatusGet
vpncmd localhost:port /server /password:*** /adminhub:@@@ /cmd NatGet
vpncmd localhost:port /server /password:*** /adminhub:@@@ /cmd SecureNatStatusGet
vpncmd localhost:port /server /password:*** /adminhub:@@@ /cmd DhcpGet
vpncmd localhost:port /server /password:*** /adminhub:@@@ /cmd AccessList
//replace: 'port' with number; *** with SE admin password; @@@ with VPN hub's name

If applicable, VM host of the VPN server:
netstat -r
ipconfig /all

VPN client:
netstat -r
ipconfig /all
ping 192.168.10.250

daveco1966
Posts: 11
Joined: Wed Oct 11, 2023 12:19 pm

Re: LAN TO LAN

Post by daveco1966 » Tue Oct 24, 2023 8:09 am

Thanks a lot, but my problem is still alive,
the issue I cannot acheive is to ping 192.168.1.72 that is lan device I need to send information to"

solo
Posts: 1193
Joined: Sun Feb 14, 2021 10:31 am

Re: LAN TO LAN

Post by solo » Tue Oct 24, 2023 9:48 am

Don't thank yet, just post the logs, or else you're on your own.

daveco1966
Posts: 11
Joined: Wed Oct 11, 2023 12:19 pm

Re: LAN TO LAN

Post by daveco1966 » Tue Oct 24, 2023 4:38 pm

Microsoft Windows [Versione 10.0.19045.3570]
(c) Microsoft Corporation. Tutti i diritti sono riservati.

C:\Users\SEDE>netstat -r
===========================================================================
Elenco interfacce
12...e8 4e 06 8b 85 64 ......Realtek PCIe GbE Family Controller
1...........................Software Loopback Interface 1
===========================================================================

IPv4 Tabella route
===========================================================================
Route attive:
Indirizzo rete Mask Gateway Interfaccia Metrica
0.0.0.0 0.0.0.0 192.168.10.254 192.168.10.250 281
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
192.168.10.0 255.255.255.0 On-link 192.168.10.250 281
192.168.10.250 255.255.255.255 On-link 192.168.10.250 281
192.168.10.255 255.255.255.255 On-link 192.168.10.250 281
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 192.168.10.250 281
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 192.168.10.250 281
===========================================================================
Route permanenti:
Indirizzo rete Mask Indir. gateway Metrica
0.0.0.0 0.0.0.0 192.168.10.254 Predefinito
0.0.0.0 0.0.0.0 192.168.1.1 1
===========================================================================

IPv6 Tabella route
===========================================================================
Route attive:
Interf Metrica Rete Destinazione Gateway
1 331 ::1/128 On-link
12 281 fe80::/64 On-link
12 281 fe80::5400:2f09:4d5a:f813/128
On-link
1 331 ff00::/8 On-link
12 281 ff00::/8 On-link
===========================================================================
Route permanenti:
Nessuna

C:\Users\SEDE>ipconfig /all

Configurazione IP di Windows

Nome host . . . . . . . . . . . . . . : SERVER-DANEA
Suffisso DNS primario . . . . . . . . :
Tipo nodo . . . . . . . . . . . . . . : Ibrido
Routing IP abilitato. . . . . . . . . : No
Proxy WINS abilitato . . . . . . . . : No

Scheda Ethernet Ethernet 2:

Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Realtek PCIe GbE Family Controller
Indirizzo fisico. . . . . . . . . . . : E8-4E-06-8B-85-64
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : Sì
Indirizzo IPv6 locale rispetto al collegamento . : fe80::5400:2f09:4d5a:f813%12(Preferenziale)
Indirizzo IPv4. . . . . . . . . . . . : 192.168.10.250(Preferenziale)
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Gateway predefinito . . . . . . . . . : 192.168.10.254
IAID DHCPv6 . . . . . . . . . . . : 501763590
DUID Client DHCPv6. . . . . . . . : 00-01-00-01-2C-66-42-4A-00-9C-02-A7-F7-FD
Server DNS . . . . . . . . . . . . . : 192.168.10.254
8.8.8.8
NetBIOS su TCP/IP . . . . . . . . . . : Attivato

C:\Users\SEDE>vpncmd localhost:5555 /server /password:nontiscordardime /cmd BridgeList
vpncmd command - SoftEther VPN Command Line Management Utility
SoftEther VPN Command Line Management Utility (vpncmd command)
Version 4.42 Build 9798 (English)
Compiled 2023/06/30 11:06:58 by buildsan at crosswin with OpenSSL 3.0.9
Copyright (c) 2012-2023 SoftEther VPN Project. All Rights Reserved.

Connection has been established with VPN Server "localhost" (port 5555).

You have administrator privileges for the entire VPN Server.

VPN Server>BridgeList
BridgeList command - Get List of Local Bridge Connection
Number|Virtual Hub Name|Network Adapter or Tap Device Name|Status
------+----------------+----------------------------------+------
The command completed successfully.


C:\Users\SEDE>vpncmd localhost:5555 /server /password:nontiscordardime /cmd RouterList
vpncmd command - SoftEther VPN Command Line Management Utility
SoftEther VPN Command Line Management Utility (vpncmd command)
Version 4.42 Build 9798 (English)
Compiled 2023/06/30 11:06:58 by buildsan at crosswin with OpenSSL 3.0.9
Copyright (c) 2012-2023 SoftEther VPN Project. All Rights Reserved.

Connection has been established with VPN Server "localhost" (port 5555).

You have administrator privileges for the entire VPN Server.

VPN Server>RouterList
RouterList command - Get List of Virtual Layer 3 Switches
Layer 3 Switch Name|Running Status|Interfaces|Routing Tables
-------------------+--------------+----------+--------------
The command completed successfully.


C:\Users\SEDE>vpncmd localhost:5555 /server /password:nontiscordardime /adminhub:VPN /cmd StatusGet
vpncmd command - SoftEther VPN Command Line Management Utility
SoftEther VPN Command Line Management Utility (vpncmd command)
Version 4.42 Build 9798 (English)
Compiled 2023/06/30 11:06:58 by buildsan at crosswin with OpenSSL 3.0.9
Copyright (c) 2012-2023 SoftEther VPN Project. All Rights Reserved.

Connection has been established with VPN Server "localhost" (port 5555).

You have administrator privileges for the entire VPN Server.

The Virtual Hub "VPN" has been selected.
VPN Server/VPN>StatusGet
StatusGet command - Get Current Status of Virtual Hub
Item |Value
-----------------------------+---------------------
Virtual Hub Name |VPN
Status |Online
Type |Standalone
SecureNAT |Enabled
Sessions |2
Sessions (Client) |1
Sessions (Bridge) |0
Access Lists |0
Users |3
Groups |0
MAC Tables |2
IP Tables |4
Num Logins |44
Last Login |2023-10-24 18:34:58
Last Communication |2023-10-24 18:37:27
Created at |2023-10-12 14:34:50
Outgoing Unicast Packets |224,867,814 packets
Outgoing Unicast Total Size |109,001,743,614 bytes
Outgoing Broadcast Packets |31,097,024 packets
Outgoing Broadcast Total Size|3,212,045,448 bytes
Incoming Unicast Packets |618,930,060 packets
Incoming Unicast Total Size |325,319,671,210 bytes
Incoming Broadcast Packets |11,505,412 packets
Incoming Broadcast Total Size|1,264,441,944 bytes
The command completed successfully.


C:\Users\SEDE>vpncmd localhost:5555 /server /password:nontiscordardime /adminhub:VPN /cmd NatGet
vpncmd command - SoftEther VPN Command Line Management Utility
SoftEther VPN Command Line Management Utility (vpncmd command)
Version 4.42 Build 9798 (English)
Compiled 2023/06/30 11:06:58 by buildsan at crosswin with OpenSSL 3.0.9
Copyright (c) 2012-2023 SoftEther VPN Project. All Rights Reserved.

Connection has been established with VPN Server "localhost" (port 5555).

You have administrator privileges for the entire VPN Server.

The Virtual Hub "VPN" has been selected.
VPN Server/VPN>NatGet
NatGet command - Get Virtual NAT Function Setting of SecureNAT Function
Item |Value
-------------------------------+-----
Use Virtual NAT Function |Yes
MTU Value |1500
TCP Session Timeout (Seconds) |1800
UDP Session Timeout (Seconds) |60
Save NAT and DHCP Operation Log|Yes
The command completed successfully.


C:\Users\SEDE>vpncmd localhost:5555 /server /password:nontiscordardime /adminhub:VPN /cmd SecureNatStatusGet
vpncmd command - SoftEther VPN Command Line Management Utility
SoftEther VPN Command Line Management Utility (vpncmd command)
Version 4.42 Build 9798 (English)
Compiled 2023/06/30 11:06:58 by buildsan at crosswin with OpenSSL 3.0.9
Copyright (c) 2012-2023 SoftEther VPN Project. All Rights Reserved.

Connection has been established with VPN Server "localhost" (port 5555).

You have administrator privileges for the entire VPN Server.

The Virtual Hub "VPN" has been selected.
VPN Server/VPN>SecureNatStatusGet
SecureNatStatusGet command - Get the Operating Status of the Virtual NAT and DHCP Server Function (SecureNat Function)
Item |Value
-------------------------+----------
Virtual Hub Name |VPN
NAT TCP/IP Sessions |16 Session
NAT UDP/IP Sessions |4 Session
NAT ICMP Sessions |0 Session
NAT DNS Sessions |0 Session
Allocated DHCP Clients |1 Client
Kernel-mode NAT is Active|No
Raw IP mode NAT is Active|No
The command completed successfully.


C:\Users\SEDE>vpncmd localhost:5555 /server /password:nontiscordardime /adminhub:VPN /cmd DhcpGet
vpncmd command - SoftEther VPN Command Line Management Utility
SoftEther VPN Command Line Management Utility (vpncmd command)
Version 4.42 Build 9798 (English)
Compiled 2023/06/30 11:06:58 by buildsan at crosswin with OpenSSL 3.0.9
Copyright (c) 2012-2023 SoftEther VPN Project. All Rights Reserved.

Connection has been established with VPN Server "localhost" (port 5555).

You have administrator privileges for the entire VPN Server.

The Virtual Hub "VPN" has been selected.
VPN Server/VPN>DhcpGet
DhcpGet command - Get Virtual DHCP Server Function Setting of SecureNAT Function
Item |Value
-------------------------------+--------------
Use Virtual DHCP Function |Yes
Start Distribution Address Band|192.168.30.10
End Distribution Address Band |192.168.30.200
Subnet Mask |255.255.255.0
Lease Limit (Seconds) |7200
Default Gateway Address |192.168.30.1
DNS Server Address 1 |192.168.30.1
DNS Server Address 2 |None
Domain Name |
Save NAT and DHCP Operation Log|Yes
Static Routing Table to Push |
The command completed successfully.


C:\Users\SEDE>vpncmd localhost:5555 /server /password:nontiscordardime /adminhub:VPN /cmd AccessList
vpncmd command - SoftEther VPN Command Line Management Utility
SoftEther VPN Command Line Management Utility (vpncmd command)
Version 4.42 Build 9798 (English)
Compiled 2023/06/30 11:06:58 by buildsan at crosswin with OpenSSL 3.0.9
Copyright (c) 2012-2023 SoftEther VPN Project. All Rights Reserved.

Connection has been established with VPN Server "localhost" (port 5555).

You have administrator privileges for the entire VPN Server.

The Virtual Hub "VPN" has been selected.
VPN Server/VPN>AccessList
AccessList command - Get Access List Rule List
Item|Value
----+-----
The command completed successfully.

daveco1966
Posts: 11
Joined: Wed Oct 11, 2023 12:19 pm

Re: LAN TO LAN

Post by daveco1966 » Tue Oct 24, 2023 4:39 pm

Microsoft Windows [Versione 10.0.22621.2428]
(c) Microsoft Corporation. Tutti i diritti riservati.

C:\Users\david>netstat -r
===========================================================================
Elenco interfacce
18...5e 0b f9 65 6e 20 ......VPN Client Adapter - VPN
15...48 9e bd 0f a8 c9 ......Intel(R) Ethernet Connection (10) I219-LM
9...2c db 07 b4 4e bc ......Microsoft Wi-Fi Direct Virtual Adapter
7...2e db 07 b4 4e bb ......Microsoft Wi-Fi Direct Virtual Adapter #2
14...00 50 56 c0 00 01 ......VMware Virtual Ethernet Adapter for VMnet1
22...00 50 56 c0 00 08 ......VMware Virtual Ethernet Adapter for VMnet8
11...00 ff a0 55 1c b6 ......TAP-Windows Adapter V9
13...2c db 07 b4 4e bb ......Intel(R) Wi-Fi 6 AX201 160MHz
4...2c db 07 b4 4e bf ......Bluetooth Device (Personal Area Network)
1...........................Software Loopback Interface 1
===========================================================================

IPv4 Tabella route
===========================================================================
Route attive:
Indirizzo rete Mask Gateway Interfaccia Metrica
0.0.0.0 0.0.0.0 192.168.30.1 192.168.30.10 2
8.8.8.8 255.255.255.255 192.168.1.1 192.168.1.37 45
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
130.158.6.69 255.255.255.255 192.168.1.1 192.168.1.37 45
192.168.1.0 255.255.255.0 On-link 192.168.1.37 301
192.168.1.37 255.255.255.255 On-link 192.168.1.37 301
192.168.1.255 255.255.255.255 On-link 192.168.1.37 301
192.168.30.0 255.255.255.0 On-link 192.168.30.10 257
192.168.30.10 255.255.255.255 On-link 192.168.30.10 257
192.168.30.255 255.255.255.255 On-link 192.168.30.10 257
192.168.80.0 255.255.255.0 On-link 192.168.80.1 291
192.168.80.1 255.255.255.255 On-link 192.168.80.1 291
192.168.80.255 255.255.255.255 On-link 192.168.80.1 291
192.168.83.0 255.255.255.0 On-link 192.168.83.1 291
192.168.83.1 255.255.255.255 On-link 192.168.83.1 291
192.168.83.255 255.255.255.255 On-link 192.168.83.1 291
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 192.168.30.10 257
224.0.0.0 240.0.0.0 On-link 192.168.80.1 291
224.0.0.0 240.0.0.0 On-link 192.168.83.1 291
224.0.0.0 240.0.0.0 On-link 192.168.1.37 301
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 192.168.30.10 257
255.255.255.255 255.255.255.255 On-link 192.168.80.1 291
255.255.255.255 255.255.255.255 On-link 192.168.83.1 291
255.255.255.255 255.255.255.255 On-link 192.168.1.37 301
===========================================================================
Route permanenti:
Nessuna

IPv6 Tabella route
===========================================================================
Route attive:
Interf Metrica Rete Destinazione Gateway
1 331 ::1/128 On-link
14 291 fe80::/64 On-link
22 291 fe80::/64 On-link
13 301 fe80::/64 On-link
14 291 fe80::4aa8:b75a:14b6:f3f3/128
On-link
22 291 fe80::b13f:5aa4:fb13:3fbe/128
On-link
13 301 fe80::daae:e34:303b:4a9c/128
On-link
1 331 ff00::/8 On-link
14 291 ff00::/8 On-link
22 291 ff00::/8 On-link
13 301 ff00::/8 On-link
===========================================================================
Route permanenti:
Nessuna

C:\Users\david>ipconfig /all

Configurazione IP di Windows

Nome host . . . . . . . . . . . . . . : MYZBOOK
Suffisso DNS primario . . . . . . . . :
Tipo nodo . . . . . . . . . . . . . . : Ibrido
Routing IP abilitato. . . . . . . . . : No
Proxy WINS abilitato . . . . . . . . : No

Scheda sconosciuta VPN - VPN Client:

Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : VPN Client Adapter - VPN
Indirizzo fisico. . . . . . . . . . . : 5E-0B-F9-65-6E-20
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì
Indirizzo IPv4. . . . . . . . . . . . : 192.168.30.10(Preferenziale)
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Lease ottenuto. . . . . . . . . . . . : martedì 24 ottobre 2023 18:34:54
Scadenza lease . . . . . . . . . . . : martedì 24 ottobre 2023 20:34:54
Gateway predefinito . . . . . . . . . : 192.168.30.1
Server DHCP . . . . . . . . . . . . . : 192.168.30.1
Server DNS . . . . . . . . . . . . . : 192.168.30.1
NetBIOS su TCP/IP . . . . . . . . . . : Attivato

Scheda Ethernet Ethernet:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Intel(R) Ethernet Connection (10) I219-LM
Indirizzo fisico. . . . . . . . . . . : 48-9E-BD-0F-A8-C9
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì

Scheda LAN wireless Connessione alla rete locale (LAN)* 1:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Indirizzo fisico. . . . . . . . . . . : 2C-DB-07-B4-4E-BC
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì

Scheda LAN wireless Connessione alla rete locale (LAN)* 2:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
Indirizzo fisico. . . . . . . . . . . : 2E-DB-07-B4-4E-BB
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : Sì

Scheda Ethernet VMware Network Adapter VMnet1:

Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
Indirizzo fisico. . . . . . . . . . . : 00-50-56-C0-00-01
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : Sì
Indirizzo IPv6 locale rispetto al collegamento . : fe80::4aa8:b75a:14b6:f3f3%14(Preferenziale)
Indirizzo IPv4. . . . . . . . . . . . : 192.168.80.1(Preferenziale)
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Gateway predefinito . . . . . . . . . :
IAID DHCPv6 . . . . . . . . . . . : 117461078
DUID Client DHCPv6. . . . . . . . : 00-01-00-01-2B-81-00-AE-48-9E-BD-0F-A8-C9
NetBIOS su TCP/IP . . . . . . . . . . : Attivato

Scheda Ethernet VMware Network Adapter VMnet8:

Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
Indirizzo fisico. . . . . . . . . . . : 00-50-56-C0-00-08
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : Sì
Indirizzo IPv6 locale rispetto al collegamento . : fe80::b13f:5aa4:fb13:3fbe%22(Preferenziale)
Indirizzo IPv4. . . . . . . . . . . . : 192.168.83.1(Preferenziale)
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Gateway predefinito . . . . . . . . . :
IAID DHCPv6 . . . . . . . . . . . : 251678806
DUID Client DHCPv6. . . . . . . . : 00-01-00-01-2B-81-00-AE-48-9E-BD-0F-A8-C9
NetBIOS su TCP/IP . . . . . . . . . . : Attivato

Scheda Ethernet Ethernet 2:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : TAP-Windows Adapter V9
Indirizzo fisico. . . . . . . . . . . : 00-FF-A0-55-1C-B6
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì

Scheda LAN wireless Wi-Fi:

Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Intel(R) Wi-Fi 6 AX201 160MHz
Indirizzo fisico. . . . . . . . . . . : 2C-DB-07-B4-4E-BB
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì
Indirizzo IPv6 locale rispetto al collegamento . : fe80::daae:e34:303b:4a9c%13(Preferenziale)
Indirizzo IPv4. . . . . . . . . . . . : 192.168.1.37(Preferenziale)
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Lease ottenuto. . . . . . . . . . . . : martedì 24 ottobre 2023 17:52:44
Scadenza lease . . . . . . . . . . . : mercoledì 25 ottobre 2023 17:52:31
Gateway predefinito . . . . . . . . . :
Server DHCP . . . . . . . . . . . . . : 192.168.1.1
IAID DHCPv6 . . . . . . . . . . . : 103602951
DUID Client DHCPv6. . . . . . . . : 00-01-00-01-2B-81-00-AE-48-9E-BD-0F-A8-C9
Server DNS . . . . . . . . . . . . . : 8.8.8.8
NetBIOS su TCP/IP . . . . . . . . . . : Attivato

Scheda Ethernet Connessione di rete Bluetooth:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Indirizzo fisico. . . . . . . . . . . : 2C-DB-07-B4-4E-BF
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì

C:\Users\david>ping 192.168.10.250

Esecuzione di Ping 192.168.10.250 con 32 byte di dati:
Risposta da 192.168.10.250: byte=32 durata=28ms TTL=127
Risposta da 192.168.10.250: byte=32 durata=29ms TTL=127
Risposta da 192.168.10.250: byte=32 durata=30ms TTL=127
Risposta da 192.168.10.250: byte=32 durata=28ms TTL=127

Statistiche Ping per 192.168.10.250:
Pacchetti: Trasmessi = 4, Ricevuti = 4,
Persi = 0 (0% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 28ms, Massimo = 30ms, Medio = 28ms

C:\Users\david>

solo
Posts: 1193
Joined: Sun Feb 14, 2021 10:31 am

Re: LAN TO LAN

Post by solo » Tue Oct 24, 2023 10:24 pm

daveco1966 wrote:
Mon Oct 23, 2023 1:17 pm
I need to connect client and host via RDP and send information from rdp to client ( local lan ip ).
...
host server 192.168.10.250 with w10 and software to run from client (via vpn/rdp)
...
the issue I cannot acheive is to ping 192.168.1.72 that is lan device I need to send information to
The NAT is one-way and will not allow a "reverse" ping to 192.168.1.72, however the client can freely RDP to 192.168.10.250 already. There is no problem.

daveco1966
Posts: 11
Joined: Wed Oct 11, 2023 12:19 pm

Re: LAN TO LAN

Post by daveco1966 » Wed Oct 25, 2023 8:21 am

I know, this is correct, but I need to ping 192.168.1.72 from 192.168.10.250 while using rdp from 192.168.1.x; I'm asking if it's possibile and how to do it.

solo
Posts: 1193
Joined: Sun Feb 14, 2021 10:31 am

Re: LAN TO LAN

Post by solo » Wed Oct 25, 2023 8:35 am

It is possible but first tell us where is 192.168.1.72 - not in your log, and what would be its application?

daveco1966
Posts: 11
Joined: Wed Oct 11, 2023 12:19 pm

Re: LAN TO LAN

Post by daveco1966 » Wed Oct 25, 2023 9:21 am

Microsoft Windows [Versione 10.0.22621.2428]
(c) Microsoft Corporation. Tutti i diritti riservati.

C:\Users\david>netstat -r
===========================================================================
Elenco interfacce
18...5e 0b f9 65 6e 20 ......VPN Client Adapter - VPN
15...48 9e bd 0f a8 c9 ......Intel(R) Ethernet Connection (10) I219-LM
9...2c db 07 b4 4e bc ......Microsoft Wi-Fi Direct Virtual Adapter
7...2e db 07 b4 4e bb ......Microsoft Wi-Fi Direct Virtual Adapter #2
14...00 50 56 c0 00 01 ......VMware Virtual Ethernet Adapter for VMnet1
22...00 50 56 c0 00 08 ......VMware Virtual Ethernet Adapter for VMnet8
11...00 ff a0 55 1c b6 ......TAP-Windows Adapter V9
13...82 c8 d7 f1 24 83 ......Intel(R) Wi-Fi 6 AX201 160MHz
4...2c db 07 b4 4e bf ......Bluetooth Device (Personal Area Network)
1...........................Software Loopback Interface 1
===========================================================================

IPv4 Tabella route
===========================================================================
Route attive:
Indirizzo rete Mask Gateway Interfaccia Metrica
0.0.0.0 0.0.0.0 192.168.30.1 192.168.30.10 2
8.8.8.8 255.255.255.255 192.168.1.254 192.168.1.57 35
93.44.156.24 255.255.255.255 192.168.1.254 192.168.1.57 35
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
130.158.6.114 255.255.255.255 192.168.1.254 192.168.1.57 35
192.168.1.0 255.255.255.0 On-link 192.168.1.57 291
192.168.1.57 255.255.255.255 On-link 192.168.1.57 291
192.168.1.255 255.255.255.255 On-link 192.168.1.57 291
192.168.30.0 255.255.255.0 On-link 192.168.30.10 257
192.168.30.10 255.255.255.255 On-link 192.168.30.10 257
192.168.30.255 255.255.255.255 On-link 192.168.30.10 257
192.168.80.0 255.255.255.0 On-link 192.168.80.1 291
192.168.80.1 255.255.255.255 On-link 192.168.80.1 291
192.168.80.255 255.255.255.255 On-link 192.168.80.1 291
192.168.83.0 255.255.255.0 On-link 192.168.83.1 291
192.168.83.1 255.255.255.255 On-link 192.168.83.1 291
192.168.83.255 255.255.255.255 On-link 192.168.83.1 291
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 192.168.30.10 257
224.0.0.0 240.0.0.0 On-link 192.168.80.1 291
224.0.0.0 240.0.0.0 On-link 192.168.83.1 291
224.0.0.0 240.0.0.0 On-link 192.168.1.57 291
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 192.168.30.10 257
255.255.255.255 255.255.255.255 On-link 192.168.80.1 291
255.255.255.255 255.255.255.255 On-link 192.168.83.1 291
255.255.255.255 255.255.255.255 On-link 192.168.1.57 291
===========================================================================
Route permanenti:
Nessuna

IPv6 Tabella route
===========================================================================
Route attive:
Interf Metrica Rete Destinazione Gateway
1 331 ::1/128 On-link
14 291 fe80::/64 On-link
22 291 fe80::/64 On-link
13 291 fe80::/64 On-link
14 291 fe80::4aa8:b75a:14b6:f3f3/128
On-link
22 291 fe80::b13f:5aa4:fb13:3fbe/128
On-link
13 291 fe80::c439:c02b:3b7e:badd/128
On-link
1 331 ff00::/8 On-link
14 291 ff00::/8 On-link
22 291 ff00::/8 On-link
13 291 ff00::/8 On-link
===========================================================================
Route permanenti:
Nessuna

C:\Users\david>ipconfig /all

Configurazione IP di Windows

Nome host . . . . . . . . . . . . . . : MYZBOOK
Suffisso DNS primario . . . . . . . . :
Tipo nodo . . . . . . . . . . . . . . : Ibrido
Routing IP abilitato. . . . . . . . . : No
Proxy WINS abilitato . . . . . . . . : No

Scheda sconosciuta VPN - VPN Client:

Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : VPN Client Adapter - VPN
Indirizzo fisico. . . . . . . . . . . : 5E-0B-F9-65-6E-20
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì
Indirizzo IPv4. . . . . . . . . . . . : 192.168.30.10(Preferenziale)
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Lease ottenuto. . . . . . . . . . . . : mercoledì 25 ottobre 2023 11:12:11
Scadenza lease . . . . . . . . . . . : mercoledì 25 ottobre 2023 13:12:11
Gateway predefinito . . . . . . . . . : 192.168.30.1
Server DHCP . . . . . . . . . . . . . : 192.168.30.1
Server DNS . . . . . . . . . . . . . : 192.168.30.1
NetBIOS su TCP/IP . . . . . . . . . . : Attivato

Scheda Ethernet Ethernet:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Intel(R) Ethernet Connection (10) I219-LM
Indirizzo fisico. . . . . . . . . . . : 48-9E-BD-0F-A8-C9
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì

Scheda LAN wireless Connessione alla rete locale (LAN)* 1:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Indirizzo fisico. . . . . . . . . . . : 2C-DB-07-B4-4E-BC
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì

Scheda LAN wireless Connessione alla rete locale (LAN)* 2:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
Indirizzo fisico. . . . . . . . . . . : 2E-DB-07-B4-4E-BB
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : Sì

Scheda Ethernet VMware Network Adapter VMnet1:

Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
Indirizzo fisico. . . . . . . . . . . : 00-50-56-C0-00-01
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : Sì
Indirizzo IPv6 locale rispetto al collegamento . : fe80::4aa8:b75a:14b6:f3f3%14(Preferenziale)
Indirizzo IPv4. . . . . . . . . . . . : 192.168.80.1(Preferenziale)
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Gateway predefinito . . . . . . . . . :
IAID DHCPv6 . . . . . . . . . . . : 117461078
DUID Client DHCPv6. . . . . . . . : 00-01-00-01-2B-81-00-AE-48-9E-BD-0F-A8-C9
NetBIOS su TCP/IP . . . . . . . . . . : Attivato

Scheda Ethernet VMware Network Adapter VMnet8:

Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
Indirizzo fisico. . . . . . . . . . . : 00-50-56-C0-00-08
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : Sì
Indirizzo IPv6 locale rispetto al collegamento . : fe80::b13f:5aa4:fb13:3fbe%22(Preferenziale)
Indirizzo IPv4. . . . . . . . . . . . : 192.168.83.1(Preferenziale)
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Gateway predefinito . . . . . . . . . :
IAID DHCPv6 . . . . . . . . . . . : 251678806
DUID Client DHCPv6. . . . . . . . : 00-01-00-01-2B-81-00-AE-48-9E-BD-0F-A8-C9
NetBIOS su TCP/IP . . . . . . . . . . : Attivato

Scheda Ethernet Ethernet 2:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : TAP-Windows Adapter V9
Indirizzo fisico. . . . . . . . . . . : 00-FF-A0-55-1C-B6
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì

Scheda LAN wireless Wi-Fi:

Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Intel(R) Wi-Fi 6 AX201 160MHz
Indirizzo fisico. . . . . . . . . . . : 82-C8-D7-F1-24-83
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì
Indirizzo IPv6 locale rispetto al collegamento . : fe80::c439:c02b:3b7e:badd%13(Preferenziale)
Indirizzo IPv4. . . . . . . . . . . . : 192.168.1.57(Preferenziale)
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Lease ottenuto. . . . . . . . . . . . : mercoledì 25 ottobre 2023 09:30:44
Scadenza lease . . . . . . . . . . . : giovedì 26 ottobre 2023 09:30:32
Gateway predefinito . . . . . . . . . :
Server DHCP . . . . . . . . . . . . . : 192.168.1.254
IAID DHCPv6 . . . . . . . . . . . : 103602951
DUID Client DHCPv6. . . . . . . . : 00-01-00-01-2B-81-00-AE-48-9E-BD-0F-A8-C9
Server DNS . . . . . . . . . . . . . : 8.8.8.8
NetBIOS su TCP/IP . . . . . . . . . . : Attivato

Scheda Ethernet Connessione di rete Bluetooth:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Indirizzo fisico. . . . . . . . . . . : 2C-DB-07-B4-4E-BF
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì

C:\Users\david>ping 192.168.10.250ù
Impossibile trovare l'host 192.168.10.250ù. Verificare che il nome sia corretto e riprovare.

C:\Users\david>ping 192.168.10.250

Esecuzione di Ping 192.168.10.250 con 32 byte di dati:
Risposta da 192.168.10.250: byte=32 durata=29ms TTL=127
Risposta da 192.168.10.250: byte=32 durata=28ms TTL=127
Risposta da 192.168.10.250: byte=32 durata=28ms TTL=127
Risposta da 192.168.10.250: byte=32 durata=29ms TTL=127

Statistiche Ping per 192.168.10.250:
Pacchetti: Trasmessi = 4, Ricevuti = 4,
Persi = 0 (0% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 28ms, Massimo = 29ms, Medio = 28ms

Stato Nome IP Radmin Http Https Ftp Rdp Cartelle condivise Stampanti condivise Gruppo NetBIOS Produttore Indirizzo MAC
On MYZBOOK 192.168.1.33 Wisol 70:2C:1F:69:BE:93
On myAp 192.168.1.35 NWA1123ACv3 (lighttpd) ? Zyxel Communications Corporation D4:1A:D1:47:75:7D
On linux-3 192.168.1.42 Amazon Technologies Inc. 68:DB:F5:4D:7C:D4
On ESP 192.168.1.43 Espressif Inc. 60:01:94:07:35:4F
On ESP 192.168.1.44 Espressif Inc. 60:01:94:07:A7:C9
On ESP 192.168.1.45 Espressif Inc. D8:F1:5B:C5:73:CF
On SEC84251902C1B8 192.168.1.46 Samsung SyncThru Web Service Samsung Electronics 84:25:19:02:C1:B8
On linux-2 192.168.1.47 Amazon Technologies Inc. B4:E4:54:5F:6F:3A
On ESP 192.168.1.48 Espressif Inc. FC:F5:C4:85:7B:85
On TY 192.168.1.49 Tuya Smart Inc. 18:69:D8:10:FA:95
On TY 192.168.1.50 Tuya Smart Inc. 18:69:D8:10:DB:16
On TY 192.168.1.51 Tuya Smart Inc. 18:69:D8:10:FE:B5
On ESP 192.168.1.52 Espressif Inc. D8:F1:5B:C6:26:1C
On K3G-EU-PNA4766A 192.168.1.55 Dyson Limited C8:FF:77:64:CF:3B
On 192.168.1.56 192.168.1.56 Intel Corporate 90:61:AE:10:0D:E7
On MYZBOOK 192.168.1.57 Users 82:C8:D7:F1:24:83
On Smarther 192.168.1.59 Texas Instruments 34:03:DE:19:E0:8C
On Android 192.168.1.68 66:56:2B:E7:FC:C9
On MYZBOOK 192.168.1.72 Login for XML (CustomWebserver) Custom Engineering 00:0E:E2:17:8A:F7
On myfastgate.lan 192.168.1.254 Advanced Digital Broadcast SA 20:83:F8:BD:E5:E6

solo
Posts: 1193
Joined: Sun Feb 14, 2021 10:31 am

Re: LAN TO LAN

Post by solo » Wed Oct 25, 2023 9:44 am

I see. You have two options:

1/ add MLA to the NAT, similar (but not the same) to I cannot access a VPN client computer from other LAN clients

2/ replace NAT with L3 Switch

daveco1966
Posts: 11
Joined: Wed Oct 11, 2023 12:19 pm

Re: LAN TO LAN

Post by daveco1966 » Wed Oct 25, 2023 12:52 pm

I've tried to use L3 but I didn't acheive any good result

solo
Posts: 1193
Joined: Sun Feb 14, 2021 10:31 am

Re: LAN TO LAN

Post by solo » Wed Oct 25, 2023 2:17 pm


daveco1966
Posts: 11
Joined: Wed Oct 11, 2023 12:19 pm

Re: LAN TO LAN

Post by daveco1966 » Thu Oct 26, 2023 1:12 pm

My scenario is
SERVER SIDE
192.168.10.X
SOFTETHER SERVER 192.168.10.250
Gateway 192.168.10.254

CLIENT 1 SIDE
192.168.1.X
SOFTETHER SERVER 192.168.1.250
Gateway 192.168.1.254
device to ping from rdp 192.168.1.100

CLIENT 2 SIDE
192.168.2.X
SOFTETHER SERVER 192.168.2.250
Gateway 192.168.2.254
device to ping from rdp 192.168.2.100
How can I set VPN SERVER L3 switch to solve the problem
You do not have the required permissions to view the files attached to this post.

solo
Posts: 1193
Joined: Sun Feb 14, 2021 10:31 am

Re: LAN TO LAN

Post by solo » Fri Oct 27, 2023 2:23 am

Wait, you are moving the goalposts and now there is an extra "CLIENT 2 SIDE 192.168.2.X". Your original objective was:
HOST lan 192.168.10.x 255.255.255.0
CLIENT1 lan 192.168.1.x 255.255.255.0
host server 192.168.10.250 with w10 and software to run from client (via vpn/rdp)
the issue I cannot acheive is to ping 192.168.1.72 that is lan device I need to send information to
To ping 192.168.1.72, assuming everything is set up as posted in the above logs, do:

on 192.168.10.250, aka "host server"
- install MLA https://learn.microsoft.com/en-us/troub ... ck-adapter
- reboot after installing MLA
- assign a static IP to the MLA: 192.168.30.2
- bridge SoftEther's hub to the MLA
- add a persistent static route: route -p add 192.168.1.0 mask 255.255.255.0 192.168.30.10

on "MYZBOOK 192.168.1.57 Users 82:C8:D7:F1:24:83", aka "CLIENT1"
- start the "Routing and Remote Access" service

on "MYZBOOK 192.168.1.72 Custom Engineering 00:0E:E2:17:8A:F7"
- add a persistent static route: route -p add 192.168.10.0 mask 255.255.255.0 192.168.1.57
- run: netsh advfirewall firewall set rule name="File and Printer Sharing (Echo Request - ICMPv4-In)" new enable=yes

daveco1966
Posts: 11
Joined: Wed Oct 11, 2023 12:19 pm

Re: LAN TO LAN

Post by daveco1966 » Fri Oct 27, 2023 8:11 am

on "MYZBOOK 192.168.1.72 Custom Engineering 00:0E:E2:17:8A:F7"
- add a persistent static route: route -p add 192.168.10.0 mask 255.255.255.0 192.168.1.57
- run: netsh advfirewall firewall set rule name="File and Printer Sharing (Echo Request - ICMPv4-In)" new enable=yes

this is not a Windows hardware, it is a Fiscal Printer

solo
Posts: 1193
Joined: Sun Feb 14, 2021 10:31 am

Re: LAN TO LAN

Post by solo » Fri Oct 27, 2023 8:58 am

Then on "On myfastgate.lan 192.168.1.254 Advanced" router add a static route equivalent of:
ip route add 192.168.10.0/24 via 192.168.1.57

daveco1966
Posts: 11
Joined: Wed Oct 11, 2023 12:19 pm

Re: LAN TO LAN

Post by daveco1966 » Thu Nov 16, 2023 7:41 am

thanks a lot, but at the end it was too much complicated, my be I will use other solutions

solo
Posts: 1193
Joined: Sun Feb 14, 2021 10:31 am

Re: LAN TO LAN

Post by solo » Thu Nov 16, 2023 7:58 am

daveco1966 wrote:
Fri Oct 27, 2023 8:11 am
this is not a Windows hardware, it is a Fiscal Printer
daveco1966 wrote:
Thu Nov 16, 2023 7:41 am
thanks a lot, but at the end it was too much complicated, my be I will use other solutions
Yes, another solution is to simply run RDP with this option: Local devices and resources > Choose the devices and resources that you want to use in your remote session > Printers

driv@163.com
Posts: 2
Joined: Thu Nov 16, 2023 6:20 am

Re: LAN TO LAN

Post by driv@163.com » Fri Nov 17, 2023 6:53 am

I had the same problem,bridge to server, lan to lan, Can ping the PC in the opposite LAN, Unable to access services on the host,such as the web,ftp,samba.I think it's a problem with L3 switch.

driv@163.com
Posts: 2
Joined: Thu Nov 16, 2023 6:20 am

Re: LAN TO LAN

Post by driv@163.com » Fri Nov 17, 2023 7:06 am

3 layer function is faulty, ping is ok, cannot access the web、samba or ftp address of the peer LAN

daveco1966
Posts: 11
Joined: Wed Oct 11, 2023 12:19 pm

Re: LAN TO LAN

Post by daveco1966 » Thu Nov 23, 2023 1:26 pm

solo wrote:
Thu Nov 16, 2023 7:58 am
daveco1966 wrote:
Fri Oct 27, 2023 8:11 am
this is not a Windows hardware, it is a Fiscal Printer
daveco1966 wrote:
Thu Nov 16, 2023 7:41 am
thanks a lot, but at the end it was too much complicated, my be I will use other solutions
Yes, another solution is to simply run RDP with this option: Local devices and resources > Choose the devices and resources that you want to use in your remote session > Printers
this is the first thing I've done, it doesn't work

solo
Posts: 1193
Joined: Sun Feb 14, 2021 10:31 am

Re: LAN TO LAN

Post by solo » Thu Nov 23, 2023 9:33 pm

Indeed RDP redirected printers may not work sometimes. Alternatively try VNC or its clone.

Locked