#1402 closed Bug (fixed)
constantly maps and unmaps the NAT-PMP port
Reported by: | jah | Owned by: | charles |
---|---|---|---|
Priority: | Normal | Milestone: | 1.40 |
Component: | libtransmission | Version: | 1.34 |
Severity: | Normal | Keywords: | |
Cc: |
Description
Running Mac version:
- Opened network prefs
- changed listening port from 50001 to 54321
- T now constantly maps/unmaps the port, and also constantly checks to see if it is open.
I've attached a log of the behaviour, however here is a sample:
2008-11-02 01:16:10 +1100 natpmp.c:68 [Info] Port Forwarding (NAT-PMP): sendnewportmappingrequest succeeded (12) 2008-11-02 01:16:10 +1100 natpmp.c:68 [Info] Port Forwarding (NAT-PMP): readnatpmpresponseorretry succeeded (0) 2008-11-02 01:16:10 +1100 natpmp.c:171 [Info] Port Forwarding (NAT-PMP): no longer forwarding port 50001 2008-11-02 01:16:10 +1100 port-forwarding.c:100 [Info] Port Forwarding: State changed from "???" to "Starting" 2008-11-02 01:16:10 +1100 port-forwarding.c:108 [Info] Port Forwarding: Closing port 50001 2008-11-02 01:16:10 +1100 net.c:195 [Debug] Transmission: Bound socket 11 to port 54321 2008-11-02 01:16:10 +1100 port-forwarding.c:123 [Info] Port Forwarding: Opened port 54321 to listen for incoming peer connections 2008-11-02 01:16:18 +1100 natpmp.c:68 [Info] Port Forwarding (NAT-PMP): sendnewportmappingrequest succeeded (12) 2008-11-02 01:16:18 +1100 natpmp.c:68 [Info] Port Forwarding (NAT-PMP): readnatpmpresponseorretry succeeded (0) 2008-11-02 01:16:18 +1100 natpmp.c:215 [Info] Port Forwarding (NAT-PMP): Port 50001 forwarded successfully 2008-11-02 01:16:18 +1100 port-forwarding.c:100 [Info] Port Forwarding: State changed from "Starting" to "Forwarded" 2008-11-02 01:16:19 +1100 port-forwarding.c:100 [Info] Port Forwarding: State changed from "Forwarded" to "Stopping" 2008-11-02 01:16:23 +1100 peer-mgr.c:1294 [Debug] Transmission: Banned IP address "213.246.52.12" tried to connect to us 2008-11-02 01:16:26 +1100 natpmp.c:68 [Info] Port Forwarding (NAT-PMP): sendnewportmappingrequest succeeded (12) 2008-11-02 01:16:26 +1100 natpmp.c:68 [Info] Port Forwarding (NAT-PMP): readnatpmpresponseorretry succeeded (0) 2008-11-02 01:16:26 +1100 natpmp.c:171 [Info] Port Forwarding (NAT-PMP): no longer forwarding port 50001 2008-11-02 01:16:26 +1100 port-forwarding.c:100 [Info] Port Forwarding: State changed from "Stopping" to "Starting" 2008-11-02 01:16:34 +1100 natpmp.c:68 [Info] Port Forwarding (NAT-PMP): sendnewportmappingrequest succeeded (12) 2008-11-02 01:16:34 +1100 natpmp.c:68 [Info] Port Forwarding (NAT-PMP): readnatpmpresponseorretry succeeded (0) 2008-11-02 01:16:34 +1100 natpmp.c:215 [Info] Port Forwarding (NAT-PMP): Port 50001 forwarded successfully 2008-11-02 01:16:34 +1100 port-forwarding.c:100 [Info] Port Forwarding: State changed from "Starting" to "Forwarded" 2008-11-02 01:16:34 +1100 peer-mgr.c:1294 [Debug] Transmission: Banned IP address "213.246.52.12" tried to connect to us 2008-11-02 01:16:35 +1100 port-forwarding.c:100 [Info] Port Forwarding: State changed from "Forwarded" to "Stopping"
Attachments (1)
Change History (6)
Changed 12 years ago by jah
comment:1 Changed 12 years ago by livings124
- Component changed from Transmission to libtransmission
- Owner set to charles
- Version changed from 1.34 to 1.34+
comment:2 Changed 12 years ago by charles
Thanks for the log jah. I've never seen this behavior before...
comment:3 Changed 12 years ago by charles
- Milestone changed from None Set to 1.40
- Status changed from new to assigned
- Version changed from 1.34+ to 1.34
jah: could you test >= r7009 and see if the problem persists?
comment:4 Changed 12 years ago by charles
- Resolution set to fixed
- Status changed from assigned to closed
- Summary changed from [r6991] T constantly maps and unmaps the NAT-PMP port to constantly maps and unmaps the NAT-PMP port
confirmed fixed in r7009 by Waldorf
comment:5 Changed 12 years ago by charles
fix committed to 1.3x branch in r7281.
Note: See
TracTickets for help on using
tickets.
log of cycle behaviour