Export to GitHub

iperf - issue #98

Tunnel packet support


Posted on Nov 2, 2013 by Grumpy Elephant

Explaination of new feature Add tunnel packet support, like ipv4 in ipv4, ipv4 in ipv6, ipv6 in ipv4, ipv6 in ipv6, GRE tunnel

Justification of new feature This could test the performance of tunnel packets.

Comment #1

Posted on Nov 8, 2013 by Happy Kangaroo

(No comment was entered for this change.)

Comment #2

Posted on Jan 8, 2014 by Happy Dog

Can you give some more details here?

It's quite straightforward to set up a tunnel to another host and run iperf3 over the tunnel using appropriate routing / addressing. How does that differ from what you have in mind?

Comment #3

Posted on Jan 17, 2014 by Grumpy Elephant

I was thinking something similiar to the --parallel option for client. Iperf3 can simulate upto 128 parallel connection and wanted to see if that can be extended to have 128 different tunnels to the server.

Comment #4

Posted on Feb 3, 2014 by Happy Dog

Hrm. As far as I know it's not possible to have multiple GRE or IP-in-IP tunnels between two IP hosts (i.e. a pair of IPv4 addresses). The use of 802.1q VLANs might allow you to do it, by creating tunnels between the VLAN interfaces, but that adds an extra layer of encapsulation and overhead. But in any case the tunneling details are all separate from iperf3.

I admit I'm not 100% sure what you're trying to test, but it feels to me that this could be best done with multiple clients and servers.

Marking this as WontFix, at least for now.

Status: WontFix

Labels:
Type-Enhancement Milestone-future