On Linux SE server DE version (ip 192.168.1.22)
On Win SE server Stable version (IP 192.168.1.46)
Each SE server has been connected to a remote server using CC (= cascade connection)
Each SE server has a HUB (= VPN) and each has a username (=vpn) and IPsec/PSK has been enabled
Phones are able using L2TP to connect to SE server on Linux (192.168.1.20) or Win (192.168.1.46), but the Linux machine itself L2TP to SE server fails or Win fails too.
On Linux I could use "ip" command to route 192.168.1.22 traffic via a tap devices i.e. tap_tap.
But the Win machine is a laptop which a carry round + I connect my phone to SE server on Win using L2TP.
Thus I need a solution to connect the laptop itself to SE server on itself using L2TP, while my phone can connect to this server using L2TP over WiFi (WiFi of LAN or laptop HotSpot)
here is the "server log" when the Linux machine tries to connect to SE server on itself (192.168.1.22 => 192.168.1.22)
Code: Select all
2023-02-15 13:17:03.662 L2TP PPP Session [192.168.1.22:42941]: A new PPP session (Upper protocol: L2TP) is started. IP Address of PPP Client: 192.168.1.22 (Hostname: "xxxxxx"), Port Number of PPP Client: 42941, IP Address of PPP Server: 192.168.1.22, Port Number of PPP Server: 1701, Client Software Name: "L2TP VPN Client - xelerance.com", IPv4 TCP MSS (Max Segment Size): 1374 bytes
2023-02-15 13:17:04.369 L2TP PPP Session [192.168.1.22:42941]: The PPP session is disconnected because the upper-layer protocol "L2TP" has been disconnected.
2023-02-15 13:17:04.369 L2TP PPP Session [192.168.1.22:42941]: The PPP session is disconnected.
- excluding that machine traffic (like what we have for Policy Base Routing) or
- separate that machine IP from SE server IP (SE server should listen on any other IP)
I appreciate any suggestions or solutions
Regards