• We had to restore from a backup today after a failed software update. Backup was from 0000 EDT and restored it at 0800 EDT so we lost about 8hrs. Today is 07/20/2024. More info here.

Openvpn client and server on the same machine.

zenvice

New Member
Joined
May 2, 2020
Messages
5
Reaction score
0
Credits
62
Hello to all !!


I want to set up a Rraspberry with samba server + VPN server + torrent client + VPN client for torrent.


The idea is to be able to access my local network from outside, which works very well.
The idea is to be able to do wake on lan and remote on my fixed pc from outside, which works very well.
The idea is to do this while the torrent client is running with the VPN client, it blocks.


The problem is when I launch the VPN client on my raspberry it seems to pass all traffic through the raspberry VPN client and so when I try to connect/authenticate to my Raspberry from outside on my ip (ISP) it must be stuck because the answer doesn't come back through the public ip of my Raspberry.
I think I should force the traffic coming from the VPN (server) to take the path of my public ip and not the VPN (client)


here is my route configuration when the raspberry VPN client is not running:


pi@raspberrypi:~ $ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG 202 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 303 0 0 wlan0
10.8.0.0 0.0.0 255.255.255.0 U 0 0 0 tun0
192.168.1.0 0.0.0 255.255.255.0 U 202 0 0 eth0
192.168.1.0 0.0.0 255.255.255.0 U 303 0 0 wlan0
note by the way: I don't even see my public IP?


Here is my route configuration when the VPN client is running on my raspberry

route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.8.8.1 128.0.0.0 UG 0 0 0 tun1
0.0.0.0 192.168.1.1 0.0.0.0 UG 202 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 303 0 0 wlan0
10.8.0.0 0.0.0 255.255.255.0 U 0 0 0 tun0
10.8.8.0 0.0.0 255.255.255.0 U 0 0 0 tun1
128.0.0.0 10.8.8.1 128.0.0.0 UG 0 0 0 tun1
185.210.217.133 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
192.168.1.0 0.0.0 255.255.255.0 U 202 0 0 eth0
192.168.1.0 0.0.0 255.255.255.0 U 303 0 0 wlan0
There I note a problem if I'm not mistaken all the traffic to the tunel0 must pass back through the tunel0 and the tunel1, I think the problem comes from there, but I do not know how to do it.


Thank you in advance for your time and help


Sincerely
 


:(

Not yet - and you've definitely waited a while, so brining it back up by bumping it is understandable (it's less so when it's 30 minutes later).

Maybe your bump will help.

I don't have an answer, as I've done nothing like that before. Do you perhaps need to specifically open (and maybe forward) the ports that your torrent client is using? That'd be me taking a wild stab in the dark and up to you to implement. Sadly, I haven't got any real help for you.

Maybe your bump will help? Maybe it was overlooked? I'd ping a specific user to help, but I don't wanna throw them under the bus like that.
 
I'll move this to Single Board Computers where it may attract the required attention.

Wizard
 
I have never tried doing that much at one time on my PI-4B, I mostly use it as a daily driver and for spreadsheets. It may be asking a bit too much of the little guy.;)
 

Members online


Top