Shareaza P2P Client

[David]

Hi Shareaza Users,

Here are some rulesets that I can recommend for the Shareaza P2P file sharing client. I have used them myself and experienced good connectivity and no functional issues.

Shareaza Basic Ruleset:

Shareaza HTTP Connection Rule
Where the protocol is: TCP
Where the direction is: Outbound
Where the remote port is: 80
Allow It

Shareaza Outbound Network Connection Rule
Where the protocol is: TCP
Where the direction is: Outbound
Where the remote port is: 6346 - 6347
Allow It

Shareaza Inbound Network Connection Rule Note: To share your files.
Where the protocol is: TCP
Where the direction is: Inbound
Where the local port is: 6346 - 6347
Allow It Note: Change to deny it if you do NOT want to share

Shareaza Extended TCP Port Coverage
Where the protocol is: TCP
Deny It Note: Blocks TCP connections not allowed by rules above.

Shareaza Extended UDP Port Coverage
Where the protocol is: UDP
Deny It Note: Blocks UDP connections not allowed by rules above.

Note: Make all of the rules in the order that I have listed above, otherwise they will not work right. It is very important that the TCP and UDP Extended Port Coverage Rules be last for proper functioning. This setup will help avoid rule creation popups for clients using non-standard (undefined) ports and also if your client tries to use a non-standard (undefined) port.

If you would like to maximize your clients ability to establish outbound connections to other clients while still minimizing the inbound connections, then you could open up your ruleset like this:

Shareaza Advanced Outbound Connection Ruleset:

Shareaza HTTP Connection Rule
Where the protocol is: TCP
Where the direction is: Outbound
Where the remote port is: 80
Allow It

Shareaza Outbound Network Connection Rule
Where the protocol is: TCP
Where the direction is: Outbound
Where the remote port is: 1024 - 65535
Allow It

Shareaza Inbound Network Connection Rule Note: To share your files.
Where the protocol is: TCP
Where the direction is: Inbound
Where the local port is: 6346 - 6347
Allow It Note: Change to deny it if you do NOT want to share

Shareaza Extended TCP Port Coverage
Where the protocol is: TCP
Deny It Note: Blocks TCP connections not allowed by rules above.

Shareaza Extended UDP Port Coverage
Where the protocol is: UDP
Deny It Note: Blocks UDP connections not allowed by rules above.

Note: Make all of the rules in the order that I have listed above, otherwise they will not work right. It is very important that the TCP and UDP Extended Port Coverage Rules be last for proper functioning. This setup will help avoid rule creation popups for clients using non-standard (undefined) ports and also if your client tries to use a non-standard (undefined) port.

If you would like to maximize your clients ability to establish outbound connections to other clients and also maximize other clients ability to connect to you, then you could open up your ruleset like this:

Shareaza Advanced Connection Ruleset:

Shareaza HTTP Connection Rule
Where the protocol is: TCP
Where the direction is: Outbound
Where the remote port is: 80
Allow It

Shareaza Outbound Network Connection Rule
Where the protocol is: TCP
Where the direction is: Outbound
Where the remote port is: 1024 - 65535
Allow It

Shareaza Inbound Network Connection Rule Note: To share your files.
Where the protocol is: TCP
Where the direction is: Inbound
Where the local port is: 1024 - 65535
Allow It Note: Change to deny it if you do NOT want to share.

Shareaza Extended TCP Port Coverage
Where the protocol is: TCP
Deny It Note: Blocks TCP connections not allowed by rules above

Shareaza Extended UDP Port Coverage
Where the protocol is: UDP
Deny It Note: Blocks UDP connections not allowed by rules above.

Note: Make all of the rules in the order that I have listed above, otherwise they will not work right. It is very important that the TCP and UDP Extended Port Coverage Rules be last for proper functioning. This setup will help avoid rule creation popups for clients using non-standard (undefined) ports and also if your client tries to use a non-standard (undefined) port.

Remember that ALL of the rulesets that I have listed above ONLY apply to Shareaza, so you even if you use one of the two advanced rulesets that I have listed above, you should experience no security problems. The rules for Shareaza WILL NOT allow access to any other application or system resourse over those port ranges.

Well, that is all of the information that I can give at the moment. Remember to go through ALL of the configuration screens of Shareaza and make the settings that you wish. Proper P2P Client setup is very important if you want to avoid problems. If you have any questions about the proposed rulesets that I have provided, please let me know.

Have a good day.

[thurstydog]

Hi David,

thank you very much for these rulesets. But the second and third one seem exactly the same to me .....


But thanx anyway


Thurstydog

[David]

Hi thurstydog,

Welcome to the forums. Right you are. I do a lot of cutting and pasting to save time since the rulesets are similar. On the last ruleset, I meant to extend the range of the inbound connections also. I have made the correction to my previous post. There are a couple of even less restrictive choices, but I really like the design and function of the rulesets above. Although I strongly recommend using the ruleset, here are two more options.

Shareaza Trusted TCP Connection Ruleset:

Shareaza Outbound Network Connection Rule
Where the protocol is: TCP
Where the direction is: Outbound
Allow It

Shareaza Inbound Network Connection Rule Note: To share your files.
Where the protocol is: TCP
Where the direction is: Inbound Note: Change to deny it if you do NOT want to share.
Allow It

Shareaza Extended UDP Port Coverage
Where the protocol is: UDP
Deny It Note: Blocks UDP connections not allowed by rules above.

Note: You will notice that I am not using the TCP Extended Coverage rule for this more liberal ruleset. The reason is because all TCP port connections are already allowed for Shareaza if you use this ruleset.

And, last of all, P2P applications can be made Trusted Applications. This opens up the full TCP and UDP port range, but ONLY to that application, NOT to other applications or system services. So, making Shareaza a Trusted Application is also an option.

I hope that adding two more options to the three that I have given previously has not confused you. I just wrote these last two options so that you and other users are aware of those methods and also for general information purposes. But, my preference and my recommendation is to just use one of the three rulesets that I presented in my original post, written above. In the end, it is the users choice and I do not think any of the choices are bad.

Thanks for pointing out my error. As I have said, it is now corrected. If you have any more questions about the comments or advice given in this thread, please let me know.

Have a good day.

[guitarhero]

No UDP at all? Not even the one port?

[David]

Not unless it is used as some sort of a control port for one of the protocols that Shareaza Supports. However, I will not make rulesets for Beta Software. So, I will not include any rules for other protocols until Shareaza 1.9 is final. The rules above are more than adequate for the Gnutella and Gnutella 2 networks used by the Gnutella 1.8 Series. If you do not feel that you the connectivity that you desire for Shareaza, then make it a trusted application.

[David]

Hello,

A new Shareaza Release Candidate has been issued. So, for those of you using Shareaza, you may want to click on the link below and get your copy.

Shareaza v1.8.9.17 Release Candidate

Have a good day.

[c0n73nd3r]

Hello David,

I was wondering if those rules could also be applied to KazaaLite?

If not, do you or anyone else have some suggestions on a good ruleset for KazaaLite?

[David]

c0n73nd3r,

The Kazaa network is somewhat different. If you were going to apply any of the rules above, I would try the Advanced Connection Ruleset in the first post above. That is a good general purpose ruleset. The only thing that you may have to add is rule to Allow UDP 1214. But, don't add it unless it is necessary. And if you do add the rule, it must be ABOVE the TCP and UDP deny rules that terminate the ruleset.

I hope that helps get you started.

Have a good day.

[vince32837]

Hi David,

I'm running Outpost 2.0 Pro. I installed the latest version of Shareaza. I loaded your rule set versions 1 then tried version 2. In both rules wizard and block most modes. Shareaza runs shows it searching for files but it hangs never returning a file result. I exited outpost to confirm there is a conflict, ran a another file search files come up after 10 seconds. I even deleted your last 2 rules TCP and UDP port coverage.... still hangs but pop-ups show up as you stated.

Any ideas??


Thanks Vince

[David]

Hi vince,

For a test, you might try making it a Trusted Application. If that works, then try these rules:

TCP, Out, Allow It

TCP, Deny It

UDP, Deny It

If it works as Trusted, but not with the three rules listed here, let me know. The ruleset does need some minor tweaking for the added protocols, but the ruleset above really should work. It should at least work for getting good access to the Gnutella network.

Keep us advised of your progress.

By the way, I plan to update the Shareaza ruleset once version 1.9 is final. I want to see the finished product before recommending anything.

Have a good day.

[vince32837]

David,

I will give a try.

Thanks Vince

[David]

Hi Vince,

Good luck and let us know if the problem persists.

[Wile Coyote]

Hi, i've created another ruleset for Shareaza which is working better for me. Because with the new client it is possible to connect to the edonkey network, Bit Torrent and Gnutella 1 and 2
So here it is:

[Shareaza]
VisibleState: 1
Exe:
Shareaza, Shareaza.exe
DefaultState: 1
RuleName: Shareaza HTTP connection
Protocol: TCP
RemotePort: 80-83, 443, 1080, 3128, 8080, 8088, 11523
Direction: Outbound
AllowIt

DefaultState: 1
RuleName: Shareaza Connections to Servers
Protocol: TCP
Direction: Outbound
AllowIt

DefaultState: 1
RuleName: Shareaza Source Asking to other Clients
Protocol: UDP
Direction: Outbound
AllowIt

DefaultState: 1
RuleName: Shareaza Connections from other Clients
Protocol: TCP
LocalPort: 4661-4663, 6346-6348
Direction: Inbound
AllowIt

DefaultState: 1
RuleName: Shareaza Source Asking from other Clients
Protocol: UDP
LocalPort: 3000-8000
Direction: Inbound
AllowIt

DefaultState: 1
RuleName: Shareaza Inbound TCP Connections Not Allowed
Protocol: TCP
LocalPort: 1-1024
Direction: Inbound
BlockIt

DefaultState: 1
RuleName: Shareaza Inbound UDP Connections Not Allowed
Protocol: UDP
LocalPort: 1-1024
Direction: Inbound
BlockIt

Maybe somebody likes it.
Rgds
Wile Coyote

[David]

Wile Coyote,

Looks like a good ruleset. I may have organized them a little differently. But, it really does not matter. Thanks for sharing the ruleset as I have not tried the new Shareaza client yet. I will probably also post my own recommendations for rules after I give the new client a try.

[cyberdog]

Hi,
I have just setup Shareaza with the basic rule set that David suggests. Just one question, the rules that where created when I installed Shareaze, do I use them with the new ones or do I remove them. Thanks