Gå til innhold
Trenger du hjelp med internett og nettverk? Still spørsmål her ×

Torrentbits, problemer med NGT


Anbefalte innlegg

Jeg har en Cisco router fra NGT. Jeg har Charlie abb. På min maskin har jeg 10.0.0.3 som lokal ip.

 

PROBLEMET:

 

Til torrentbits brukes jo portene 6881-6999. Jeg har åpenet disse. Jeg har brukt Azuerus til å prøve å laste ned. Når jeg konfigurer Azuerus får jeg melding om at portene fungere som det skal. Når jeg skal laste ned får jeg meldingen: " Port 6881 is blacklisted". Får altså ikke lastet ned noe som helst :no:

 

Noen som har opplevd det samme problemet, evt har noen råd??

 

På forhånd takk

Lenke til kommentar
Videoannonse
Annonse

Les FAQ en

 

Why do I get a "rejected by tracker - Port xxxx is blacklisted" error?

 

Your client is reporting to the tracker that it uses one of the default bittorrent ports (6881-6889) or any other common p2p port for incoming connections.

 

TorrentBits does not allow clients to use ports commonly associated with p2p protocols. The reason for this is that it is a common practice for ISPs to throttle those ports (that is, limit the bandwidth, hence the speed).

 

The blocked ports list include, but is not neccessarily limited to, the following:

 

Direct Connect

411 - 413

Kazaa

1214

eDonkey

4662

Gnutella

6346 - 6347

BitTorrent

6881 - 6889

 

In order to use use our tracker you must configure your client to use any port range that does not contain those ports (a range within the region 49152 through 65535 is preferable, cf. IANA). Notice that some clients, like Azureus 2.0.7.0 or higher, use a single port for all torrents, while most others use one port per open torrent. The size of the range you choose should take this into account (typically less than 10 ports wide. There is no benefit whatsoever in choosing a wide range, and there are possible security implications).

 

These ports are used for connections between peers, not client to tracker. Therefore this change will not interfere with your ability to use other trackers (in fact it should increase your speed with torrents from any tracker, not just ours). Your client will also still be able to connect to peers that are using the standard ports. If your client does not allow custom ports to be used, you will have to switch to one that does.

 

Do not ask us, or in the forums, which ports you should choose. The more random the choice is the harder it will be for ISPs to catch on to us and start limiting speeds on the ports we use. If we simply define another range ISPs will start throttling that range also.

 

Finally, remember to forward the chosen ports in your router and/or open them in your firewall, should you have them. See the Why is my port listed as "---" section and links therein for more information on this.

Endret av Batou
Lenke til kommentar

Opprett en konto eller logg inn for å kommentere

Du må være et medlem for å kunne skrive en kommentar

Opprett konto

Det er enkelt å melde seg inn for å starte en ny konto!

Start en konto

Logg inn

Har du allerede en konto? Logg inn her.

Logg inn nå
×
×
  • Opprett ny...