Hello,
I have a copy of Windows 10 with a lot of blocked IPs IN the firewall, not just the host file.
I would like to export all of the current block rules for these IPs from the Windows firewall and just import them in to Comodo Firewall and not have to do every single thing a la cart.
note - this is NOT a range so this is not a range option
Can someone explain if this is possible, and how to best accomplish this task in order to replace the WF with the CF?
Thank in advance!
Nope it is not possible to import rules into CFW from windows firewall.
Thanks for the timely reply.
Is it possible to import rules in to the CFW from any type such as .csv, txt etc etc?
The only way to import anything is CIS own settings which is a .cfgx file which really it is in xml format. You can take a look by going int the CIS install directory and changing the file extension of any of the default configurations from .cfgx to .xml and open it in a web browser. Then look for the firewall section to see how the rules are saved.
Thx, on the same page and I had looked at it this way. I see at the bottom of the firewall section where this should be located.
I’m unable to add any addresses in the firewall and have them articulated in the xml file, they appear to be only in the db.
What I would like to do is add a list via copy\paste or powershell etc to block all the known MSFT spying addresses in Windows 10, but using CFW instead of the Windows FW.
Hello,
I would like to again revisit this topic and see of anyone has some insight on how I might export the W10 FW rules in to the W10 Comodo Firewall?
The previously mention idea of modifying the xml didn’t work for me.
Can this function be added to Comodo if there is no current interoperability?
Anyone with clever ideas that work?
Destroy Windows Spying Rules:
[INFO] Add Windows Firewall rule: “104.89.242.39_Block”
[INFO] Add Windows Firewall rule: “104.96.147.3_Block”
[INFO] Add Windows Firewall rule: “111.221.29.177_Block”
[INFO] Add Windows Firewall rule: “111.221.29.253_Block”
[INFO] Add Windows Firewall rule: “111.221.64.0-111.221.127.255_Block”
[INFO] Add Windows Firewall rule: “131.253.34.230_Block”
[INFO] Add Windows Firewall rule: “131.253.40.37_Block”
[INFO] Add Windows Firewall rule: “131.253.61.100_Block”
[INFO] Add Windows Firewall rule: “131.253.61.64_Block”
[INFO] Add Windows Firewall rule: “131.253.61.68_Block”
[INFO] Add Windows Firewall rule: “131.253.61.96_Block”
[INFO] Add Windows Firewall rule: “134.170.115.60_Block”
[INFO] Add Windows Firewall rule: “134.170.165.248_Block”
[INFO] Add Windows Firewall rule: “134.170.165.253_Block”
[INFO] Add Windows Firewall rule: “134.170.185.70_Block”
[INFO] Add Windows Firewall rule: “134.170.30.202_Block”
[INFO] Add Windows Firewall rule: “137.116.81.24_Block”
[INFO] Add Windows Firewall rule: “137.117.235.16_Block”
[INFO] Add Windows Firewall rule: “157.55.129.21_Block”
[INFO] Add Windows Firewall rule: “157.55.130.0-157.55.130.255_Block”
[INFO] Add Windows Firewall rule: “157.55.133.204_Block”
[INFO] Add Windows Firewall rule: “157.55.235.0-157.55.235.255_Block”
[INFO] Add Windows Firewall rule: “157.55.236.0-157.55.236.255_Block”
[INFO] Add Windows Firewall rule: “157.55.240.220_Block”
[INFO] Add Windows Firewall rule: “157.55.52.0-157.55.52.255_Block”
[INFO] Add Windows Firewall rule: “157.55.56.0-157.55.56.255_Block”
[INFO] Add Windows Firewall rule: “157.56.106.189_Block”
[INFO] Add Windows Firewall rule: “157.56.121.89_Block”
[INFO] Add Windows Firewall rule: “157.56.124.87_Block”
[INFO] Add Windows Firewall rule: “157.56.77.148_Block”
[INFO] Add Windows Firewall rule: “157.56.77.149_Block”
[INFO] Add Windows Firewall rule: “157.56.91.77_Block”
[INFO] Add Windows Firewall rule: “157.56.96.54_Block”
[INFO] Add Windows Firewall rule: “168.63.108.233_Block”
[INFO] Add Windows Firewall rule: “172.230.215.85_Block”
[INFO] Add Windows Firewall rule: “191.232.139.2_Block”
[INFO] Add Windows Firewall rule: “191.232.139.254_Block”
[INFO] Add Windows Firewall rule: “191.232.80.58_Block”
[INFO] Add Windows Firewall rule: “191.232.80.62_Block”
[INFO] Add Windows Firewall rule: “191.237.208.126_Block”
[INFO] Add Windows Firewall rule: “195.138.255.0-195.138.255.255_Block”
[INFO] Add Windows Firewall rule: “2.22.61.43_Block”
[INFO] Add Windows Firewall rule: “2.22.61.66_Block”
[INFO] Add Windows Firewall rule: “204.79.197.200_Block”
[INFO] Add Windows Firewall rule: “207.46.101.29_Block”
[INFO] Add Windows Firewall rule: “207.46.114.58_Block”
[INFO] Add Windows Firewall rule: “207.46.223.94_Block”
[INFO] Add Windows Firewall rule: “207.68.166.254_Block”
[INFO] Add Windows Firewall rule: “212.30.134.204_Block”
[INFO] Add Windows Firewall rule: “212.30.134.205_Block”
[INFO] Add Windows Firewall rule: “213.199.179.0-213.199.179.255_Block”
[INFO] Add Windows Firewall rule: “23.102.21.4_Block”
[INFO] Add Windows Firewall rule: “23.204.68.66_Block”
[INFO] Add Windows Firewall rule: “23.205.214.76_Block”
[INFO] Add Windows Firewall rule: “23.218.212.69_Block”
[INFO] Add Windows Firewall rule: “23.223.20.82_Block”
[INFO] Add Windows Firewall rule: “23.36.33.135_Block”
[INFO] Add Windows Firewall rule: “23.48.106.243_Block”
[INFO] Add Windows Firewall rule: “23.57.101.163_Block”
[INFO] Add Windows Firewall rule: “23.57.107.27_Block”
[INFO] Add Windows Firewall rule: “23.99.10.11_Block”
[INFO] Add Windows Firewall rule: “40.77.226.221_Block”
[INFO] Add Windows Firewall rule: “40.77.226.223_Block”
[INFO] Add Windows Firewall rule: “52.167.222.147_Block”
[INFO] Add Windows Firewall rule: “64.4.23.0-64.4.23.255_Block”
[INFO] Add Windows Firewall rule: “64.4.54.22_Block”
[INFO] Add Windows Firewall rule: “64.4.6.100_Block”
[INFO] Add Windows Firewall rule: “65.39.117.230_Block”
[INFO] Add Windows Firewall rule: “65.52.100.11_Block”
[INFO] Add Windows Firewall rule: “65.52.100.7_Block”
[INFO] Add Windows Firewall rule: “65.52.100.9_Block”
[INFO] Add Windows Firewall rule: “65.52.100.91_Block”
[INFO] Add Windows Firewall rule: “65.52.100.92_Block”
[INFO] Add Windows Firewall rule: “65.52.100.93_Block”
[INFO] Add Windows Firewall rule: “65.52.100.94_Block”
[INFO] Add Windows Firewall rule: “65.52.108.103_Block”
[INFO] Add Windows Firewall rule: “65.52.108.254_Block”
[INFO] Add Windows Firewall rule: “65.52.108.29_Block”
[INFO] Add Windows Firewall rule: “65.52.108.33_Block”
[INFO] Add Windows Firewall rule: “65.55.108.23_Block”
[INFO] Add Windows Firewall rule: “65.55.138.114_Block”
[INFO] Add Windows Firewall rule: “65.55.138.126_Block”
[INFO] Add Windows Firewall rule: “65.55.138.186_Block”
[INFO] Add Windows Firewall rule: “65.55.223.0-65.55.223.255_Block”
[INFO] Add Windows Firewall rule: “65.55.252.63_Block”
[INFO] Add Windows Firewall rule: “65.55.252.71_Block”
[INFO] Add Windows Firewall rule: “65.55.252.92_Block”
[INFO] Add Windows Firewall rule: “65.55.252.93_Block”
[INFO] Add Windows Firewall rule: “65.55.29.238_Block”
[INFO] Add Windows Firewall rule: “65.55.39.10_Block”
[INFO] Add Windows Firewall rule: “77.67.29.176_Block”
[INFO] Add Windows Firewall rule: “WSearch_Block”
Maybe possible to do by edit of a new cfg file.
Best advice is to enter a few blocks first before making the new config file - use these new blocks for examples for adding in the rest of the blocks; in the XML formatting. Use notepad for the editing. Follow the xml format correctly for the new entries when adding in the blocks.
Do not add unwanted spaces or re-adjust lines spacing, or the xml will be corrupted and then useless.
After it is finished, then import the edited cfg into Comodo.
If made correctly, it should work.
No offense, but I think you didn’t read the whole thread.
I said I LOOKED for a place to put these and either it doesn’t exist or it isn’t obvious.
If YOU KNOW where to add the lines, show me a real example!
None of the “all you need to do is . . .”
If you know exactly where to put a list of blocked IPs in the xml - show me the money.
I already renamed a copy of the cfgx to xml and have it open again right now in Notepad++ . . . so ?
Suggest create a category, then edit.
v7 format:
Note to self = “Create Category” . . roger that and THANKS.
I would create a new Category in the Firewall Rules pane in the user interface?
Thx for the format idea, I see that the ones you list are ranges, and I just need to add individual ones.
Would I then just use the same single IP in the body for start and end?
Or something more like this:
Then rename the xml back to a similar original .cfgx file name and then IMPORT.
Am I getting warmer?
TBH never tried this, but
IP address listed as start and end address:
AddrStart=“52.54.6.128” AddrEnd="52.54.6.128
Also the UID= seems to be required for each entry, not as a group of entries.
I am guessing the UID number is randomly created when a IP is added manualy, so maybe pick one UID for the first entry and change it sequentially for newer entry.
TBH this is not the easiest format - my old favorite firewall (another vendor) back in the day was simpler to edit with mass entries.
Roger the unique entries - I’ll conjure up a new format here soon.
Given the number of Unique IPs that I need to list, I prob need to mod the last couple of UID characters to accomplish this.
So something like this?
And so on and so on and so on . . . hundreds of times.
I’m surprised there’s no real comodo dev that can speak authoritatively to this after all this time. 
That may be it!
Maybe first create category, set it up, then enter in one IP and one IP range.
Save cfg.
Use entered for examples.
Then edit. Changing UID for each entry.
Hope that works.
Maybe devs do not want people editing the cfg?
“We here at Comodo stand fast that our products will never offer interoperability with any other product, ever. You have our word on it!”
/■■■■■■
The last time I tried to edit and save the cfg it went wonky and I couldn’t figure out what I was doing wrongly. I finally gave up.
I wonder if it’s also possible to just import the part of the config I want in the future or to be able to share those particular entries with others.
LOL
Manual editing is time consuming.
Importing list of IPs would be nice.
Daym skrate!
About creating a new “category” - this is essentially creating a new block rule and selecting the OUT property, adding an IP range, then finding said range in the cfg and adding on to it?
I’m just a tad unsure about where to actually create the new “BLOCK THESE ■■■■■■ IP” rule.
I’m currently on the Comodo W10 Firewall edition.
I think I’m stuck at the same place as the last time, in that no matter WHAT I create, anywhere - it will not show up in the figgen xml, no nein nyet nada.
Therefore there’s not anything to find in the xml in order to edit or to add to.
So in your case, how did you do that?
Start a section in the network zones.
The image shown is for ports, not IPs.
I’m using v5 but the idea is the same for newer verions.
Sorry this is still a dead end to me. I cam make a new " NETWORK ZONES > BLOCKED ZONES and give it a single IP but then I still can’t find it in a new cgf, I’m telling you the cfgs are not being modified since 6-6-2018.
Sorry to trouble you for something more but the instructions still are a bit cryptic.
Steps . . . screenshots . . . magic . . . voodoo . . . ■■■■ man I’ll take whatever you can provide but at this juncture I’m still at a dead end like the last time.
Open Network Zones.
Use Add button.
Create a new Zone using New Network zone.
Call it whatever - perhaps Windows 10 IP.
Under this new zone, there is provision for a new entry; add in the ips using the new window and the corresponding selection for IP and range in the drop down.put in a few enties for this new category.
Do the Okay button to save it.
Now open the Blocked Zone tab.
Use the Add button.
Select Network Zone and now select the newly made Zone.
Do the okay button.
Should be good now.
There are better info on this in the help .