Gnutella Forums

Gnutella Forums (https://www.gnutellaforums.com/)
-   General Gnutella / Gnutella Network Discussion (https://www.gnutellaforums.com/general-gnutella-gnutella-network-discussion/)
-   -   Warning!!! (https://www.gnutellaforums.com/general-gnutella-gnutella-network-discussion/1734-warning.html)

n3tdiver June 10th, 2001 03:13 PM

Warning!!!
 
Hi ppl,

I just wanna warn you for something !

1. Almost all of the *tella different clients are default
set up to use the port 6346 for incoming connection!
2. There is always possibility to change this port to
something differrent.
3. My expirience showed me that it is possible in
this case for an ISP to block *tella traffic and
network as just blocking traffic on port 6346.
4. Almost all of the *tella clients are used with
they default settings.

So i pls. you ppl !! dont use the default port
settings ... one morning it will be too late to
change it. Because of that the computers in
my uni can't use anymore gnutella or bearshare
or whatever based on gnutella protocol !!!!!!!
pls. change it to whatever you want ... it will
still work ... thats the idea ...

MfG,
netdiver.
PS sorryforthebrockenenglish ;) and i mean the things above very serious!!!

Gnutelled Guy June 16th, 2001 09:00 AM

hm ... could experienced people comment this?
 
hey, could someone understanding the gnutella network better than me comment on this? maybe he has got a point here? if we all use some other port, the clients should still be able to check that out and this wouldn't harm the network, would it? so that would certainly make blocking harder then ... are there any pitfalls with this idea?

Unregistered June 16th, 2001 11:46 AM

any port will work and other clients will be able to see you no prob.
i wouldn't change till you see a problem, like if they throttle you or something.
if your client doesn't let you change the port, it sucks, trash it and report it as a bug.

JD June 16th, 2001 03:42 PM

If your firewall blocks you on 6346, only you should need to change your Gnutella client port to an available firewall port.
Everybody you connect to can be whatever they want, even 6346, as long as it works for them.

Example: You go through your port xxxx and into 6346 at the other end. The other end has nothing to do with your firewall settings.
There client will 'know' what port you are on!

I noticed however, that one or the other client have a small problem yet to be fixed, that if you change from 6346 to another port, there are upload problems, or something like that.
A small bug.

JD

Gnutelled Guy June 17th, 2001 09:46 AM

small bug
 
well, upload problems sound criticial. i mean up (thats down for the other direction) are the essence of p2p. but i will try that out and see how well it works. oherwise it sounds good if people would use a variety of ports ...


All times are GMT -7. The time now is 04:26 AM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
SEO by vBSEO 3.6.0 ©2011, Crawlability, Inc.

Copyright © 2020 Gnutella Forums.
All Rights Reserved.