Now looks fine, they are using topology subnet, not net30, I've no idea if it changes the setup.
you can start testing transmission, also with user transmission with a bash shell like I mentioned before with echoip.com
RPi2 with OMV, OpenVPN and Transmission firewall settings.
-
- OMV 2.x
- Brutis
-
-
I am curious about the gateway .237 it should be .60
-
Yes, well that's a problem, go back to the default conf in your vpn provider if it has the same behavior, I think the only change was route-nopull
-
Well, I say I have no idea then. You should look at the logs before the restart, maybe there is something else, but is alway better to look at the server log, which in this case is not possible.
flush the iptables of you want the transmission to start traffickin again you have rUles from the script there
-
ok, i went to ask for a testing account there and i found this service quite different from other ones. I was chatting in IRC with some people there.
So you need to modify the script a little bit, because the connection needs a route to the vpn server through the non-vpn connection. In this case instead of route-nopull use route-noexec (this is to pass env vars to script) and use route-up for the iptables script
In the link is the modified script
http://sprunge.us/EOhFThen you will also need a down script with ip route del $route_network_1 just to clean the main table after vpn is down.
The disconnection was because the server is configured send a restart signal if no activity (normal policy), without the route mentioned before there wasn't any activity, that's why.
Hope this works
-
You have really gone above and beyond what I would say is the "normal" level of help and I thank you very much
I have made the changes but ran into a little question regarding the scripts.
The ipredator.conf runs the following to add in their DNS serversCodescript-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf
I was reading you cannot have multiple up or down lines in this .confThe update-resolv-conf is
Bash
Alles anzeigen#!/bin/bash # # Parses DHCP options from openvpn to update resolv.conf # To use set as 'up' and 'down' script in your openvpn *.conf: # up /etc/openvpn/update-resolv-conf # down /etc/openvpn/update-resolv-conf # # Used snippets of resolvconf script by Thomas Hood <jdthood@yahoo.co.uk> # and Chris Hanson # Licensed under the GNU GPL. See /usr/share/common-licenses/GPL. # # 05/2006 chlauber@bnc.ch # # Example envs set from openvpn: # foreign_option_1='dhcp-option DNS 193.43.27.132' # foreign_option_2='dhcp-option DNS 193.43.27.133' # foreign_option_3='dhcp-option DOMAIN be.bnc.ch' [ -x /sbin/resolvconf ] || exit 0 case $script_type in up) for optionname in ${!foreign_option_*} ; do option="${!optionname}" echo $option part1=$(echo "$option" | cut -d " " -f 1) if [ "$part1" == "dhcp-option" ] ; then part2=$(echo "$option" | cut -d " " -f 2) part3=$(echo "$option" | cut -d " " -f 3) if [ "$part2" == "DNS" ] ; then IF_DNS_NAMESERVERS="$IF_DNS_NAMESERVERS $part3" fi if [ "$part2" == "DOMAIN" ] ; then IF_DNS_SEARCH="$IF_DNS_SEARCH $part3" fi fi done R="" for SS in $IF_DNS_SEARCH ; do R="${R}search $SS " done for NS in $IF_DNS_NAMESERVERS ; do R="${R}nameserver $NS " done echo -n "$R" | /sbin/resolvconf -a "${dev}.inet" /etc/openvpn/firewall.sh ;; down) /sbin/resolvconf -d "${dev}.inet" ip route del $route_network_1 ;; esacIs it ok to add the lines 49 & 53 as I have done? There doesn't appear to be any errors when openvpn starts or stops with # openvpn --config /etc/openvpn/IPredator-CLI-Password.conf
-
You can try múltiple up lines (don't know if it works), if you put multiple scripts in one line there will be treated as arguments or vars.
or as you want you can paste the resolv script inside the iptables script. That should work also, I guess.
-
Looks like is working apparently.
-
It could be something that leaked, you can maybe add a reject input rule for eth0 on peer port.
-
Transmission has port checker, does it show as open?
-
Oh I just found that
it shows it is Closed -
As a sanity check maybe after openvpn starts restart transmission daemon just to reset all connections that might be open through eth0. Just saw a few i think they were coming from before, after a daemon restart all goes through tun
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!