Jump to content
Not connected, Your IP: 44.192.247.185

Search the Community

Showing results for tags 'Comodo Firewall'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • AirVPN
    • News and Announcement
    • How-To
    • Databases
  • Community
    • General & Suggestions
    • Troubleshooting and Problems
    • Blocked websites warning
    • Eddie - AirVPN Client
    • DNS Lists
    • Reviews
    • Other VPN competitors or features
    • Nonprofit
    • Off-Topic
  • Other Projects
    • IP Leak
    • XMPP

Product Groups

  • AirVPN Access
  • Coupons
  • Misc

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Twitter


Mastodon


AIM


MSN


ICQ


Yahoo


XMPP / Jabber


Skype


Location


Interests

Found 5 results

  1. I understand that with the new Eddie version, the Comodo Firewall settings are no longer up to date. I am now getting a whole slew of errors (e.g., not connecting, IPv6 tunnel errors, connection loops, etc.). Instead of trying to fix the problem, I shut the entire firewall down and went back to the basic Windows 8.1 firewall on default settings. At least now airvpn is connecting. There used to be a sticky tutorial here on the AirVPN forums on how to configure Comodo Firewall with AirVPN, but I do not see it anymore (nor can I find it). Is it safe to assume that Comodo Firewall is no longer recommended by the admins? If it is still recommended, what is the recommended setup? Warm regards, Jopa
  2. I'm running AirVPN v.2.10.3 on a Windows 7 laptop with NOD32 antivirus (just downgraded from NOD32 internet security so that I can install the Comodo Firewall). I am messing around with these settings because the old uTorrent (v. 1.8.2; there is a reason for this) stopped downloading for some reason, and I couldn't figure it out in the NOD32 firewall settings. I am writing this post because I am confused about how the AirVPN "Network Lock" feature works with the Windows Firewall (especially since I will be using the Comodo setup here). Is there a conflict of some sort or problem with using Comodo Firewall along with the "Network Lock" feature? Or do they not work together? Also, if there are specific instructions on how to get uTorrent working on AirVPN (still doesn't work), I'm still at a loss. Thanks. JP
  3. Hi! After April 2014 AirVPN Major System Update I downloaded AirVPN Client v. 1.92 and generated new configurations for both Windows and Linux. However, when I am connected to AirVPN servers under Ubuntu 14.04 LTS Trusty Tahr 64-bit, ipleak.net reveals that Tor exit node is set along with AirVPN exit node, despite the fact that Tor application is not even installed. When Windows 8.1 Pro 64-bit is in use, Tor exit node doesn't exist. I checked the connection a few times with either Comodo Firewall turned on and off. My Comodo Firewall is configured to prevent leaks according to AirVPN articles. In short, what does it mean? Does my connection (under Windows) lack some recently added additional layer of protection? If yes, how to turn it on. Have I to change Comodo Firewall configuration? If yes, tell me how, please. Thank you for your responses.
  4. Hi! After AirVPN Major System Update of April 2014 user can use three alternative connections simultaneously on three different devices with only one bought account. I would like to use my laptop (with Windows 8.1 Pro 64-bit and Comodo Firewall configured to prevent ip leaks) as a hotspot. When Comodo Firewall is turned off, everything works perfectly. I can connect my netbook to internet via my laptop and, of course, use AirVPN clients on both machines. However, when Comodo Firewall is turned on, it blocks device, which is connected to hotspot providing computer, from obtaining the internet data transmission. My Comodo Firewall on host is set to prevent leakage according to to the description given here (https://airvpn.org/t...-prevent-leaks/). To let device (connected to host) be connected to internet, I have to disable the main firewall rule (Block And Log IP In/Out From MAC Any To MAC Any Where Protocol Is Any) by changing the command "Block and Log" into "Allow and Log". After the moment when device was just connected and AirVPN client started the encryption of all the communication with the network, the rule can be restored. Is there a possibility to modify configuration of Comodo Firewall to let devices be connected to network through hotspot providing computer without any manual operations within the firewall of the latter? If yes, tell me how, please. I would like to be still protected against ip leakage of course. Thank you for your responses.
  5. I recently updated my Comodo firewall to version 6. It's bloated and terrible, while version 5 was great. Is there a security risk involved with staying on version 5 instead of moving to 6? Thanks.
×
×
  • Create New...