Re: Issue 77 in iperf: Firewall/NAT traversal options

[ip...@googlecode.com]

Updates:
Summary: Firewall/NAT traversal options

Comment #3 on issue 77 by bltier...@lbl.gov: Firewall/NAT traversal options
http://code.google.com/p/iperf/issues/detail?id=77

changing summary lable

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[ip...@googlecode.com]

Updates:
Owner: jef.posk...@gmail.com

Comment #4 on issue 77 by bltier...@lbl.gov: Firewall/NAT traversal options
http://code.google.com/p/iperf/issues/detail?id=77

(No comment was entered for this change.)

[ip...@googlecode.com]

Comment #5 on issue 77 by liweihu...@gmail.com: Firewall/NAT traversal
options
http://code.google.com/p/iperf/issues/detail?id=77

now -r / -d flag only start a server thead at an other port on client host

[ip...@googlecode.com]

Updates:
Owner: bm...@es.net

Comment #6 on issue 77 by bltier...@es.net: Firewall/NAT traversal options
http://code.google.com/p/iperf/issues/detail?id=77

(No comment was entered for this change.)

[ip...@googlecode.com]

Updates:
Status: WontFix

Comment #7 on issue 77 by bm...@es.net: Firewall/NAT traversal options
http://code.google.com/p/iperf/issues/detail?id=77

-R does enable "reverse" mode transfers from a server to a client. However
it doesn't do anything with respect to opening up firewall ports or doing
port forwarding on NAT boxes, which is the other part of the enhancement
request.

Without making some fairly major changes to iperf3's use of the network (in
particular, that would probably involve multiplexing control and data
transfer on the same TCP connection, and I don't have a solution at all for
UDP), I don't think we can do this.

I know there's are various heuristic ways of doing NAT traversal by
injecting carefully crafted packets into the network, but I can't picture
these fitting into iperf3 into any workable way.

I'm going to mark this as WontFix at this point, but it can be reopened if
there is high demand and if we figure out a practical way to do it.

[ip...@googlecode.com]

Comment #8 on issue 77 by liweihu...@gmail.com: Firewall/NAT traversal
options
http://code.google.com/p/iperf/issues/detail?id=77

so sorry~

[ip...@googlecode.com]

Comment #9 on issue 77 by radoslaw...@gmail.com: Firewall/NAT traversal
options
http://code.google.com/p/iperf/issues/detail?id=77

Could you explain why iperf cannot use existing connection initiated from
client behind NAT to test both upload and download? I don't understand what
is the reason to open new UDP or TCP connection in downlink test (when
using -d or -r option).

[ip...@googlecode.com]

Comment #10 on issue 77 by bm...@es.net: Firewall/NAT traversal options
http://code.google.com/p/iperf/issues/detail?id=77

This issue tracker is deprecated. Please do not post new issues or issue
comments here. Instead, please use the issue tracker at:

https://github.com/esnet/iperf/issues

Thanks.