Jump to content
Not connected, Your IP: 3.226.251.81

go558a83nk

Members2
  • Content Count

    1743
  • Joined

    ...
  • Last visited

    ...
  • Days Won

    21

Everything posted by go558a83nk

  1. it could be that some protocols are still blocked even if allow local is on. Staff will have to say for sure. I do know other people have had problems with blocked local assets even with allow local on and I've read of the same problem with other VPNs that also use the windows filtering platform.
  2. Allow local network in the settings. preferences>network lock>allow lan/private
  3. There's no impatience and people are more likely to test if the servers is more useful to them.
  4. It looks like some of the requests for experimental servers were declined (UK, Switzerland) but I'll go ahead and request a Dallas server just to see. Could we have a Dallas experimental server for chacha20? Thanks.
  5. I think they fixed something because the last couple of days they've been slow but now they seem good again.
  6. You may be overreacting a bit. For example, pfsense stable is still on openvpn 2.4.6 and another VPN provider I use is still using 2.4.6 with their app. I don't know why that is but it seems to me that devs aren't in a hurry to move to the 2.4.7 version.
  7. I have an idea. It's your network. AirVPN didn't just stop working. Nothing's changed with AirVPN.
  8. NAT>port forward> create a rule such that interface is your AirVPN openvpn client destination is AirVPN address port and what IP it redirects to is up to you make sure it creates the associated filter rule automatically
  9. no problems for me using the app on phone.
  10. Yes, that's why you run openvpn on pfsense - so that all devices in your local network go through that one tunnel. Or, you can do policy routing and route some devices to clear internet. As far as helping you figure out this setup, I'm not much help. I followed the guide in this forum years ago and have kept that going until now.
  11. I think in android in the settings you select TLS mode as tls-crypt. That's the same as entry IP 3 or 4 I was talking about. You definitely want to try to use UDP either way.
  12. On my Shield TV the difference in speed was a matter of 45mbit/s vs 35mbit/s. Not that significant a speed increase with chacha20. This using the same speedtest server, same VPN server, same port and protocol. Only thing that changed was stream cipher. AES-256-GCM vs chacha20. But, perhaps my speed from that VPN server just never will be that high anyway.
  13. I've got pfsense working to redirect all DNS requests to 10.4.0.1 but still roku and shield tv Netflix does not work on Equuleus. Apple TV netflix does work. Somehow they are sniffing things out and I've confirmed that no DNS requests other than to 10.4.0.1 are sent by looking at my states table.
  14. TCP causes too much latency. Try UDP ports but using Entry IP 3 or 4.
  15. Is the ubuntu tracker updating, giving you seeds and peers?
  16. Do you have any data to report on ChaCha20 performance on CPUs that *do* support AES-NI? That is, AES-256-GCM accelerated by AES-NI vs ChaCha20? The following site suggests that those of us with AES-NI CPU should stick with ciphers that are accelerated by AES-NI. Do you concur? https://calomel.org/aesni_ssl_performance.html
  17. Looks like pfsense openvpn directives. They really have nothing to do with being unable to torrent. If the VPN works properly with other activities then there's surely just something wrong with your torrent client setup. Even if port forwarding isn't setup properly you should still be able to download.
  18. It doesn't matter if the assigned IP are internal. Keep in mind that security must not only be for network attacks but against physical seizure as well. If any records exist on a server that can be tied to users it is a serious anonymity breach.
  19. I've wondered the same thing! Just posting so that I get notified of any real answer.
  20. Well, you could connect to Tor but the same websites that don't like VPN probably don't like Tor either.
  21. Try moving your static key into the static key section, not tls-auth section, especially since you're not using tls-auth but tls-crypt.
×
×
  • Create New...