380.66_beta3 - the same problem.When distributing torrents, the huge use of CPU.
I checked this on Transmission and qBittorrent.
There is no such problem with 380.65_4
380.66_beta3 - the same problem.When distributing torrents, the huge use of CPU.
I checked this on Transmission and qBittorrent.
There is no such problem with 380.65_4
Normal when torrenting.I dont know if it is the first time you looking at CPU graph when downloading torrent, but mine(rt-ac1900p,1.4 ghz cpu) can reach 20%-30% with multiples torrents.380.66_beta3 - the same problem.
I was combining routing policy with DNS filtering to avoid DNS leaks on two VPN connections.380.66 Beta 3 is being uploaded.
Code:eb129ac webui: implement help popup for OpenVPN's Internet Redirection options b5e7b94 Bumped revision to beta 3 bec8038 openvpn: re-implemented code to only copy rules related to the intended tunnel, but as a new Internet routing mode called "Policy Rules (strict)". 0b1aa1c openvpn: use the defined max number of openvpn clients as defined in shared.h where appropriate 6e777ac webui: fix incorrect variable names in the rangeFloat method (bug in upstream code) f0bfb69 Updated documentation
Please test the new Policy Rules (strict) if you were already using policy rules. This is the same feature that was implemented in beta1, except I chose for now to make it available as a separate mode, in case it might cause issues with certain configurations. The new strict mode is recommended for people who run multiple tunnels, or who need to ensure that no route gets leaked into their client's routing table.
I recall that discussion as well.In the past, "Strict" wasn't a good option if I could remember it well.
It wasn't 100% safe (all to technical for me).
Is "Strict" a safe option now?
Because "Strict" gives me the advantage to use ab-solution with a VPN-connection.
I did experience problems when using strict policy as well. So, my work around was to use relaxed policy and DNS Filtering; otherwise, if the VPN was dropped for any reason, it wasn't reestablished automatically because openvpn couldn't resolve the IP address of the VPN server.In the past, "Strict" wasn't a good option if I could remember it well.
It wasn't 100% safe (all to technical for me).
Is "Strict" a safe option now?
Because "Strict" gives me the advantage to use ab-solution with a VPN-connection.
But not 100%, so the interface of the router does not open.Normal when torrenting.I dont know if it is the first time you looking at CPU graph when downloading torrent, but mine(rt-ac1900p,1.4 ghz cpu) can reach 20%-30% with multiples torrents.
N66 have 600 mhz cpu
When distributing torrents, the huge use of CPU.
I checked this on Transmission and qBittorrent.
There is no such problem with 380.65_4
In the past, "Strict" wasn't a good option if I could remember it well.
It wasn't 100% safe (all to technical for me).
Is "Strict" a safe option now?
Because "Strict" gives me the advantage to use ab-solution with a VPN-connection.
That is nothing broken only a new way to use openvpn.There is definitely something broken in beta 3 with OpenVPN client. With ALL selected traffic doesn't go through VPN tunnel.
It works only if source IP is listed under Policy rules (strict).
- NEW: Added new Internet redirection mode to OpenVPN clients
called "Policy Rule (Strict)". The difference from the
existing "Policy Rule" mode is that in strict mode,
only rules that specifically target the tunnel's
interface will be used. This ensures that you don't
leak traffic through global or other tunnel routes,
however it also means any static route you might have
defined at the WAN level will not be copied either.
In general, it's recommended to use this new strict
mode.
I was combining routing policy with DNS filtering to avoid DNS leaks on two VPN connections.
Should I stop this practice under Beta 3?
Sent from my ONEPLUS A3000 using Tapatalk
I have tried all the settings in this area and cannot get ab-solution to work through the tunnel. Strict, Exclusive, Relaxed. No ab-solution for me in the tunnel. I'm using policy rules with 5 computers in the tunnel. All of them have no ad blocking.
There is definitely something broken in beta 3 with OpenVPN client. With ALL selected traffic doesn't go through VPN tunnel.
It works only if source IP is listed under Policy rules (strict).
I was on Beta 1 and everything was fine. went to Beta 3 this morning and OpenVPN clent no longer worked. it reported that it connected but traffic didn't seem to be going over it. if I went to whatismyipaddress.com it reported my Comcast address. I rolled back to Beta 1 and it is once again working as it should. this is on my 87u.
I've set Redirect Internet traffic ALL and test with ipleak.net.How are you testing it when setting Internet Redirection to "All"?
I can't test it right now because I'm not home.
Need more information as to how you have it configured, and whether there are any error message in System Log.
May 1 22:38:07 openvpn-routing: Configuring policy rules for client 1
May 1 22:38:07 openvpn-routing: Creating VPN routing table
May 1 22:38:07 openvpn-routing: Removing route for 10.11.10.1 to tun11 from main routing table
May 1 22:38:07 openvpn-routing: Removing route for 0.0.0.0/1 to tun11 from main routing table
May 1 22:38:07 openvpn-routing: Removing route for 128.0.0.0/1 to tun11 from main routing table
May 1 22:38:07 openvpn-routing: Adding route for 192.168.100.51 to 0.0.0.0 through WAN
May 1 22:38:07 openvpn-routing: Adding route for 192.168.100.1 to 0.0.0.0 through WAN
May 1 22:38:07 openvpn-routing: Adding route for 192.168.100.75 to 0.0.0.0 through VPN client 1
May 1 22:38:07 openvpn-routing: Tunnel re-established, restoring WAN access to clients
May 1 22:38:07 openvpn-routing: Completed routing policy configuration for client 1
May 1 22:38:07 openvpn[23785]: Initialization Sequence Completed
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!