--
Yes, I mean "Aim" as "Aol Instant Messenger" even though I hate it, it's a good port change option. I ran a netstat with Aim running, and the port is 5190. I double-checked it so it was its port, not the one I was running. About my other question, it is early, but how would we move the network to another port? We'd use all the forums, but what about people who don't look at the forums? Could the program developers put a script in their programs that changes the listening port 5190?

Kirby
[IMG]http://**************.com/ms/kirbykore/images/kirbywave.gif[/IMG]

Perhaps I am not understand exactly what it is you want to do with port 5190. I always thought that a port is used for one type of protocol, not several. If you wanted to switch Gnutella to another port, wouldn't it make sense to use one that is not being used by another service? If using an already claimed port #, there would be more traffic on it than the current network already has. What would be the advantage of using AIM's port?

__________________
~TruStarWarrior~
LimeWire Forum Moderator

Anyone who wants to can choose to listen to ports other than 6346. In fact, many people are already using 6347, 6348, 6349, and 6355. By spreading ourselves out over a larger area, it makes it more difficult to track specific users, but in now way would using another port isolate users from one another. There are always bridges between the ports being used (i.e. people who are connected to both 6346 and 6347 ports).

Yes, we could tell everyone in the forum to switch to another port number is required, but as you have already stated, it is too early and there is no need to do this yet. Yes, developers could write a script that changes the listening port to 5190, or any other port for that matter. Right now, I am working on a Script for Win 98 that will change the port number for you. We'll see if I can get it to work right, and if I do, I'll post it for you. ALter, Kirby!

__________________
~TruStarWarrior~
LimeWire Forum Moderator

I do have a solution for the script idea. I made an executable file for windows that modifies the LimeWire listening port number. But after reading LimeWire's License Agreement, I think it would be in everyone's best interests if I do not distribute it. Unless I get a green light from a LimeWire developer, which I am not currently seeking, I am not going to release it. This type of alteration could potentially fall under the category of backwards engineering, and since LimeWire is not an opensource project, I will respect their rights and will not release any modifying software.

On the other hand, it is relatively easy for users to change the listening port themselves. It's simple enough to go to the options tab and type in a few little digits. So, if we can all coordinate our efforts, we may be able to expand the Gnutella networks should the need arise. :-)

__________________
~TruStarWarrior~
LimeWire Forum Moderator

--
The reason it would be good to switch to 5190 is that when (not an if) ports 6346,6347 are widely blocked, we can move there and if they block 5190, they will also block Aim, and the Aim users will be mad. 5190 is also a good choice because there's not too much alternate traffic. Some idiot might come in and say "Why not switch to port 80?? They can't block that!!" Because the rest of the internet is using that port and it would take hours to connect, let alone download something. For now, it makes sense to stay put on 634*. But
very soon these ports will start being blocked, and we'll need a plan.

Kirby
[IMG]http://**************.com/ms/kirbykore/images/kirbywave.gif[/IMG]

I see what you are saying. This would be feasible as long as we could reach enough people to do this. I noticed that you underlined very in your last post. How soon do you think it will happen? What influences your thinking in this way? Please let us all know. Also, what scheme do you think they could use to block the ports? Would the ISPs do it individually?

I can think of one thing that the RIAA could do. If they modified a gnutella client, they could load it on several hundred conputers hooked up to the internet. Right now, you're thinking "So What??" But, using this vantage point, they could broadcast random, automatically generated quieries, searches, pings, etc. If they had enough of these clients adding massive amounts of traffic to the network, the network would slow to a crawl. It could clog and and not be worth anything to users. The network would be completely jammed and no one could find anything in their searches.

If they did try to do something like this, their effect could be minimized by blocking the hosts that are doing this. We would have to organize an effort to discover all these "bad broadcasters", and we could tell everyone to block them. Or, we could release a script or executable (with LimeWire's permission of course) to block all the known offenders automatically. This is a rather depressing subject, but I know we should all be actively planning for the future. Any ideas, Kirby?

__________________
~TruStarWarrior~
LimeWire Forum Moderator

--
I underlined very for a few reasons, like universities have already started blocking. Mainly because the RIAA is starting to mess around with Gnutella. One guy here had a nasty letter sent to him, so it couldn't be long before they try to get ISPs to block 634*. 5190 isn't too congested at all, I was just downloading on it.

Kirby

[IMG]http://**************.com/ms/kirbykore/images/kirbywave.gif[/IMG]

Universities started blocking a long time ago. Universities also, the majority of them, started refusing to block a long time ago. You are wondering into the area once again of the gov't having to make things illegal, except now your talking about open ports! LOL. I'm sorry, but it seems this conversation is getting more and more ridiculous. Most colleges have already made their decision as to whether or not they wanted to block access, and most have decided not.