[apaq]

Hi,
does anybody tried to setup 2 simultaneous tunnels on Linux using tun0 & tun1 interfaces? I know I should add two additional routing tables assigned to each network interface to handle the traffic, but don't know what routes should be there to bypass enp0s3 connection.

[Jiaz]

@apaq: I recommend much easier setup and use vm/docker and connect to vpn in there and open/serve a socks/http proxy. That way you don't have to mess with routing and just setup multiple socks/http proxies in JDownloader. There are ready 2 use docker images for that

Without that you have to define what dest IP should take which route/device. With said way you can use both/multiple connections simultaneously

[FBD]

When you have two network interfaces for your two openvpn connections, you need to add routes for the websites you want to connect to for each tun interface. So if you want to have youtube to be handled by tun1 you would have to add routes for all youtube ip addresses to go through tun1. That's very tedious and only really reasonable if you have only one or two hosters you want to route for.

An easier approach would be to start up a proxy server (like tinyproxy for example) for each interface and have that proxy server only use one interface. For example, configure proxyserver1 to use tun1 and be listening on port 8888, and proxyserver2 to use tun2 and listen on port 8889.

Then you can setup jdownloader to use those proxy servers very easily in the connection manager and setup load balancing or white/blacklist for hosters for each proxyserver/tun-device and conveniently manage the connections.

A few years ago I wrote a script that setup tinyproxy instances for multiple openvpn connections,
see github.com/FarBeyondDriven/multi-openvpn-tinyproxy
you may not be able to use it directly, but it can surely give you some hints to set things up properly.

[Jiaz]

@FBD: Very nice With that "multiple routing tables" approach, same should be possible without additional proxies and setup JDownloader to use those interfaces directly?

[apaq]

thanks @FBD for guidance I will try to understand your approach, however it's more advanced than I though. If there is easier way like @Jiaz suggested I would go for it first.

@Jiaz can you send some step-by-step solution or example how to do that?

[Jiaz]

@apag: search for "docker vpn proxy" or "socks docker vpn" and similiar. for example
github.com/ducmthai/vpn-as-a-container
or
github.com/kizzx2/docker-openvpn-client-socks
and many more

[apaq]

meanwhile I checked @FBD's script but when running openvpn I got the error

Options error: --up script fails with '/home/john/Downloads/vpnroutes': Permission denied (errno=13)

[Jiaz]

@apaq: I do recommend to stick to ready2use docker images when not familiar with openvpn/network/routing stuff

[FBD]

Originally Posted by apaq

meanwhile I checked @FBD's script but when running openvpn I got the error

Options error: --up script fails with '/home/john/Downloads/vpnroutes': Permission denied (errno=13)

That error means that openvpn (which invokes that script when the connection is "--up") does not have permissions to execute it. You have to make it executable (u+x).

If that all is a bit over your head, maybe a docker approach would be easier.

[apaq]

thanks @FBD, I was determined and followed your precious tips. Finally both connections were succesfully established, your script works very well!

[FBD]

Originally Posted by apaq

thanks @FBD, I was determined and followed your precious tips. Finally both connections were succesfully established, your script works very well!

Nice to hear, thanks for the feedback.

[apaq]

@FBD Is there a way to maintain active connection after closing terminal? Normally by doing this connection is lost.

[Jiaz]

@apaq: eg run those commands in screen, so you can open new screen, run command, and then detach from it

[pspzockerscene]

How to Use "screen" on Linux

To keep a process running after closing your terminal, you can use the screen command. Here is a short guide:

Step 1: Start a new screen session

screen -S mysession

This creates a screen session named "mysession".

Step 2: Run your command inside the screen
For example:

python3 myscript.py

Step 3: Detach from the screen session
Press:

Ctrl + A, then D

This will detach the session and bring you back to the regular terminal.

Step 4: Reattach to the screen session (optional)
If you want to go back into the session:

screen -r mysession

Important Tip
Even if you close your terminal window, the screen session will continue running in the background.

List all screen sessions

screen -ls

End a screen session
Inside the screen session, type:

exit

Or, from outside the screen:

screen -X -S mysession quit

This way, your process will keep running even if you disconnect from SSH or close the terminal window.

[apaq]

thanks for guidance @Jiaz and @pspzockerscene for more details. Now everything works in a sleek manner.

[Jiaz]

@apaq: You're welcome but all thanks to FBD

[apaq]

that's right, @FBD made impressive job, all credit to him.