When bandwidth redlines, Port 6346 often looms large. The culprit? Frequently, LimeWire. The peer-to-peer (p2p) networking software. A computer running LimeWire can act as both client and server, hosting unknown files… often copyrighted… for download by unknown outsiders. Around two million unknown outsiders.

[LimeWire.org]

LimeWire is not literally a virus. But that’s small consolation for admins charged with keeping networks fast and secure. Leaky, constipated networks do not enhance career advancement. Same goes for support desk crew, who constantly wade through complaints of suddenly slow PCs, always attended by,”I didn’t install anything!”

Many p2p lovers have traditionally brushed off admin concerns regarding security and bandwidth. But the US Supreme Court’s Grokster decision caught their attention. In essence, it says,”If you produce software and encourage people to violate other people’s copyrights, we’re gonna get you.”

Flush with success, the Recording Industry Association of America (RIAA) crowed:

With this unanimous decision, the Supreme Court has addressed a significant threat to the U.S. economy and moved to protect the livelihoods of the more than 11 million Americans employed by the copyright industries. The Supreme Court has helped to power the digital future for legitimate online businesses - including legal file sharing networks - by holding accountable those who promote and profit from theft. This decision lays the groundwork for the dawn of a new day - an opportunity that will bring the entertainment and technology communities even closer together, with music fans reaping the rewards. — 27 June 2005

RIAA quickly followed with a string of lawsuits aimed at individuals who illegally distribute copyrighted music via peer-to-peer services, including Grokster, eDonkey, KaZaA, and LimeWire. After the Federal Court of Australia declared KaZaA illegal, the world became a very small place for p2p authors.

The stage was set. RIAA fired a warning letter off to p2p developers. And LimeWire fired back… by throwing in the towel. The developers are grinding out a non-infringement version. Users, of course, are outraged.

Is the sordid story of Port 6346 over for harried admins? Not completely. Since LimeWire is open source, you’ll probably be stomping out something on Port 6346 till you block it completely. Then file-sharers will just move on to other ports. Fact is, they already have. Their rallying cry?

Via Slyck Forum: “Limewire users, back up your source codes and learn to compile.”

OK. It’s not quite “Give me liberty or give me death.”

But it’s the best they could do under the circumstances.

See Also: