I have tried everything imo. I can’t seem to allow connection to a single ip only:
127.0.0.1
I wan’t to block access to everything else.
- I tried to customize blocked application by modifying check [x] destination to 127.0.0.1 single ipv4
Logically it should block all access except the destination 127.0.0.1.
doesn’t work
2. I tried customizing “outgoing only” and restricting 127.0.0.1 exception, no luck.
I tried online tutorial about firewall which is limited to GUI and technical scope of understanding firewall rather then logical.
Could someone give an example how to do this?
Thanks
You’re probably not going have much luck with this, although it will depend on the application you’re creating the rule for? May I ask why you trying to limit connections to loopback (127.0.0.1)
Example would be to set my FTP to connect to only one IP and deny access to any other ip. I just have a need to restrict access to one ip on WinSCP or filezilla.
Also was going to test same settings with localhost.
Is there a built in issue in Comodo Firewall with loopback?? Because I saw one similar request 2yr old post with zero replies…
I was able to do this with simplest of the firewalls like ZA and somehting from AVG, “upgraded” to comodo in my mind expecting more versatility.
What kind of FTP connection are you using, active or passive? For most applications, if you want to allow your access to single address and block anything else, you’d create an Application rule something along the lines of the following:
Application Name - myapp.exe
Action - Allow
Protocol - TCP
Direction - Out
Source Address - ANY
Destination Address - The IP address you want to connect to goes here
Source Port - What ever is appropriate
Destination Port - What ever is appropriate
Application Name - myapp.exe
Action - Block
Protocol - IP
Direction - Out
Source Address - ANY
Destination Address - ANY
IP Details - ANY
Also was going to test same settings with localhost.
Is there a built in issue in Comodo Firewall with loopback?? Because I saw one similar request 2yr old post with zero replies…
I was able to do this with simplest of the firewalls like ZA and somehting from AVG, “upgraded” to comodo in my mind expecting more versatility.
What problem are you having?
As I see you created two rules that filter each-other out. I thought Comodo would auto create filtering rule because it has exception rule.
Im using passive non secure FTP.
May I ask why did you pick TCP and not IP in allow rule? (Im not very networking savvy) is it better or more thorough?
Your rule seems to be working. I tested on browser also and only working when AVAST Web shield is disabled.
You could get away without using the second block rule but having it prevents further requests to connect to alternate IP addresses.
Im using passive non secure FTP.
You’re ok with setting the port requirements?
May I ask why did you pick TCP and not IP in allow rule? (Im not very networking savvy) is it better or more thorough?
With Comodo, IP is a generic for all protocols, which you’re unlikely to need.
Thanks for the solution. Ports are basic 21, do i ned to configure comodo for ports?
I don’t care about ports as long as ip is the same.
If you aren’t concerned, just allow all ports out. Otherwise, allow TCP/21 and ANY TCP port above 1024 out.