Guide---Multi Session/Tunnel---TCP/UDP---Windows OS & Comodo scenario Native OpenVPN 2.5 Wintun adapters---

[Flx 77]

Easy-Way:
Comodo configuration files(links below)
Windows 7 config file
https://airvpn.org/forums/topic/17440-guide-fix-for-tap-adapter-in-windows/page/3/?tab=comments#comment-106650
Windows 10 config file
https://airvpn.org/forums/topic/17440-guide-fix-for-tap-adapter-in-windows/page/3/?tab=comments#comment-109051
How-to:(link below)
https://airvpn.org/forums/topic/17440-guide-fix-for-tap-adapter-in-windows/page/3/?tab=comments#comment-109909

Other details:
1.Install a few extra Wintun adapters:
--------Open a cmd.exe window Run-as-Admin---install.wintun.bat---
cd \
cd Program Files
cd OpenVPN
cd bin
tapctl.exe create --hwid wintun
--------Open a cmd.exe window Run-as-Admin---install.wintun.bat---
Or 
Copy and Paste "tapctl.exe create --hwid wintun" in your cmd.exe window Run As Admin
Repeat the above until you install the 4 or 5 wintun adapters required.

2.Comodo Firewall Ruleset for OpenVPN Multisession scenario:

Apply it to both openvpn.exe and openvpn-gui.exe files in Comodo under "Application Rules".

3.After you have created and imported the necessary yourairvpn.ovpn files (key1_port443 key2_port80 key3_port53 key4_port41185 etc.) in OpenVPN-GUI.

4. Command-line: Script for command-line client to server connection(2.5_git version)

Open 3 cmd.exe windows by Right-click the multi.bat file and "Run as Admin".
AFTER you have imported yourairvpn.ovpn profiles.

5. OpenVPN-GUI(2.5 version)
Right click on your Taskbar icon OpenVPN-GUI and you will see there the profiles imported. 
On each profile click Connect and wait for it to establish a connect to server; then Click "Show Status".
Re-do the above; for each NEW session/tunnel you wish to create on a different key.

6.Most "suggested/preferred" double or triple session!

7. Don't forget:
Modify/Change your config profiles to work for wintun mode!
------buffersize------
rcvbuf 562144
sndbuf 562144
------buffersize------
-----------------
windows-driver wintun
----------------
Next:
Block all your interfaces other than VPN/TAP and apply this to browsers/torrent clients under "Application Rules".
ONLY allows for data transfer/traffic over VPN established tunnels/sessions.
and:
Segment your airvpn.ip-range properly.
8. Errors that you may encounter:
Windows Smart screen may block the multi.bat and/or install.wintun.bat file.
Comodo will/may block the install.wintun.bat and/or multi.bat as well. Switch it from "Unrecognized" to "Trusted" in Comodo-->>File List
NOTE: 
This is NOT an "out-of-the-box" concept. All this is provided AS IS.(files/examples etc.)
Regards,
Flx
 

multi.zip

[Flx 77]

Server-side port(s) assigned that you define in/for each of your yourairvpn.ovpn:
 ----------------------
remote-random
remote xxx.xxx.xxx.xxx 80
remote xxx.xxx.xxx.xxx 443
remote xxx.xxx.xxx.xxx 2018
remote xxx.xxx.xxx.xxx 41185
remote xxx.xxx.xxx.xxx 80
remote xxx.xxx.xxx.xxx 443
remote xxx.xxx.xxx.xxx 2018
remote xxx.xxx.xxx.xxx 41185
 ----------------------
For more on TCP/UDP ports check out the Specs page.(Protocols and entry-IP addresses of each VPN server).

[Flx 77]

 

On 8/13/2020 at 5:59 PM, Flx said:

8. Errors that you may encounter:

Another sort of error encountered and connection fails due to "ring-buffers":
OpenVPN looks for the first installed Wintun adapter. 
1. Disable the first installed Wintun Adapter. Now connect to server on a different/next Profile Imported (e.g. AIrVPN profile2) . Let it connect.
2. Re-enable the first installed Wintun Adapter. Now try connect to server on (e.g. AirVPN profile1), which will use the first installed Wintun Adapter you have just re-enabled. 
Now it will work.
Happy browsing and Stay Safe.

[Flx 77]

Extra info for those that still don't understand:
https://airvpn.org/forums/topic/47071-tom-spark-reviews-arivpn/ 

[Flx 77]

As of now 2 DCO tunnels running "side-by-side" (Elgafar and Kornephoros).
OpenVPN 2.7.5 client version was suppossed to fix the DNS not enforced over the tunnel(s).
To get this under control add a quad9 server to the main adapter and nslookup will use that as the DNS. 
This will only help fix the "connectivity". Can't wait for 2.7.6 release and see if there is an actual fix applied.
Comparing this with 3 Wintun vs. 2 DCO established session(s), the results did not surprise me:
https://www.speedtest.net/result/19502727405
with "rcvbuf 262144 and sndbuf 262144" at default value. With 3 DCO sessions a "small overall system instability" is noted.
Everything else works as expected for me. Modify or change the comodo config until you get the desired *perfection*.

[go558a83nk 384]

41 minutes ago, Flx said:

As of now 2 DCO tunnels running "side-by-side" (Elgafar and Kornephoros).
OpenVPN 2.7.5 client version was suppossed to fix the DNS not enforced over the tunnel(s).
To get this under control add a quad9 server to the main adapter and nslookup will use that as the DNS. 
This will only help fix the "connectivity". Can't wait for 2.7.6 release and see if there is an actual fix applied.
Comparing this with 3 Wintun vs. 2 DCO established session(s), the results did not surprise me:
https://www.speedtest.net/result/19502727405
with "rcvbuf 262144 and sndbuf 262144" at default value. With 3 DCO sessions a "small overall system instability" is noted.
Everything else works as expected for me. Modify or change the comodo config until you get the desired *perfection*.

deleted, I misunderstood what OS was being used here.