Jump to content
Not connected, Your IP: 3.137.192.3

go558a83nk

Members2
  • Content Count

    2093
  • Joined

    ...
  • Last visited

    ...
  • Days Won

    37

Posts posted by go558a83nk


  1. 1 hour ago, mazurka7 said:

    Thanks. That explains and confirms my findings. Your prior reply to a similar problem has been hugely helpful in my search as well.  :good:
    That said, I am still puzzled by the reasoning behind AirVPN's advice to put 10.4.0.1 for WAN DNS as it seems that while it works partially (using IP instead of domain for AirVPN server), it breaks the router's Network monitoring function. Is there any justification for this?


    *if* you're using IP address in the VPN server field instead of a domain then putting 10.4.0.1 in the WAN DNS setting might be OK.  Because there's no domain to resolve the router doesn't need to reach 10.4.0.1 prior to connection.

  2. No, that's not being hostile.  That's a gentle reprimand for believing *torguards marketing* because it seemed to me you were saying that you didn't get the speed torguard advertised.  Now I see that you do get better speeds with them. 

    By the way,  I run pfsense too and have run wireguard on it since it became publicly available a couple weeks ago.  Somewhere on the forum here you'll also see some posts of mine with a speedtest using wireguard.  At the time I was told it was a new record.  So, that's why I encouraged you to try it.

    With openvpn Air found that the 10gbit/s servers weren't as efficient as several 1gbit/s servers. I've seen a post detailing their findings.  But wireguard may change that paradigm.  Since wireguard is more efficient with CPU usage, and many people will have systems that can saturate 1gbit/s home internet using wireguard, VPN providers may have to trend towards 10gbit/s servers to meet the demand for speed.  But I'm no network engineer so what do I know....  And even if VPN servers do get more speed capability it still depends on what ISP/transit/peerage actually allows.

    edit: your brother getting gig VPN to your homemade server is a great example of what I mean by ISP/transit/peerage allowance.  Since you're both on the same ISP there's no bottleneck.  But transiting outside your ISP likely leads to bottlenecks more or less depending on which networks are traversed. 

    edit2: why aren't you running VPN on the pfsense box itself?  and, with wireguard in eddie can you manipulate mtu and mss?  if so, try 1420 for both or tune them for your network.  sometimes that's a problem with wireguard.


  3. why on earth do you think you'll magically get better speed with any VPN because they flip a switch for you or say the right words in marketing (torguard)?  speed is heavily dependent upon protocol and what the network route allows.  try wireguard in that case.  Here with air there are a couple servers that are 10gbit/s.  have you tested those to prove to yourself that it's not a server load issue that won't be fixed by a dedicated server?

     


  4. 1 hour ago, monstrocity said:
    6 hours ago, Staff said:
    @monstrocity

    Hello!

    Watch out, the fact that WireGuard's transport layer is UDP does not prevent (as it happens with OpenVPN, on the other hand) both TCP and UDP wrapping, of course. TCP and UDP packet forwarding must work both with WireGuard and OpenVPN in the same way Please feel free to open a ticket if they don't.

    Kind regards

     
    I'm not following. UDP ports are blocked by an institution level firewall, and I have never been able to obfuscate it using UDP tunnels with any VPN service provider - I've tried several besides AirVPN in the past.  I get almost no throughput on UDP with OpenVPN or Wireguard. This has always been the case. With Eddie I have to use TCP server entry points or I can't establish a connection to anything. 

    It sounds like your ISP or something on your network is harsh to UDP traffic if TCP VPN tunnels are faster.

  5. 6 hours ago, monstrocity said:
    11 hours ago, autone said:

    Anyone managed to get port forwarding to work with wireguard? I am getting connection refused errors. It works fine on openVPN.

    I opened UDP port 1637 on the router that's behind a W10 machine, and WG worked fine through Eddie.  I'm not sure if that port needs to be open or not on your end - worth a shot if nothing else works.

    don't open a port on your router for eddie.  it's not needed for anything if everything's going through the VPN tunnel.

  6. 20 hours ago, Jacker@ said:

    Hi,

    @go558a83nk

    Can you explain how/what you changed address and CIDR?

    I want to run multiple WG servers in pfsense, but cannot, all server configs have the same Address = 10.153.187.114/10

    Thanks in advance 😁


    You need to create another "device" which will allow you to generate configs with a different tunnel IP address. https://airvpn.org/devices/

    As far as changing the /10 to /32 I do that in the interface settings of the wireguard tunnel. First I setup tunnel and peer for wireguard handshake, then setup interface and gateway for that wireguard tunnel.

  7. re my above post.  I changed the tunnel addresses from /10 to /32 and it works.

    however, I was pulling my hair out trying to figure out why my second tunnel wasn't working even after the tunnel addresses didn't overlap.  server was Chameleon.

    turns out when I tried to use Leo instead it works.  So perhaps something is wrong with Chameleon wireguard?


  8. I want to add a second wireguard tunnel/peer setup on my pfsense box, using a different device as setup in my AirVPN account.  The different device gives me a different, unique interface address for wireguard configs.  However, it still overlaps in network address space with the other address for my other "device" so pfsense doesn't allow me to add it. (The /10 address is a very large address range!)

    Is there any solution to this so that I can have multiple wireguard tunnels running?

×
×
  • Create New...