My IP changed to my real one

[MaRkOpOlO 0]

hey i was using my bit torrent client and i locked my windows account and when i came back after 2 hours my real ip was being shown instead of the servers ip so i made tried to make comodo block all other ips apart from the servers ips i have followed this guide ((https://airvpn.org/index.php?option=com_kunena&func=view&catid=3&id=3405&Itemid=142) ) 9 times for the last day with no results. and so i am wondering if there is a video or something that can help make a better guide to follow for this.

[MaRkOpOlO 0]

ok now it is saying that i am already connected when i clearly am not whilst trying my tenth attempt to doing that guide this is really frustrating can anyone give a clear simple guide on how to fix these problems now?

(edit:I can now login but other then that the same problems with comodo are still there.)

[Staff 9968]

ok now it is saying that i am already connected when i clearly am not whilst trying my tenth attempt to doing that guide this is really frustrating can anyone give a clear simple guide on how to fix these problems now?

(edit:I can now login but other then that the same problems with comodo are still there.)

Hello!

Where do you get stuck with the Comodo guide (which step)?

If you need to block ONLY your torrent client please see here:

https://airvpn.org/index.php?option=com_kunena&func=view&catid=3&id=1713&Itemid=142#1715

Kind regards

[MaRkOpOlO 0]

I am not sure what step i get stuck at its just that it hasnt worked yet i can login and choose a server but then it never gets to the point where it is at the server i tried connecting to the cygnus server. i have an attachment with my current global rules also all it says is Connecting but it never does.

[Staff 9968]

I am not sure what step i get stuck at its just that it hasnt worked yet i can login and choose a server but then it never gets to the point where it is at the server i tried connecting to the cygnus server. i have an attachment with my current global rules also all it says is Connecting but it never does.

Hello!

The Cygnus entry-IP address is 37.220.11.106.

In order to connect to Cygnus please just modify the IP of the "Allow" rule from/to IP 37.220.11.107. Change the IP to 37.220.11.106.

Whenever you have some problem of this kind, it's convenient to check the Comodo logs to see immediately where the block occurs.

Assuming that the network zones have been defined correctly, all the other rules look just fine. You might like to modify the rule pertaining to the Loopback Zone in Allow IP In/Out From In [Loopback Zone] To In [Loopback Zone]

Kind regards

[MaRkOpOlO 0]

Thank you it does appear to be working now.

[MaRkOpOlO 0]

I have found a new problem, it does not let me connect to any webpage other than airvpn i think it might be my netork setup so i will take a print screen of that.

[MaRkOpOlO 0]

I have found a big issue airvpn says i am connected but my web browser says that i am not (this is with the firewall off atm) i have refreshed but both chrome and firefox says that its my real ip being used instead of the servers.

[MaRkOpOlO 0]

this is the print screen

[Staff 9968]

I have found a new problem, it does not let me connect to any webpage other than airvpn i think it might be my netork setup so i will take a print screen of that.

Hello!

The [Loopback Zone] Network Zone is wrongly defined, it must be [127.0.0.1 / 255.0.0.0]

The [AirVPN] Network Zone is wrongly defined, it must be IP range [10.4.0.0 - 10.9.255.255], or [10.0.0.0 / 255.0.0.0]

The [Home Network] Network Zone is wrongly defined, it must be AT LEAST [192.168.0.0 / 255.255.255.0], however please check your DHCP server (your router probably). A safe definition may be [192.168.0.0 / 255.255.0.0] to cover 192.168.*.*.

The [LAN] Network Zone will go to overlap with the [Home Network] Network Zone, so you can just delete the [LAN] Network Zone in order to avoid confusion and conflicts and be consistent with your global rules.

When you have fixed the Network Zones, store the changes, please re-launch the Air client, re-connect to Cygnus, test the connection and if you have further problems please send us the Comodo logs and the Air logs.

We're looking forward to hearing from you.

Kind regards

[MaRkOpOlO 0]

I have attached the comodo logs the air vpn logs and an attachment that shows the VPN is not working i have restarted chrome and Firefox and the airvpn several times to be positive that it still had a problem.

Logsandstuff.zip

[Staff 9968]

I have attached the comodo logs the air vpn logs and an attachment that shows the VPN is not working i have restarted chrome and Firefox and the airvpn several times to be positive that it still had a problem.

Hello!

The Comodo logs show a block to the operating system in the DHCP "negotiation". Please make sure that you have the global Allow rule specified in step 11a:

Allow IP In/Out From MAC Any To IP 255.255.255.255 Where Protocol Is Any

and that your network areas are correctly defined according to the previous message.

As a possible consequence, the TAP-Win32 interface does not come up, this is the reason for which you establish a tunnel but you don't tunnel anything inside it: no access to the TAP-Win32 interface is possible.

If the TAP-Win32 still does not come up after the changes reported here above, please make sure that you launch the Air client with administrator privileges (it is set by default to be launched with those privileges, but you will have to authorize it if you have the default Win7 UAC active).

If that does not solve the problem, you should uninstall OpenVPN. When you re-install it, make sure that you authorize it to install all the drivers it asks you for authorization.

Kind regards

[MaRkOpOlO 0]

Yes that has made the vpn work however comodo still will not block connections when the vpn is down and i still get something blocked in the comodo logs i am putting a screenshot of my current global rules network rules to see if you can figure out where i went wrong.

Comodologsandscreenshots.zip

[Staff 9968]

Yes that has made the vpn work however comodo still will not block connections when the vpn is down and i still get something blocked in the comodo logs i am putting a screenshot of my current global rules network rules to see if you can figure out where i went wrong.

Hello!

The global rules look fine, there are just some duplicates but they are inessential, for example the following three rules are the same according to your Network Zones configuration:

Allow IP In/Out From IP In [10.4.0.0 -10.9.255.255] To MAC Any Where Protocol Is Any

Allow IP In/Out From In [AirVPN] To MAC Any Where Protocol Is Any

Allow IP In/Out From MAC Any To In [AirVPN] Where Protocol Is Any

Anyway, this is not the cause of the problem. The blocks you can see in Comodo logs are ok.

Please make sure that the Comodo firewall security policy is set to "Custom Policy" and that you don't have any other firewall running.

Please close all your applications (close browsers, disconnect from VPN etc.), set Comodo to "Custom Policy", reconnect to the VPN, start normal Internet activity then disconnect from the VPN and check that you don't have anymore connectivity outside your local network.

We're looking forward to hearing from you.

Kind regards

[MaRkOpOlO 0]

I have restarted the web browser and such and made sure comodo is on custom policy but it still will not block connections when not connected to the vpn and im also sure that there are connections that are not going through the vpn even when it is on as comodo shows that chrome is taking up about 11% compared to openvpn, although it might just be to itself though it still is not blocking either firefox nor chrome when not connected.

[Staff 9968]

I have restarted the web browser and such and made sure comodo is on custom policy but it still will not block connections when not connected to the vpn and im also sure that there are connections that are not going through the vpn even when it is on as comodo shows that chrome is taking up about 11% compared to openvpn, although it might just be to itself though it still is not blocking either firefox nor chrome when not connected.

Hello!

The 11% of Chrome (or any other application) is normal. All the applications will communicate with the outside, but passing through the tunnel, except OpenVPN. However, Comodo will correctly display the percentage on the total communications, on any network card. So that 11% refers to communications of Chrome to/from your TAP-Win32 card AND/OR to/from airvpn.org.

Important: when you disconnect from the VPN your applications will be anyway authorized to communicate with airvpn.org (and with the VPN servers specified entry-IP addresses, of course), according to the global rules. This is to allow the Air client to connect. If you don't like this behavior, you can delete the allow rules for 46.105.19.36, and connect via OpenVPN directly or via the OpenVPN GUI, which don't need to contact airvpn.org.

You can perform a quick check even without tools like Wireshark. Open the Comodo "View Active Connections" while you're connected to the VPN, and check that all the applications, except openvpn.exe, are connecting from 10.*.*.*. If some application is connecting from 192.168.*.* (assuming this is your home network zone) to the outside world, then there's something wrong.

Then, disconnect the VPN and check that the only communications comply with the global rules. For example, try to open with Chrome any website except airvpn.org, you should be unable to reach it.

We're looking forward to hearing from you.

Kind regards

[MaRkOpOlO 0]

Yes i realized that about the airvpn.org will always be accessible but the problem is that i can go on youtube or google any website even though i have the firewall on custom policy the way it is setup currently.

[Staff 9968]

Yes i realized that about the airvpn.org will always be accessible but the problem is that i can go on youtube or google any website even though i have the firewall on custom policy the way it is setup currently.

Hello!

Did you set any application rule?

When Comodo evaluates the rules, for incoming connections the global rules take precedence over the application rules.

For outgoing connections, on the contrary, application rules take the precedence on global rules. In the case of web browsers, they don't need an incoming connection, because they establish an outgoing TCP connection and communicate through the established socket. MISLEADING: the global rules will be evaluated anyway after the application rules.

Please check that you don't have application rules, especially that Chrome is not a trusted application or is anyway authorized to establish outgoing connections.

In case of any doubt, please do not hesitate to send us a screenshot of your application rules.

EDIT:

The recommendation is wrong, sorry. Although application rules take precedence over global rules for outgoing packets, this is an evaluation precedence only. No application rule can jump to "accept" before the global rules are also evaluated. So an outgoing connection must pass both the application rules and the global rules to be established. Therefore, this can't be the problem. Chances are that some other firewall or antivirus is interfering with Comodo.

Kind regards

[MaRkOpOlO 0]

I did check my application rules and there are some set however i am not sure exactly what you mean as when i put it for untrusted program it would not work under vpn so hear are my application rules.

oh and also should i use the same application rules for the bit torrent client?

[Staff 9968]

I did check my application rules and there are some set however i am not sure exactly what you mean as when i put it for untrusted program it would not work under vpn so hear are my application rules.

oh and also should i use the same application rules for the bit torrent client?

Hello!

Forget momentarily about application rules, the previous suggestion was misleading, we apologize for the inconvenience.

First of all, please perform a basic test: put your Comodo firewall to "Custom Policy", then reboot your system.

Please let us know whether you have Internet connectivity just after the reboot (do not connect to the VPN).

Kind regards

[MaRkOpOlO 0]

I have put it in custom policy and i did reboot and i did not connect to the vpn but i still had internet connection and the i still was able to go on any website.

[Staff 9968]

I have put it in custom policy and i did reboot and i did not connect to the vpn but i still had internet connection and the i still was able to go on any website.

Hello!

We can't reproduce the behavior.

Please move up your main blocking rule to the top, reboot and perform again the test. If you still have connectivity, please report to Comodo support team for major bug.

Kind regards

[MaRkOpOlO 0]

i went to bed sorry about the wait, i have tried to put the global rule to block all the way up to the top but all that seems to do is block everything including the vpn but it does block everything though.

[Staff 9968]

i went to bed sorry about the wait, i have tried to put the global rule to block all the way up to the top but all that seems to do is block everything including the vpn but it does block everything though.

Hello!

No problems, of course you can test when you wish and when you have time.

Now, there is a time-consuming test which you can perform if you wish to. Put on top only the allow rule:

Allow TCP or UDP Out From MAC Any To IP 255.255.255.255 Where Source Port Is Any And Destination Port Is Any

in order to allow DHCP "negotiation", reboot and check again whether you can browse (without VPN connection, always). If you can, please report.

If not, move down the block rule only one line at a time, and each time check whether the connection is re-established. This will help identify which rule causes the malfunctioning. When you detect the "guilty rule", try various combinations of the already existing allow rules to determine the set of rules which are causing the leaks.

Also, feel free to send us your exact Windows configuration, in order to help us reproduce your system as near as we can.

Once again, please re-check that you have no other firewalls and/or antivirus running, or any other monitoring system which can run with administrator privileges and interfere with Comodo.

Kind regards

[MaRkOpOlO 0]

I have found that it is these following rules which allow chrome and firefox to go to the internet when not connected to the vpn and the vpn does not work if these are not above the block rule

also i have windows 7 ultimate.

Allow IP In/Out from MAC Any To In [AirVPN] Where Protocol Is Any

Allow IP In/Out from In [AirVPN] To MAC Any Where Protocol Is Any