Actual versions seem to have solved this problem: 4.3.0.6-1
** Changed in: azureus (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/264950
Title:
Az
To use a higher port, just download Vuze directly from sourceforge.
--
Azureus doesn't allow ports above 49151
https://bugs.launchpad.net/bugs/264950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
I think this should be reconsidered by the Vuze development team. I know
Ubuntu's bug tracker is not the best place to try and get their
attention, but it's worth a shot.
You can read my (slightly ranty and undeservingly infuriated) post here:
http://ubuntu-ky.ubuntuforums.org/showthread.php?p=865
** Changed in: azureus (Ubuntu)
Status: Won't Fix => In Progress
--
Azureus doesn't allow ports above 49151
https://bugs.launchpad.net/bugs/264950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
Hi,
I would consider this as a bug because it reduces my ability to use one of my
favorite trackers that will only except ports between 49152 - 65535. I have
been using Azureus for years on windows and never had a problem. This bug
makes Azureus, fairly useless to me on Ubuntu. Is there any hop
Hi,
I just wanted to say that, as goto mentions, as of 7 February 2009 many parts
of the Azureus wiki seem to be really outdated. New users trying to configure
their azureus/vuze should be careful when taking information from there.
In summary, even if the Azureus wiki tells you to "Choose a por
Hello,
I just tried to set my port and it did not work and there was no help (that
helped or explained) why it did not work, it was really strange. There should
be better error messages that explain the strange behaviour.
And on Azureus Wiki ( http://wiki.vuze.com/index.php/Port_is_blacklisted
Well the only thing I see fit to do is to lower the number of ports
reserved because the chances of having ~1000 users running Azureus is
pretty unlikely.
Right now, the choice is either between this or having an arbitrary
local user privilege escalation vulnerability, and frankly if the latter
we
> What happens if the user had a port >49151 and upgrades to this version of
> Azureus? Does it fail miserably or pick some valid port and move on?
It fails, but not miserably :)
It shows a warning message and select another port (randomly ?)
> I spoke with the patch author -- after testing, it's
I spoke with the patch author -- after testing, it's verified that when
you upgrade Azureus with a reserved port, it automatically picks another
one.
With that said, I think that the behavior described in this bug report is not a
bug and doesn't need modification.
** Changed in: azureus (Ubuntu
Just to clarify:
What happens if the user had a port >49151 and upgrades to this version
of Azureus? Does it fail miserably or pick some valid port and move on?
** Changed in: azureus (Ubuntu)
Status: Invalid => Incomplete
--
Azureus doesn't allow ports above 49151
https://bugs.launchpad
> The range shouldn't be used for your main (and static) listen ports
I agree with that but wouldn't it be a better option to let user choose a range
of ports in the Dyn/Priv ports ?
Or for beginners something like :
- start Vuze
- test configured port availability
- available -> continue s
** Changed in: azureus (Ubuntu)
Status: New => Invalid
--
Azureus doesn't allow ports above 49151
https://bugs.launchpad.net/bugs/264950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
This is a consequence of the patch that fixes bug 222630. What was port
6880 is now a dynamic port chosen in that range, see README.multiuser in
the installed docs for further informations.
The range shouldn't be used for your main (and static) listen ports, as
per IANA specification (http://www.i
Just noticed, if I go to Tools>NAT/Firewall Test, it says "TCP ports
above 49152 are reserved internally, so they cannot be used." But since
49152 worked fine yesterday, I'm not sure what it's complaining about.
--
Azureus doesn't allow ports above 49151
https://bugs.launchpad.net/bugs/264950
Yo
15 matches
Mail list logo
