G2 Source Problem and Flooding of the G2 cache.

[skeeterhoss]

I was woundering if there is any way to block cirtian sources from diffrent countries when it comes to the G2 sources?
Ive noticed that sevral times and frequently my G2 connection wont connect due to the connection being flooded with sources from Hong Kong, China, Taiwan and Veitnam that are preventing any other G2 sources from connecting and thoes sources not connecting themself, They just scroll and dont connect.
It would be nice to have an option to connect to cirtian sources that you choose from cirtian countries that you choose when it comes to the G2 and ED2K connections so, This problem wouldent be an issue.

[old_death]

The issue you're having is due to some incompatibility between Foxy and other Gnutella2 clients. If you want to get rid of those clients in your host cache, you can just run the installer and check the option to clear the host cache during the installation process.

As for fixing the problem, one of our devs was working on the issue, but he didn't get much free time ATM, so either the next, or the release after the next one might fix the problem...

As for blocking these clients by IP, I don't think this is possible, as Shareaza can't handle that much items in its security filter system.

[siavoshkc]

[siavoshkc]

Here is the list. Remove all default rules and import this xml (remove .zip by renaming the file).
It doesn't include all IPs but effectively will ban Hong Kong and Taiwan.

EDIT: Not China

[diztrancer]

Blocking HK and Taiwan hosts = EPIC FAIL

[siavoshkc]

We should encourage people to use Shareaza. By banning countries we are advertising those countries to use Foxy. At the other hand I coudn't connect to G2 for one day because of this issue.

The solution is:
If you're a Hub never filter countries.
If you're Leaf clear cache and block countries for initial connection to Hubs and then disable the IP block rules.

[old_death]

[smokex]

Why not add foxy to user agent filter and block it that way? FOXY

[old_death]

Because this doesn't work: The user agent filter needs a connection to be established and the user agent string to be exchanged before being able to identify and block a client. However, Foxy clients do block us basically at the same time (maybe some milliseconds later), so adding FOXY to the user agent string won't do us any good (as it won't really speed up the time from the begin of the connection attempt to the end of it).

[sophist-uk]

Well I downloaded the IP block lists for CN, HK and TW and used Excel to transform these into an importable Security XML file.

But when I imported them it made no difference to whether Shareaza tried to connect to these hubs - until I stopped and restarted Shareaza and then it seems to work just fine!!!

So in case anyone else would like to import the block list, here they are (IP ranges as of a few days ago).

Shareaza Country Block CN HK TW.zip

(19.94 KiB) Downloaded 1049 times

S

[old_death]

Nice work. Maybe you could start a thread with that filter as the first post?

[thecyrez]

[sophist-uk]

[smokex]

Ohai Cedric.

[siavoshkc]

[old_death]

No. What we need to do is remember the source of an alternate IP and remove these alternate IPs from the cache if the source doesn't comply to the G2 standard (e.g. it is Foxy).

[thecyrez]

[old_death]

[thecyrez]

[old_death]

[thecyrez]

[dr-flay]

I don't have a problem with connecting to servers I don't want. Only the first time after install.
I open the cache window and set a bunch of IPs to be my preferred connections (often all the UK ones, as that is where I am).

Over the following days I will remove the ones that fail, but it settles into using them in order of "current Users" as I leave the cache that way round.

Others from other countries, float up the list, but as I can't get the amount of connections on most Chinese caches, they stay at the bottom of the list.
Every now and then I "encourage" the cache with a few more preferred connections.

I do the same thing with G1 to stop myself from connecting to Limewire users. (a matter of principal more than anything).

Not ideal but it works a treat.

... and Oh ! didn't realise http://services.ce3c.be/ciprg/ was not known here, or I would have posted it before !
It's in my "IP and Advert blocking" section, with some other blocking resources.
http://my.opera.com/dr-flay/blog/online-anti-malware
Advanced users are directed at the end of this page -> http://my.opera.com/dr-flay/blog/how-to-block-sites to use the previous link for creating their own block lists.

*EDIT* Of course it is known here
viewtopic.php?f=2&t=1532