Re: [multipathtcp] Trace format mptcp

Bhumika Parikh <> Mon, 22 August 2016 17:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8E22112B039 for <>; Mon, 22 Aug 2016 10:58:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ydbR-cecBf45 for <>; Mon, 22 Aug 2016 10:58:29 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400c:c08::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9B93E12D169 for <>; Mon, 22 Aug 2016 10:58:26 -0700 (PDT)
Received: by with SMTP id n59so202781912uan.2 for <>; Mon, 22 Aug 2016 10:58:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=kEdMyIn5c75D7tvnNN73tlrulDCN9Vp1dKC321xM/ak=; b=v/9FvfnehwdYAM/A4a+NvsteR2Dd8Hu43obu02twnu3FMLr3aXf5wOTPQvT2AEjWnp NW66hTKVU9WjWyi5X9MF0gqolj84UovLXQXCyqYvYAKCmTvY56rV48e083sGNDEDROgZ vnHcjvaRFN3W5wNuQdGoRy7J/FX2PGEAFSOC3gis2CpCo7lvOtKeTlJutpUjeeObvZqJ 183RpiBuQq+667x0VTMayVwl6WLo44/0hE3zHuulzcyE2r9MXyby0Frc+yiS8LzpXl6P b39E35mbaE45ziSjT9eH6Egi8auksmIS8U0kUfj/Nz2Go7dl/swRH0skX/5dxYlBsPpi +uzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=kEdMyIn5c75D7tvnNN73tlrulDCN9Vp1dKC321xM/ak=; b=HImS/1gRShIqtHj1mSx5/ytkoLKDLl4rgsDI+T+SgqPMhHM6jamPYeWc1RIZlD5MDy 2txqnMnkMfOkGJl/Io5WcJ8KpC1NBWx4VsTVT/aJ6p2QYZIv4TYil2Tef849/XzZZ9Oc mknZHT8YKt2kqCMcuTU7Wpb65DlgVOuQw662o+H735OjaxlAE/xEzW2uIkk4xuMWc6MX qm1V9Yorf94Tj+X9WSPu0wwZ6YfhEJejrOHd7HpEWaUiONVnGDU5PwQuyKq9bHqu5+os 0fyX7VmphgioGIrksyJGyifd56SmdMCczts1M71xsgSW48iMEYaCpsZBBJoO0CXNqYV5 4yXQ==
X-Gm-Message-State: AEkoousmz8w/X2qffkyn5ckzXoCNYtmAddpM1CJ+JyjY8iwZj4z4vd0AniTU+Gru+MR3uhuw6VvbXxEBrhl8qw==
X-Received: by with SMTP id 37mr11857135uak.57.1471888705629; Mon, 22 Aug 2016 10:58:25 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Mon, 22 Aug 2016 10:58:25 -0700 (PDT)
From: Bhumika Parikh <>
Date: Mon, 22 Aug 2016 11:58:25 -0600
Message-ID: <>
Content-Type: multipart/alternative; boundary=001a113efda272b3e0053aaccbf8
Archived-At: <>
X-Mailman-Approved-At: Mon, 22 Aug 2016 11:33:16 -0700
Subject: Re: [multipathtcp] Trace format mptcp
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-path extensions for TCP <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 22 Aug 2016 17:58:30 -0000

Hello all,

I am new to using MPTCP implementation in ns-2.34. I have successfully set
up ns-2.34. I get an error when I run the mptcp-sample.tcl, but can
visualize out.nam <> and The error is something like

*fatal. no mapping info was found. ackno 227265*
Also, I cannot clearly understand the trace file format for the
file. What does each column in the file from which we redirect
values to the mptc normal tcp 1 and normal tcp 2 files represent ?

Is it necessary to use normal tcp1 and tcp2 flows. I could have a single
sender and receiver. I mean n0 and n1 with its interface nodes and
intermediate nodes ??

Please do help me out in this regard.

Thanks & Regards,

Bhumika Parikh
Graduate Student
New Mexico State University