Opera Unite - Rule creation

Comodo Internet Security - CIS Firewall Help - CIS
#1

Hi Xan, have you tried Operas’ Unite service with V10 Beta, it seems to work sporadically for me, my Firewall rule for Opera is the CIS default custom, which is O.K. for the browser itself but not sure about the Unite service, should I redefine the rule as Web Browser or define a totally new rule to use Opera Unite? How should I go about if this is the case? see attached screen shot of blocked traffic to Opera, I believe the Unite service requires port 8840 to function and CIS seems to block it, advice appreciated Xan
Xman 8)
Cheers

[attachment deleted by admin]

#2

I made Opera a trusted application 88). That did the trick :wink:

Xan

#3

Did you do it via the Define a New Trusted Application under the Firewall tab or did you simply change the default CIS custom rule to trusted application? BTW thanks Xan
Cheers
Xman 8)

#4

I’ve deleted the opera rules, and when it popped up, I told it, it was a safe application.

Xan

#5

Cool Xan, thanks again :-TU
Cheers :■■■■
Xman 8)

#6

Tried your way Xan, but CIS is still blocking Unite service, is there another way, maybe a rule I could name ‘Unite’ and apply some way to keep it connected safely, what rule could I build and exactly what should it look like in order to work flawlessly???
Regards
Xman 8)

#7

???, strange, it seems you’re the only person having problems… I’ll ask the other mods to take a look at this also, they’re better in the firewall rules than me ;).
Did you do it my way? Simply adding it as allowed ?

Xan

#8

Unite service worked for about 9 hours straight yesterday from around 8:00 PM to 5:00 AM this morning then problem with blocking port 8840 started again, see attached…
Xman :stuck_out_tongue:

[attachment deleted by admin]

#9

I think you will need to create a Global rule that Allows TCP IN on port 8840. This seems to be the port Opera is using.

#10

Interesting Toggie, please elaborate on the creation of this global rule and where & how to put it together if possible so I can try it, PM me instructions if necessary :wink:
Thanks Toggie
Regards
Xman 8)

#11

Please bear in mind that I don’t use Opera, so this is simply based on reading information on the Opera website.

From what I can gather, Opera Unite communicates over TCP using port 8840, I assume this is both inbound and outbound. If this is correct, you will need an Application rule to allow TCP IN/OUT for port 8840.

In addition, if you are using default Global Rules, which enable outbound communications, you will need a rule to allow inbound communication for Opera Unite.

Open The firewall/Advanced/Network Security Policy/Global Rules

Create a new rule:

Allow TCP IN
Source Address - ANY
Destination Address - ANY
Source Port - ANY
Destination Port - 8840

Try that and see what happens.

#12

Thanks Toggie, I’m at work now 1:07 PM (Montreal, Canada) will try this around 6:00 PM and post back
Regards
Xman 8)

#13

Update for Toggie, started Unite service with Xans’ recommendation concerning making Opera a trusted application in both Firewall & Defense+ and it was just blocked momentarily and now seems connected steadily so far, I’ll see how long it stays connected without Firewall blocking and post back. I’ll keep your suggestion as a backup solution though just in case Unite connection is broken again by the Firewall
Thanks to you both, I’ll keep you both posted :wink:
Cheers
Xman 8)

[attachment deleted by admin]

#14

Update to Xan & Toggie, I applied Toggies’ suggestion for the Global Rule under the Firewall & kept Xans’ make Opera a trusted application under Firewall also, Unite hasn’t been blocked by CIS since although Opera Unite server has dropped the connection after several hours of inactivity, my guess is this might be expected behavior to release traffic usage to other Opera Unite members, time will tell…
Thanks again guys :-TU
Cheers :■■■■
Regards
Xman 8)