PacketiX™ VPN is next-generation VPN software that offers stability, flexibility and expandability, from home and small and medium-size business networks to advanced high-bandwidth and heavy load networks required by large corporations, Internet providers and SaaS businesses.
Contrary to older VPN solutions, PacketiX™ VPN 2.0 can be integrated into an existing network much more easily, as it creates a virtual image of an Ethernet, with LAN cards, routers, hubs and switches. The PacketiX VPN protocol easily passes obstacles on the LAN and the Internet, like firewalls and proxies, as its packets can be handled like a usual SSL connection
The vpn architecture looks like following:
The simplest diagram to use at my home is a virtual hub for remote users to log into home RDP server. The set up configuration steps:
2 Create a new virtual Hub:
Visit VPN Online Test Environment page to create a new virtual Hub.
3. Download VPN Client from VPN Client Installation page and enter your new Virtual Hub to get configuration page
Manual VPN Client Installation
You can also manually install and configure the PacketiX VPN Client.
Download the latest PacketiX VPN Client Installation file
|OS Version||Installation File|
|Windows 32 bit||vpnclient-5351-en-win32-x86.exe|
|Windows 64 bit||vpnclient-5351-en-win32-x64.exe|
|Linux 32 bit||vpnclient-5350a-rtm-en-linux-x86.tar.gz|
|Linux 64 bit||vpnclient-5350a-rtm-en-linux-x64.tar.gz|
4. Install vpn client and do basic configuration.
Installation of vpn client is simple by just following the direction from the installation screen.
Launch the PacketiX VPN Client Manager. Then you will need to create a new Virtual Network Adapter. After that, you could create new vpn connection…
For my case, I created a new VPN Client Adapter – freevpn, and a new vpn connection which name is freevpn too.
After your computer connected to the virtual hub, the new VPN Client Adapter will get a ip address from DHCP service in your virtual hub.
In my case, my machine got a ip 192.168.30.10, and another machine get 192.168.30.11. Both of them can
ping each other and RDP works fine too.
Since this communication is encrypted through ssh / tcp 443 port, which is allowed by most of company firewalls, it will easily by pass your edge firewall rules.