upgraded to 1.51 and now port is closed

Ask for help and report issues with the Mac OS X version of Transmission
Post Reply
rawnutz
Posts: 6
Joined: Tue Jan 29, 2008 5:23 pm

upgraded to 1.51 and now port is closed

Post by rawnutz »

have settings in firewall of leopard to accept all incoming connections but no luck now... port 55555 is always closed when it used to be open before i upgrade :(

any help?
essiw
Posts: 567
Joined: Sat Aug 23, 2008 10:40 am
Location: the Netherlands

Re: upgraded to 1.51 and now port is closed

Post by essiw »

read the built in help in Transmission for port forwarding
rawnutz
Posts: 6
Joined: Tue Jan 29, 2008 5:23 pm

Re: upgraded to 1.51 and now port is closed

Post by rawnutz »

essiw wrote:read the built in help in Transmission for port forwarding
but it was cool before i upgraded... why should i now do port forwarding which is just cumbersome
livings124
Transmission Developer
Posts: 3142
Joined: Fri Jan 13, 2006 8:08 pm

Re: upgraded to 1.51 and now port is closed

Post by livings124 »

I can ensure that the port forwarding code hasn't been touched in months. Something must've changed in your setup.
guilherme
Posts: 51
Joined: Thu Jan 22, 2009 6:04 pm

Re: upgraded to 1.51 and now port is closed

Post by guilherme »

From which version did you update from?
Also: eventhough Transmission's code hasn't been changed, could it be that the updated libraries did something?
livings124
Transmission Developer
Posts: 3142
Joined: Fri Jan 13, 2006 8:08 pm

Re: upgraded to 1.51 and now port is closed

Post by livings124 »

I doubt it. Regardless, Transmission's port forwarding is handled by miniupnp (http://miniupnp.tuxfamily.org/), so that's probably the best place to direct your problems.
Passion4diving
Posts: 35
Joined: Fri Dec 05, 2008 11:26 pm

Re: upgraded to 1.51 and now port is closed

Post by Passion4diving »

Had the same problem. Updated to nightly 8040 and the port reopened. I did not touch any of my network settings nor my airport settings.
:mrgreen:
Post Reply