Hello Gene,
thank you very much for your answer. However, I am a completly ignorant
regarding NAT... after reading your advice, I went to the NAT howto and
I was scared...
On Mon, 2006-01-30 at 19:26 -0500, Gene Heskett wrote:
On Monday 30 January 2006 17:59, Marcelo Chiapparini wrote:
Dear
On Monday 06 February 2006 07:30, Marcelo Chiapparini wrote:
Hello Gene,
thank you very much for your answer. However, I am a completly
ignorant regarding NAT... after reading your advice, I went to the
NAT howto and I was scared...
On Mon, 2006-01-30 at 19:26 -0500, Gene Heskett wrote:
On
On Monday, February 06, 2006 6:30 AM -0600, Marcelo Chiapparini wrote:
my router, I guess, is with my IP provider... I can't do anything in
that machine...
If you are behind a NAT router, that is the place that you have to
forward ports. Ask your ISP how to log in to your router. Get a
Chris Howie wrote:
Debian-user wrote:
1) Don't use port 6881. Pick something random in the 49152-65535 range.
What's wrong with using port 6881?
Please *DO NOT* set your 'From' address to the list address. It's confusing as
I have no way to tell who sent the message. Adjust your mail
On Mon, Jan 30, 2006 at 04:54:12PM -0700, Debian-user wrote:
Chris Howie wrote:
1) Don't use port 6881. Pick something random in the 49152-65535 range.
What's wrong with using port 6881?
Some trackers will reject any connections from clients on the default
port(s).
signature.asc
Edward Shornock wrote:
On Mon, Jan 30, 2006 at 04:54:12PM -0700, Debian-user wrote:
Chris Howie wrote:
1) Don't use port 6881. Pick something random in the 49152-65535 range.
What's wrong with using port 6881?
Some trackers will reject any connections from clients on the default
port(s).
Scott wrote:
Calm down. Software malfunction.
I just discovered the problem before I got back here and saw your reply.
It wasn't intentional.
Sorry, I didn't mean to come across as angry or upset, I only meant to add
emphasis for the case where it might be intentional (it's happened
I wrote:
They may simply block anything they can't analyze.
Chris Howie writes:
That's a recipie for disaster for any ISP -- they would have to
anticipate every application that will be used by their clients and
authorize it on their analyzer. And if something like this did happen,
chances
Marcelo Chiapparini wrote:
I've just installed Azureus as my .torrent client. During its
configuration the wizard checks for the 6881 TCP port reporting the
following message: Testing port 6881... NAT error. I would like to
know how to open this port. I've surfed the list, googled the web
Chris Howie wrote:
1) Don't use port 6881. Pick something random in the 49152-65535 range.
What's wrong with using port 6881?
Curiously,
--
Scott
www.angrykeyboarder.com
© 2006 angrykeyboarder™ Elmer Fudd. All Wights Wesewved
Debian-user wrote:
1) Don't use port 6881. Pick something random in the 49152-65535 range.
What's wrong with using port 6881?
Please *DO NOT* set your 'From' address to the list address. It's confusing as
I have no way to tell who sent the message. Adjust your mail client settings
before
On Mon, 30 Jan 2006 18:28:27 -0500
Chris Howie [EMAIL PROTECTED] wrote:
Marcelo Chiapparini wrote:
I've just installed Azureus as my .torrent client. During its
configuration the wizard checks for the 6881 TCP port reporting the
following message: Testing port 6881... NAT error. I would
Andrew Sackville-West wrote:
1) Don't use port 6881. Pick something random in the 49152-65535 range.
Are you suggesting this for a reason? or just for diagnostic purposes. I
don't do much with torrent, but once in a whileI do and it never seems to
quite work very well. and yes I port
On Monday 30 January 2006 17:59, Marcelo Chiapparini wrote:
Dear debianners,
I've just installed Azureus as my .torrent client. During its
configuration the wizard checks for the 6881 TCP port reporting the
following message: Testing port 6881... NAT error. I would like to
know how to open this
Chris Howie writes:
Watch ISPs try to filter that. The TLS/SSL wrapper keeps them from
filtering by analyzing the protocol.
They may simply block anything they can't analyze.
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
John Hasler wrote:
Chris Howie writes:
Watch ISPs try to filter that. The TLS/SSL wrapper keeps them from
filtering by analyzing the protocol.
They may simply block anything they can't analyze.
That's a recipie for disaster for any ISP -- they would have to anticipate
every application that
16 matches
Mail list logo
