Jump to content
Not connected, Your IP: 34.204.194.190
l33t

ANSWERED Missing IPs from Comodo configuration guide?

Recommended Posts

I set up my Comodo configuration exactly as specified on https://airvpn.org/forums/topic/3405-windows-comodo-prevent-leaks/

I have run into some issues here though. The first was the fact that trying to connect to any server using the Eddie client failed and a message was displayed in the Windows notification area that curl had failed to reach 63.33.78.166 on port 80. Adding this IP and port to the Comodo allowed list got around this issue. Is this an authentication server that needs to be allowed in the Comodo configuration?

After resolving that issue, trying to connect to one of the servers that I had added to the [Air servers entry IPs] network zone (Yildun in this case) using the Eddie client did not work. I double checked that I had typed in the Yildun IP address correctly as reported on https://airvpn.org/generator. Looking at the Comodo logs, the only connection that was being blocked was from my machine to 173.44.55.181 port 443. I added that IP address as an allowed address and Eddie was able to connect fine. Is this IP address missing from the Comodo guide? Perhaps this is a new AirVPN frontend server that needs to be allowed?

Share this post


Link to post
15 hours ago, l33t said:

Is this an authentication server that needs to be allowed in the Comodo configuration?


IP-API reports it as Amazon. I've known Amazon IPs around here as DNS fallback IPs.
 
15 hours ago, l33t said:

Looking at the Comodo logs, the only connection that was being blocked was from my machine to 173.44.55.181 port 443


Every server has four entry IPs: A normal one (1), an alternative (2) and normal (3) and alternative (4) tls-crypt ones. They are shown in the config generator when you enable the Advanced mode in the top right corner of the page. If you resolve yildun.airvpn.org, you get (1).
Now, Eddie has its own preference which of these IPs it takes. Check Preferences > Protocols to see if you didn't accidentally select (2), (3) or (4). This can definitely happen if you let Eddie decide the protocol, so make sure to disable that and keep to (1).

Four simple things:
There's a guide to AirVPN. Before you ask questions, take 30 minutes of your time to go through it.

Amazon IPs are not dangerous here. It's the fallback DNS.
Running TOR exits is discouraged. They're subject to restrictions on the internet and harm all AirVPN users.

Furthermore, I propose that your paranoia is to be destroyed. If you overdo privacy, you'll be unique among the mass again.

 

XMPP: gigan3rd@xmpp.airvpn.org or join our lounge@conference.xmpp.airvpn.org

Share this post


Link to post

I ended up switching to use OpenVPN without Eddie and was able to remove the need to allow 63.33.78.166. Perhaps the guide should be updated to let Eddie users know that they need to allow this address.

Thank you for the information about the four entry IPs! That ended up being my issue and was something I did not even know about.

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Security Check
    Play CAPTCHA Audio
    Refresh Image

×
×
  • Create New...