possible fix for buildbot failure on NAT test case; once a 'NAT' address is used...
authorNathan S. Evans <evans@in.tum.de>
Wed, 8 Sep 2010 13:30:01 +0000 (13:30 +0000)
committerNathan S. Evans <evans@in.tum.de>
Wed, 8 Sep 2010 13:30:01 +0000 (13:30 +0000)
commit8fa400813bab11e04beab9d72f4c41b54b7dc29f
tree5709c9474a1ba71da503ebad91bc5b466de9a913
parentf99e141d6cbe5b2c43b835d450270d3a11724f5a
possible fix for buildbot failure on NAT test case; once a 'NAT' address is used and a connection established, the new connection doesn't have a 'NAT' address (port 0) any longer, because it was built off of an inbound connection from the NAT'd peer.  However, since we initiated the connection we expect that whatever address transport gives us should match.
src/transport/plugin_transport_tcp.c