Laptop Profiles?

Laptop users have particular needs that vary depending upon the connection; eg:
A HOME Lan environment (wired or wireless) where sharing is appropriate VS.
Hotspot connections away from home where ISOLATION is manditory, and perhaps
A Work environment where sharing is required BUT the subnet is totally different,
eg: 10.x.x.x vs 192.168.x.x

  1. Can Comodo address these needs with Network Profiles to select the active rule set?

The Work vs. Home issue can be addressed with multiple Trusted Networks and duplicate
rules varied upon the T.N.

  1. Is there any means to EXPORT / IMPORT the rule sets (network in particular)?

This is a feature that will be added in the firewall in the future. Maybe in v3.0 (just guessing)

There is a script that you can use to save/load the configuration:,2366.0.html

#2 is a help; my intent is to assist others in the cfg of the firewall.

#1 is my major need; moving from my lan to a hotspot requires reconfig and disable of sharing rules.
while I dislike Norton IS, it did handle this very nicely by recognizing the NIC address did not match
the existing rules (not sure it trapped on the Trusted Network or just what).


I move my laptop from work to home on occasion… Perhaps what I have done will work with/for you.

I have created separate Zones (Computer Work, Computer Home, Home DNS, Work DNS, Work LAN, etc). Each of those defines the IP range in question (which is always static, being behind a router in each case…). Where I need to, I take a Zone and turn it into a Trusted Network (which is needed for file sharing, ICS, network printing, etc).

Then I can set up my Network Monitor with sets of Rules for each scenario, to allow traffic as needed. The rules always stay the same; I don’t remove them, and I am able to connect in accordance with those rules. This does take some effort; it’s not a single-click solution, but it works for me. I know the “Profile” approach is in the Wishlist; I have a good degree of confidence for its inclusion to a future version.

Hope this helps,


tried the script – works as designed :slight_smile:

however, it is a total export for CPF; all applications, components, and network monitoring is captured.

for my intent (changing networks), it needs to control only the Network Monitoring.
Apps and Components should be sufficient as-is or relearned on a new system per the existing
users requirements.

I have created separate Zones (Computer Work, Computer Home, Home DNS, Work DNS, Work LAN, etc). Each of those defines the IP range in question (which is always static, being behind a router in each case...). Where I need to, I take a Zone and turn it into a Trusted Network (which is needed for file sharing, ICS, network printing, etc).

this has potential – EXCEPT the use of Static IP addresses. DHCP is used for all hotspots and most
infrastructures (ie IS departments. Only servers get static addresses). Personally, I use MAC filtering
in my router and limit the trusted network to a small portion of the LAN(2-10). At home at least, I can allow a friend to connect and get access but not participate in file/print sharing and thus protect us from one another :slight_smile:

second, a hotspot may implement any non-routed class A,B,C address and I have found that sometimes the hotspot address is a match for my lan. The MAC filtering is missing (not my router)
and I get a random IP, and the sharing is a 9/254 chance of a match if that router is using class C
192.168.0.* (my lan)

You can create some “generic” rules for hotspots…

Only create Out rules, because the Inbound reply is not unsolicited. Without an In rule, no unsolicited contact will be allowed.

Then you can set the type of IP Protocol you are choosing to allow (IP if you want everything allowed Out or want to set up for ICMP etc, TCP and/or UDP if you don’t). This will look like one of the default rules, with Source and Destination of Any. If you chose IP for the protocol, you will have an option to set the specific type (ICMP, IGMP, GRE, etc); whatever you know you will need to obtain the connection from the hotspot (for your DHCP lease).

Obviously for browsing you’ll need another rule for that IP Protocol as well. Obviously as well, you can’t set up a Zone for this as you have for the others, as you can’t define the IP addresses needed. Thus, you want to limit the Connection to Outbound only. For any applications you know will need to connect Out from the hotspot, you will want Network Rules for (as needed) to define Destination Port usage (to match your Application Monitor rules for each application), IP Protocol, even IP address.

More work, I know, but it can be done. You seem to have a good knowledge of what connectivity you need, so that’s a good start. Here’s a link to a compilation of “how-to” posts taken from the forum FAQ page. Each topic has an embedded link back to the original posting, where you can ask questions as you need. There’s some good stuff there to explain network rules, CFP’s layered security, different applications, etc.,6167.0.html


btw: Logging should have a separate control from Altering

also, some FWs support a Monitor status which Logs and continues with the next rule :slight_smile:

here’s my Comodo\Personal Firewall\NetCtrl and Zone controls :slight_smile:

chg the TXT to REG for readability

Moderator’s Note to users: If you change the file extension to .REG and open the file, it will load into your computer’s registry.

[attachment deleted by admin]

It’s easier if you open the Network Monitor to full-screen, and capture a screenshot. Save the 'shot as a jpeg, and attach to your post under Additional Options… :wink:

For these:

, feel free to add to the WishList, which Comodo works very diligently from…,4612.0.html


screenshot attached. this is as generic as I can get it.
Rule #5 is the exposure for hotspot access

0: block fragments
1: allow all local access
2: allow i/o
3: for dns
4: allow email and news
5; lan sharing
6: specific block
7: allow ftp, http(80,443), jsp
8: print sharing
9: ip GRE access
10: specifically block windows junk
11: icmp
12: specific
13: protocol
14: block system services
15: block non-routed 10.x.x.x w/logging
16: block non-routed 172.16.x.x w/logging

[attachment deleted by admin]


For Rule ID 3 and 8, I’d suggest creating separate In and Out rules there, instead of having a combined In/Out rule. Reason is, you’ve specified Ports; whether they are Destination or Source is going to switch aspects depending on direction of traffic (ie, when it’s Outbound, the Source is your computer; on Inbound, the Source is the remote computer…). IMO, it’s better to have separate rules. The other two cases it really wouldn’t matter, since those are very basic/generic rules.

For Rule ID 0, that would be redundant if you recreate the bottom Block & Log IP In, Any, Any. I would recommend adding that rule back regardless. That is your safety net; it is there to block anything that has not already been explicitly allowed. While your rules are fairly tight, it is especially important when using mobile access to keep that bottom “Block All” rule in place. If you kept your rules exactly as they are now and add that Block rule, it would be in position Rule ID 17.

You say Rule ID 5 is for hotspot access? It looks like a LAN rule…


rule 5 is the LAN rule, BUT is an EXPOSURE when on a hotspot :frowning:
This is what a profile should control (imo).

Also thought the implicit default rule for all FWs is DENY ALL.
I’ve added it to the bottom.

Okay, I’m with you; that falls into the category you spoke of, the possibility that the IP could match your home LAN IP 192.x.x.x.

Here’s one way to deal with it:

Create/Add a rule in between Rule ID 4 and Rule ID 5, as: Allow TCP/UDP Out. Any, Any, Any, Destination Port 80,443. This will allow you to browse from the hotspot. When you go to the hotspot, change your LAN rule to Block instead of Allow.

That’s not as easy as Profiles, I agree, but you don’t need to completely reconfigure the firewall, either.


Rules # 4,7 are the generic TCP outbound for email and browsing

the sole issue left is the rule#5 to enable/disable sharing ports (139,445).
I’ve allowed all ports on the lan, but could easily qualify to 139,445

When editing/creating a Network rule, on either Source/Destination Port tab, there’s a box you can check to “Exclude” the following criteria. Then you can check your “Set of Ports” and throw 139,445 in there (which you may already be aware of).

If that doesn’t fit into an existing rule, you can easily add one just for that; just make sure its placement isn’t going to interfere with a necessary function (ie, on your LAN rule).


I had to add the following rule to get file sharing running both ways between to systems
allow tcp/udp in/out source {home-lan} dest {home-brdcst} source-port any dest-ports {137,161}

where {home-lan} is…0.10
and {home-brdcst} is

I intentionally exclude the range… 0.254 as untrusted systems, due to WiFi connection
possibilities. Using MAC filtering, I force known systems into 0.2…0.10 and thus the sharing is

Very good; you’re doing a heck of a job digging in there, jobeard!

It’s not the automatic Profiles, for sure, but it looks like you’re getting things set up the way you want them.

Do you feel like you’re getting it set up the way you want it, though? That’s the real question.


yes :slight_smile: – just need to make it more flexible for hotspots!

Good. I saw you’ve added some suggestions to the Wishlist. Keep it up; Comodo learns from their users’ needs/requests…

If you’re satisified that your question here has been answered (if mostly by yourself…) :wink: would you Modify your original post, and add “[Resolved]” to the subject line, either before or after your original text. That way other users know there’s usable information here.

If you’re not satisfied, let me know and we’ll keep diggin’ at it… :slight_smile: