0

I'm new to the VPN stuff and have a problem with my first setup.

I created a private VPN with ZeroTier for playing old LAN games with my friends. The problem is that the VPN has an IP address range somewhere at 10.147.0.0 to 10.147.255.255, and old software does not recognize it as virtual LAN. So no servers are listed and a connect command or console sometimes doesn't exist.

The goal is to create an internal route in Windows to link an IP of the VPN to my local net.

I need something like 192.168.0.100 --> 10.147.20.62, to let the old software see the local address, and Windows routes it to the VPN. Is this possible?

I tried

route add 10.147.20.62 mask 255.255.255.255 192.168.0.100 IF 24

and the other way round

route add 192.168.0.100 mask 255.255.255.255 10.147.20.62 IF 24

but a ping 192.168.0.100 tells me the host is not reachable.

Update

As requested, I describe what I actually want the computers to do.

My desktop PC has got an IP address 192.168.0.2, assigned by my local router to my physical adapter. The desktop PC also got another IP address 10.147.x.10 assigned by the VPN provider to my virtual adapter.

The same goes for my friend in another city (VPN address 10.147.x.20).

We can see our shares due to the fact, that we are in the same VPN (10.147.x.0). But because the IP address range 10.147.x.0-255 is not a classical LAN range, some software does not recognize that there is a connection.

I want the virtual adapters address of my friend (10.147.x.20) be accessible by a local IP address 192.168.0.100 in my own network.

Picture

I don't know how to call it. Forwarding, masking, routing? But is it possible, what I want my PC to do?

Stefan L.
  • 1

1 Answers1

0

What you are actually doing is routing IP 10.147.20.62 to through the gateway 192.168.0.100 (and the other way around) using the interface ID 21. I'm not sure you understand what "routing" is and your solution is most likely the wrong approach (unless I misunderstood you). If I understood correctly you want want to something like "forward IP x.x.x.1 to IP x.x.x.2". To do this you need to exchange the destination of the IP packet, this is not what routing does.

I would suggest you describe the "actual" problem and it's context in detail maybe adding some screenshots etc. not just the (wrong) solution and or what your think the problem is (although the info about your assumed problem might be helpful this most likely is not the actual problem). And if you do write about the solution please add the source for your solution that is often helpful as well.

Or try LPChip solution from the comments.

PS. A possible solution might be NAT or IPtables (whatever the windows equivalent of IPtables is).

PPS. Here are a few pointers for you to get some further knowledge superuser question, another forum, another forum should be enough to enable you to search yourself.

Albin
  • 11,950