Can there be a virtual external L2TP interface for inbound SSH?
Posted: Sun Jun 18, 2023 1:56 pm
I am trying to solve a seemingly simple problem.
Can I use L2TP connection in parallel to my main ISP connection? So that only inbound SSH uses L2TP but traffic from LAN goes its normal way as before. Let me explain. I have an ISP that has multiple NAT in front of me (CGNAT, I think).
At home I have a debian server that I need to ssh into. My home LTE router (Mikrotik Chateau LTE) is behind this multiple NAT as the external address as determined by services like "whatismyip" is different from the external interface (lte1) address. This is confirmed by traceroute showing several private IPs after router address (which itself is 10.0.0.0range). Therefore a dynamic dns solution + port forwarding will not work.
Apparently I could get a L2TP service from AA (https://www.aa.net.uk/broadband/l2tp-service/) and that should provide me with a static IP. I imagine this as an encrypted tunnel from AA to my router that would probably create a virtual interface in the router. I think I should then be able ssh to that static IP address from AA which would lead to my router through the L2TP tunnel. The router then should port forward the packets to my debian server and so I should be able to ssh in.
But is this L2TP an all or nothing approach? Will then all my home LAN traffic have to go through that L2TP connection? I would rather that my home network continues as is and I use L2TP only to ssh into my home network (or some other connection type later on, if I find use for that). Reason: my connection is unlimited, but L2TP connection would be metered. And from the common sense viewpoint too I would rather that things are simple and understandable.
I have a picture of how I would want the setup to be. Normal traffic (N) keeps passing between LAN - MT router - Internet as before; only inbound SSH connections that I initiate when I am in the "internet" - from outside go through L2TP tunnel.

Should this work? How should I proceed?
Many thanks!
Can I use L2TP connection in parallel to my main ISP connection? So that only inbound SSH uses L2TP but traffic from LAN goes its normal way as before. Let me explain. I have an ISP that has multiple NAT in front of me (CGNAT, I think).
At home I have a debian server that I need to ssh into. My home LTE router (Mikrotik Chateau LTE) is behind this multiple NAT as the external address as determined by services like "whatismyip" is different from the external interface (lte1) address. This is confirmed by traceroute showing several private IPs after router address (which itself is 10.0.0.0range). Therefore a dynamic dns solution + port forwarding will not work.
Apparently I could get a L2TP service from AA (https://www.aa.net.uk/broadband/l2tp-service/) and that should provide me with a static IP. I imagine this as an encrypted tunnel from AA to my router that would probably create a virtual interface in the router. I think I should then be able ssh to that static IP address from AA which would lead to my router through the L2TP tunnel. The router then should port forward the packets to my debian server and so I should be able to ssh in.
But is this L2TP an all or nothing approach? Will then all my home LAN traffic have to go through that L2TP connection? I would rather that my home network continues as is and I use L2TP only to ssh into my home network (or some other connection type later on, if I find use for that). Reason: my connection is unlimited, but L2TP connection would be metered. And from the common sense viewpoint too I would rather that things are simple and understandable.
I have a picture of how I would want the setup to be. Normal traffic (N) keeps passing between LAN - MT router - Internet as before; only inbound SSH connections that I initiate when I am in the "internet" - from outside go through L2TP tunnel.

Should this work? How should I proceed?
Many thanks!