I did a search but couldn't find anything like this, but please excuse a new poster if it has either been answered or is simply part of how Transmission functions.
I am running Transmission 1.75 on OSX 10.6.1 with a 2009 AEBS and current firmware with NAT enabled.
Upon launching Transmission, the spinner next to the port indicator in preferences spins for a few seconds and then indicates the port is closed. However, if I just leave everything alone, after 3-5 minutes the Transmission log is updated and the port then indicates being open (green light).
I've attached the log entries below. Note that Transmission completes its initial load at 15:25:06, seems to get some sort of error message at 15:28:59 and then recovers from the error successfully forwarding the port. The time it takes for this to happen does vary somewhat as I cite in the title of this post. In this case it only took about 4 mins, however it has also taken almost 7 mins as well.
Once its open, everything seems to work fine although I've only used two torrents so far. That said, each were quite large and took about two hours to download so the port remained open and functional for 4 hours so I assume it is working properly. At the end of the day, having to wait 4-7 minutes for Transmission to initiate properly is not a big deal, but I wanted to make sure I wasn't doing something wrong or if there was some sort of bug.
Any thoughts?
thanks,
rwr
2009-10-11 15:25:06 -0400 fdlimit.c:626 [Debug] Transmission: setrlimit( RLIMIT_NOFILE, 712 )
2009-10-11 15:25:06 -0400 fdlimit.c:631 [Debug] Transmission: 200 usable file descriptors
2009-10-11 15:25:06 -0400 net.c:400 [Debug] Transmission: Bound socket 10 to port 51413 on 0.0.0.0
2009-10-11 15:25:06 -0400 net.c:400 [Debug] Transmission: Bound socket 11 to port 51413 on ::
2009-10-11 15:25:06 -0400 rpc-server.c:770 [Info] RPC Server: Adding address to whitelist: 127.0.0.1
2009-10-11 15:25:06 -0400 session.c:874 [Info] Transmission: Transmission 1.75 (9112) started
2009-10-11 15:25:06 -0400 tr-dht.c:142 [Debug] DHT: Initialising DHT
2009-10-11 15:25:06 -0400 tr-dht.c:167 [Info] DHT: Bootstrapping from 156 old nodes
2009-10-11 15:25:06 -0400 tr-dht.c:173 [Info] DHT: Reusing old id
2009-10-11 15:25:06 -0400 tr-dht.c:202 [Debug] DHT: DHT initialised
2009-10-11 15:25:06 -0400 rpc-server.c:770 [Info] RPC Server: Adding address to whitelist: 127.0.0.1
2009-10-11 15:25:06 -0400 natpmp.c:68 [Info] Port Forwarding (NAT-PMP): initnatpmp succeeded (0)
2009-10-11 15:25:06 -0400 natpmp.c:68 [Info] Port Forwarding (NAT-PMP): sendpublicaddressrequest succeeded (2)
2009-10-11 15:28:59 -0400 upnp.c:117 [Debug] Port Forwarding (UPnP): UPNP_GetValidIGD failed (errno 61 - Connection refused)
2009-10-11 15:28:59 -0400 upnp.c:120 [Debug] Port Forwarding (UPnP): If your router supports UPnP, please make sure UPnP is enabled!
2009-10-11 15:28:59 -0400 port-forwarding.c:88 [Info] Port Forwarding: State changed from "Not forwarded" to "Starting"
2009-10-11 15:28:59 -0400 natpmp.c:68 [Info] Port Forwarding (NAT-PMP): readnatpmpresponseorretry succeeded (0)
2009-10-11 15:28:59 -0400 natpmp.c:137 [Info] Port Forwarding (NAT-PMP): Found public address "96.11.34.25"
2009-10-11 15:28:59 -0400 natpmp.c:68 [Info] Port Forwarding (NAT-PMP): sendnewportmappingrequest succeeded (12)
2009-10-11 15:28:59 -0400 natpmp.c:68 [Info] Port Forwarding (NAT-PMP): readnatpmpresponseorretry succeeded (0)
2009-10-11 15:28:59 -0400 natpmp.c:218 [Info] Port Forwarding (NAT-PMP): Port 51413 forwarded successfully
2009-10-11 15:28:59 -0400 port-forwarding.c:88 [Info] Port Forwarding: State changed from "Starting" to "Forwarded"
2009-10-11 15:35:18 -0400 tr-dht.c:119 [Debug] DHT: Finished bootstrapping