Why use VPNKI when many providers offer certain services like “Public IP”?
Sure, they do offer such services. But see for yourself – here goes pricing for these services as of September 2016 (in Russia of course):
100 roubles monthly rate, 34 roubles one-time fee for service activation and … attention here! – per-megabyte fee! So say goodbye to “Unlimited Internet” tariffs and get ready for additional data traffic charges.
220 roubles monthly rate, service activation is free and … again – traffic charges…
3,6 roubles daily, 236 roubles service activation fee and no mention of traffic charges, but the wording is far from clear (no mention of 0 roubles/megabyte and just a reference to calling plan) so surprises are still possible.
No such service. At least there is definitely no mention of it on their corporate Web site.
Bottom line: using “Public IP”, “White IP” or similar service costs about 300-500 roubles per month in addition to one’s regular cellular bill. Now suppose that one has more than one site to connect? For example, home network and country house network, each requiring incoming connections?
Another important advantage of VPNKI is its ability to join all your devices together, forming your own private network regardless of any addressing used by your Internet providers. This ability plays well with “smart home” and “Internet of things” technologies.
Is it truly freeо?
Yes, VPNKI is a free service. This means that we are committed to helping people for free, out of enthusiasm. For anyone willing to help we have the donate button.
Who can see my packets?
Each VPNKI user has his own traffic exchange point so no user can see other users’ traffic.
What are the service limitation?
Actually there are a few ones:
- All your networks being connected must use DIFFERENT network numbers. For example, 192.168.1.0/24 and 192.168.2.0/24. Only if that is true VPNKI can route traffic among them. If your networks collide, you have to renumber them until there is no overlap.
- Your devices that initiate tunnels will receive IP addresses from 172.16.0.0/16 network. If this network overlaps with your home networks, you have to renumber the latter. Or alternatively wait for the upcoming VPNKI version which is planned to support user choice of 192.168.0.0/16, 172.16.0.0/16 or 10.0.0.0/16 for interconnect.
Why PPTP is the only supported tunneling protocol? Will there be alternatives?
PPTP has been chosen for use thanks to its simplicity and widespread support. But it can cause trouble if one’s provider blocks PPTP (TCP/1723) or GRE. We will be testing other protocols with VPNKI and adding them as options. Now we added L2TP with IPsec encryption. We have plans to add OpenVPN and SoftEther too.
Will users have control over routing tables at the tunnels exchange point?
At the moment, no. We are considering this feature for adding in future VPNKI versions.
Can one browse the Internet through VPNKI?
No. We don’t provide Internet access through VPNKI tunnels.
Could you please elaborate upon the technology behind the service?
Once a user registers, he or she gains the ability to create tunnels.
Each tunnel requires a login and password to set up. The user makes them up and also programs them into his device: home router, cellular, etc. An IP address is furnished for each tunnel, the user can view it in his site personal area, but cannot change it. At the moment VPNKI doesn’t support changing tunnel logins or passwords: to change them one has to delete and recreate the tunnel.
The next step consists of defining networks reachable VIA the device participating in the tunnel. This must be done for all tunnels built from devices that are routers (modems, home routers) and not endpoints (smartphones). For example one might specify network 192.168.10.0/24 to be reachable via tunnel “user123”.
Once all that is done, VPNKI will be ready to receive connections from one’s devices. Upon successful connection and authentication VPNKI will supply routes to destinations in your newly-formed personal network via DHCP options 121 and 249.
If one’s device lacks support for receiving routes via DHCP, he or she has set that device with static routes manually. User settings take effect on VPNKI and get propagated to one’s devices upon a new connection. So always reconnect your tunnels after reconfiguration.