Opened 6 years ago

#5990 new Bug

upnp / nat-pmp does not use bind_address

Reported by: falk0069 Owned by:
Priority: Normal Milestone: None Set
Component: Transmission Version: 2.84+
Severity: Normal Keywords: upnp
Cc:

Description

If you set the bind-address-ipv4 in the settings.json, the UPnP packets do not honor it (nor does the NAT-PMP packets). I created a little patch against v2.82 I've been using that forces the bind-address to be used for UPnP. I did not fix the NAT-PMP since it required determining the default-gateway. Nor did I address ipv6.

The files I edited were upnp.h, upnp.c, port-forwarding.c, session.c.

Hopefully you can add something like this in a future release. Please see attached patch.

Attachments (1)

upnp.patch (3.1 KB) - added by falk0069 6 years ago.

Download all attachments as: .zip

Change History (1)

Changed 6 years ago by falk0069

Note: See TracTickets for help on using tickets.