Leaderboard

I am experiencing intermitting DNS problems, where noting gets resolved anymore. I am using Eddie 2.21.3beta and Wireguard. I have to connect to another server for DNS to work again. Which server doesn'tmatter, as after some time to problem reoccurs and I have to connect to yet another server to get it working again for some time. Rinse and repeat so to say. I have no idea if it is either Eddie, Wireguard or something else related.

There are a few misconceptions here. There is a difference between logging DNS queries temporarily and logging VPN traffic. It's possible to enable logs on DNS for like 5 minutes and then turn it off. Let's say I'm trying to go to a site that Easylist, or any other list, blocks. Wouldn't it be nice to know that, so that you could then make an exclusion? This is something that every other DNS filtering service allows; ControlD, NextDNS, AdGuard Home, etc. So, what I'm asking for is nothing new or scandalous in any way.

This would create a crapload of backlash. What, it is possible to log DNS queries? So what, AirVPN lied about the no-log? I think I can answer this with a confident "No, never". I don't understand this sentence. Blocked by what? AirDNS doesn't block a single domain name. If enabled, it even unblocks a few of them. Is there a case where you think AirDNS blocked something? Or what's the cause for this sentence?

I'd assume so, since WireguardNT has been enabled by default in Wireguard itself for a few months now. https://mobile.twitter.com/EdgeSecurity/status/1437402720135270403 WireguardNT is part of the Wireguard project and thus bugs should be reported there. https://lists.zx2c4.com/mailman/listinfo/wireguard

Ya, it's available in pfSense 2.5.2. Here's how you do it: 1. Click the wrench on the top right corner and edit the first widget 2. Add a secondary Gateways widget, and then edit that one 3. Once you are done adding and editing click the save icon on the top right corner of the dashboard

I discovered a simple quirk of setting up eMule (P2P) on Windows 10 that causes port forwarding to fail with AirVPN. This tip that may save others a lot of time. During setup eMule creates an inbound rule in Windows firewall that applies to private networks in scope. This makes sense if using eMule without a VPN. However, Windows treats the AirVPN as a public network. Consequently port forwarding with eMule and AirVPN will not work using the default inbound rule created during eMule setup. The solution is to edit the scope of the eMule inbound rule in Windows firewall to apply to both private and public profiles. The latter is the important one. This is simple to do: In Windows Firewall, right click on the inbound rule for eMule, select Properties, Advanced. Under Profiles check both Private and Public. I am not a security expert so feel free to chime in if this setting raises any concerns. This may also apply to earlier versions of Windows.