seemed like a simple task but I can't figure out how to get a speedtest docker to work when I route through binhexvpn or similar.

I'd like to be able to test a bunch of different VPN's and figure out which gives me the best speed. I'm currently using PIA and getting very slow speeds when compared to no VPN

 

Unless there's another alternative to testing OpenVPN speeds on Unraid?

 

posted here since I can't open a new thread in Docker Container. 

 

Thanks

Set the speedtest container to networktype = none and add this to the extra parameter

--net=container:binhex-delugevpn

(replace "binhex-delugevpn" with any container you want, i.e. "binhexvpn")

That's what I tried but none of the speedtest dockers or chrome docker will connect when I do that. 

Well, did you "forward" the port(s) in Binhexvpn? Meaning adding the portmappings from the speedtest container to the binhex container?

yes, added port in binhexvpn that matched port of speedtest docker or chrome docker. 

Which particular containers are you using? So i can have a look at it.

Chromium ich777

Speedflux

Speedtest Tracker

Okay, ive spend too much time with that influxdb stuff

Quick work around is to enable and use privoxy in the binhex container and use that to access the container that are tunnled through the binhexvpn

172.17.0.X ip for the binhexcontainer :port for the service, that works. and doesnt require messing around with the docker image.


(If you wanna mess with the docker image, you have to use iptables to allow the connections, but that is not persistent unless you modify the whole docker image for that)
 

iptables -A OUTPUT -s 172.17.0.0/16 -d YOUR.LOCAL.NET.WORK/24 -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT
iptables -A INPUT -s YOUR.LOCAL.NET.WORK/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT

for chrome, for example
 

Edited September 13, 20232 yr by Mainfrezzer

and this will work with Chromium? really don't wanna deal with the pain of influx either lol. 

just want to do a simple speedtest

12 minutes ago, mike_2246 said:

and this will work with Chromium? really don't wanna deal with the pain of influx either lol. 

just want to do a simple speedtest

the http proxy work with any browser. (dont ask me for anything about phones xD)

Unless you wanna connect to the browser within the vpn connection to use the vpn connection. that wouldnt work and you need to run following code in the binhexvpn container

iptables -A OUTPUT -s 172.17.0.0/16 -d YOUR.LOCAL.NET.WORK/24 -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT
iptables -A INPUT -s YOUR.LOCAL.NET.WORK/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT

so that you can connect from your browser, to the browser. But thats a bit unnecessary since you can just tell your browser to use the privoxy http proxy and type in the adress:port of the services you want to reach.

Edited September 13, 20232 yr by Mainfrezzer

pretty sure i'm just doing it wrong, still can't connect to the 172.17**:8222 or 10.0**:8222

thats because if you funnel a container through another container, it ignores the mappings from the template. 8080 is the port that chrome would have on the qbittorrentvpn.

Depending on how you connect it changes following:

Scenario 1: You connect through privoxy

You would just enter 172.17.0.6:8080 or whatever your binhex ip is


Scenario 2: you still try to reach the chrome vnc without privoxy
If 8080 is already used on your server, you would map the container port in binhex from 8080 and "translate" it to port 8222 on the host side. You would need to enter and also change the iptable rules for that and then you could connect via the unraid ip + port

Edit:
I just saw the 8080 is being used by the binhexcontainer. Thats unfortunate^^ i would highly recommend you take the delugevpn in this case because that another can of tuna i dont wanna open now  (although, it seems like you can just move it. So do that, put binhex WEBUI_PORT on something else than 8080 or any of the other ports the "passthrough" container will use. 8181 or something)

Edited September 13, 20232 yr by Mainfrezzer

I'll try that for testing, Thanks!

whole point of this is I'm trying to get away from my monthly fee seedbox but getting horrible speeds on unraid docker w/VPN, I'm not expecting to get actual Up/Down speeds without VPN but I'd think that I should get more than 30/40 download speeds. Just a big hit going from Seedbox with great speed to 30/40 lol 

 

So, ive set it up on my end for visual guidance.

Binhex

 

Chrome:



What you need to enter into the binhex console
 

iptables -A OUTPUT -s 172.17.0.0/16 -d 10.0.0.0/24 -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT && iptables -A INPUT -s 10.0.0.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT

Change the 10.0.0.0/24 to whatever your network is. 192.168.0.0/24 for example.

Now you can access your Binhex Interface on UNRAID-IP:8181 and your chrome docker is UNRAID-IP:8080


From the chrome docker you can just access the rest from the 172.17.0.X:PORT



As mentioned before, if you go the privoxy route, which i highly recommend, it looks like this:

You change in binhex the Key 8: (ENABLE_PRIVOXY) to "yes"

you open your firefox, chrome, edge, whatever. Go to setting and search for "Proxy"

You set the http proxy to your unraidip:8118

now your browser gets routed through the vpn container and can access 172.17.0.X natively and you dont need to use the iptables command on every binhex-container start.

Edited September 13, 20232 yr by Mainfrezzer

got everything cloned like yours. qbit runs in :8181 chrome opens with :8080 but give me this...

got it, had to type in 10.0.*.*:8080/vnc.html. just doing 8080 didn't work