Fix a bug using IPFW transparent proxy

We've been working on setting up IPFW transparent proxy on FreeBSD, and ran into a bug when using "TransProxyType ipfw". The attached patch fixes the issue.

Trac:
Username: kmoore134

changed milestone to %Tor: 0.2.6.x-final

added 025-backport 2016-bug-retrospective component::core tor/tor milestone::Tor: 0.2.6.x-final priority::medium reporter::kmoore134 resolution::fixed status::closed tor-client type::defect version::tor 0.2.5.10 labels

Trac:
Username: kmoore134

patch-src_or_connection_edge.c

Trac:
Username: kmoore134

Trac:
Component: - Select a component to Tor
Milestone: N/A to Tor: 0.2.6.x-final
Keywords: N/A deleted, 025-backport tor-client added
Status: new to needs_review

Merged into 0.2.6; marking for possible 025 backport

Trac:
Milestone: Tor: 0.2.6.x-final to Tor: 0.2.5.x-final

public/bug15064_025 is the branch.

Not backporting these.

Trac:
Status: needs_review to closed
Resolution: N/A to fixed
Milestone: Tor: 0.2.5.x-final to Tor: 0.2.6.x-final

Hang on. How did this wind up in maint-0.2.5?

Trac:
Resolution: fixed to N/A
Status: closed to reopened

Ohhhh. I accidentally based the branch for #15205 (moved) on this. Not sure how, but at least I know how to fix it.

Reverting in 0.2.5

Trac:
Status: reopened to closed
Resolution: N/A to fixed

Mark more tickets for bug retrospective based on hand-review of changelogs from 0.2.5 onwards.

Trac:
Keywords: 025-backport tor-client deleted, tor-client, 025-backport, 2016-bug-retrospective added

closed

moved to tpo/core/tor#15064 (closed)