Opened 11 years ago

Closed 11 years ago

#67 closed (fixed)

unable to exchange Iperf TCP traffic over GRE tunnel

Reported by: Owned by: somebody
Priority: major Milestone:
Component: AM Version: SPIRAL5
Keywords: confirmation tests Cc:


Writing ticket to track resolution of problem initially reported to instageni-design.

Slice named IG-CT-3, includes two nodes (1 VM at GPO InstaGENI and 1 VM at Utah InstaGENI). The nodes that were allocated are:

  • VM-2 port 31034
  • VM-1 port 30522

I have been able to exchange traffic between the two hosts (ping and iperf udp), but iperf TCP does not work, client server connections are established but no traffic is exchanged. This is expected to work according to Rob Ricci.

The following is shown on the client side VM-2 (utah):

[lnevers@VM-2 ~]$ /usr/bin/iperf -c -t 60
Client connecting to, TCP port 5001
TCP window size: 16.0 KByte (default)
[  3] local port 46798 connected with port 5001

The test run never completes. The sliver has been renewed.

Change History (3)

comment:1 Changed 11 years ago by

On 12/17/12 11:00 AM, Leigh Stoller wrote:

> Hi. What is the command you are running on the server side please?
> Lbs

The command on the server side is "/usr/bin/iperf -s &"

comment:2 Changed 11 years ago by

On 1/3/13 4:52 PM, Leigh Stoller wrote:

So I updated all of the shared hosts on both racks and Utah with an MTU bug fix that should get this working. I did test it, but of course my luck is terrible these days, so let me know!

A new FEDORA15-OPENVZ-STD image will go out tonite (which only matters if you want to use exclusive OPENVZ nodes instead of shared nodes).


Re-running the test now.

comment:3 Changed 11 years ago by

Resolution: fixed
Status: newclosed

Problem is solved, capturing measurement now got IG-CT-3 for both Utah and GPO. Closing ticket.

Note: See TracTickets for help on using tickets.