go558a83nk

I figured out the problem with domain resolving I had yesterday. I block DNS except that which I specify in my pfsense box. I didn't realize it but qomui insists on using whatever is in the DNS options. I thought that was only used if I tick the box. Since it was trying to use those DNS servers, it failed. I switched those to ones not blocked by pfsense and all is well.

https://airvpn.org/topic/14378-how-can-i-get-vpn-servers-entry-ip-addresses/

Hello! We're sorry, only when we have a signed contract... telling anything during the negotiations, even if not in early stages, would be unfair for all parties, including you. Kind regards I wasn't asking business details, just simply the city. It seemed you were saying that they might not end up in Dallas. Is that the case?

Nevermind. It's working now. I had used the proper credentials but I hadn't input them in the GUI. Instead I edited the file that's supposed to contain them. I guess something went wrong there. This time I added the configs with my creds in the GUI and it's working well!

Really odd that you could connect right up. Yes, I use the proper credentials. It connects for a split second, confirmed in log, then disconnects. I upped verb to 5 in the config to see more info. That's how I saw the errors that I did. What openvpn version are you using?

Wow, weird. Any idea where the 10 formerly quintex servers will end up?

Ok, this is strange - was the second connection attempt successful? Could be something in their config files - I will have a look at it as I'm in the process of adding support for ProtonVPN and Windscribe to Qomui. No, it would just try and try to connect. I upped the log verbiage and saw some unroutable packet errors and some errors like the server tried to push over and over but something was wrong. If you're working to add windscribe then I'm sure you'll figure it out.

Nice. I wonder what setting is causing that. It's obviously something other than dynamic in the gateway settings because that's how mine is set. For your VPN interfaces what is your "ipv4 configuration type" set to? mine is "none". None for me too. I mainly followed the tutorial here to 99% we've entered the twilight zone

No you are doing nothing wrong, this is a bug with the new release (should not happen in older releases). When importing config files manually, qomui tries to resolve the host (ca.windscribe.com in your case) - when resolving the host fails it will leave the line unchanged (this is where the bug occurs) and issue a warning in the log as this will lead to conflicts with the firewall and doublehop feature that rely on resolved hosts - for that reason I might change qomui's behavior in the future to not import such config files as this breaks other features. The question is why resolving the host failed in your case - on my system it works fine. One reason could be that your VM did not have a working internet connection when you added the config files. If that's not the case please try to deactivate the qomui's firewall. If it still fails, check manually if your system can resolve the host with the following command (insert $host, ca.windscribe for example) and post the output: dig $host +short Additional note: You might notice that running the command above returns multiple ip addresses. Currently, qomui will only use one of them as it does not support multiple remote hosts (or Openvpn's remote-random feature) at the moment. Thanks for your feedback! I should have mentioned this because I did notice it myself - my system does resolve ca.windscribe.com just fine, before qomui attempts to load the config, and after I close the crashed qomui. After I read your reply above I edited the configs to use IP address not domain. Then they were loaded into qomui just fine. However, when I connected it seemed there were some routing problems or something openvpn didn't like so it would immediately disconnect and try to connect again.

Trying to add another provider I get this in the terminal after I start qomui-gui in the terminal. This is after an install on a mint 18.3 xfce vm with the deb package version 0.60. Am I doing something wrong? QLayout: Attempting to add QLayout "" to QWidget "providerTab", which already has a layout QObject::startTimer: Timers cannot be started from another thread QObject::startTimer: Timers cannot be started from another thread Traceback (most recent call last): File "/usr/lib/python3/dist-packages/qomui/qomui_gui.py", line 1073, in restoreDefaults default_config_dict = load.json('%s/default_config.json' % (ROOTDIR)) NameError: name 'load' is not defined Traceback (most recent call last): File "/usr/lib/python3/dist-packages/qomui/update.py", line 559, in resolve ip = check_output(dig_cmd).decode("utf-8") File "/usr/lib/python3.5/subprocess.py", line 626, in check_output **kwargs).stdout File "/usr/lib/python3.5/subprocess.py", line 708, in run output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '['dig', '+time=2', '+tries=2', 'ca.windscribe.com', '+short']' returned non-zero exit status 9 During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/qomui/update.py", line 458, in run self.import_configs() File "/usr/lib/python3/dist-packages/qomui/update.py", line 488, in import_configs ip = self.resolve(server) File "/usr/lib/python3/dist-packages/qomui/update.py", line 562, in resolve ip = server NameError: name 'server' is not defined

I've been enjoying Mint 18.3 xfce in vmware player. Much more responsive and memory efficient than cinnamon.

There's no guarantee it'll fix it but you might try the latest release. You're using an old client. Then go into the Eddie settings, then protocols, and test UDP ports at entry IP 3 or 4 for tls-crypt. Also, what exactly did you do with packet sizes?

Nice. I wonder what setting is causing that. It's obviously something other than dynamic in the gateway settings because that's how mine is set. For your VPN interfaces what is your "ipv4 configuration type" set to? mine is "none".

Nice! And I like the new page for those servers which lists the ciphers available. Will other server pages be updated with the same info?

I'm sorry, I feel bad for you Staff. No matter how many times you say *entry IP 3 and 4* people still seem to not comprehend. I guess they just don't open their eyes.

Yes, that's how setup. RTT for that by default is always 0.1ms because it's pinging my VPN internal IP, not the gateway.

yes. That is entry IP 1. You may note in Eddie or the config generator that servers have at least 2 entry IP. Servers updated to the latest software have 4 entry IP. But, always only the one exit IP.

For you it didn't make a difference I guess. But, in my experience with both those seedboxes, the ability to choose my route significantly enhanced the speed with which I could download from them. Either you get "around" overloaded networks, or you get routing that works with your location (AirVPN server) better. In the case of being able to do this with AirVPN servers, you'd possibly get routing that works better with your ISP than the default routing.

Is it possible with any AirVPN location that an option similar to https://network.feral.io/reroute or http://speedtest.seedboxes.cc/ could be offered to users? (The Seedboxes.cc site doesn't show it right away but if you test your speed you'll be offered the choice of which network to use based on the speed tests.) I'm thinking "no" but I figured I'd ask and at least generate some discussion.

Some of the servers are only 100mbit/s servers, most are 1000mbit/s. Keep that in mind when you're looking.

are you trying to connect to a server that no longer exists?

Hello, why can't you get the VPN gateway address at each connection and automatically use it for your purposes? Kind regards by default pfsense will monitor my end of the VPN, not the gateway. (but, it monitors the gateway my ISP WAN properly) I have to manually change the monitor IP. It's a good question and something people bug pfsense devs about often.

Yes, I could do that but 1) it adds more variability to the path between me the IP I'm monitoring and 2) I pay for AirVPN so I don't mind pinging them continuously but I'd feel like I'd be abusing whatever public DNS I ping.

You can ping the VPN default gateway address as usual. Kind regards The problem is that with each different connection the gateway IP will be different. So, with each new connection a person must manually change the monitor IP. We're just wishing for something that always works.

Yep, since 10.4.0.1 isn't pingable anymore there's nothing that just works anymore. Good question.