flow monitor ftp more flows than expected

45 views
Skip to first unread message

zhao yang

unread,
Sep 23, 2016, 10:34:04 AM9/23/16
to ns-3-users
The output is shown below:


Operator A: LTE; number of cells 1; number of UEs 2
Operator B: Wi-Fi; number of cells 1; number of UEs 2
LTE duty cycle: requested 1, actual 1, ABS pattern 0000000000000000000000000000000000000000
Total txop duration: 0 seconds.
Total phy arrivals duration: 0 seconds.
--------monitorA----------
Flow 1 (1.0.0.2:49153 -> 7.0.0.2:50000) proto UDP
  Tx Packets: 354
  Tx Bytes:   521912
  TxOffered:  1.39177 Mbps
  Rx Bytes:   9740
  Throughput: 16.8221 Mbps
  Mean delay:  3.77486 ms
  Mean jitter:  0.142857 ms
  Rx Packets: 7
Flow 2 (1.0.0.2:49154 -> 7.0.0.3:50000) proto UDP
  Tx Packets: 354
  Tx Bytes:   521912
  TxOffered:  1.39177 Mbps
  Rx Bytes:   9740
  Throughput: 13.2878 Mbps
  Mean delay:  4.86403 ms
  Mean jitter:  0.285714 ms
  Rx Packets: 7
Flow 3 (1.0.0.2:49155 -> 7.0.0.2:50000) proto UDP
  Tx Packets: 354
  Tx Bytes:   521912
  TxOffered:  1.39177 Mbps
  Rx Bytes:   18596
  Throughput: 28.4039 Mbps
  Mean delay:  3.85298 ms
  Mean jitter:  0.153846 ms
  Rx Packets: 13
 

Konstantinos

unread,
Sep 23, 2016, 10:46:05 AM9/23/16
to ns-3-users
Hi, 

Not clear what the error is if we do not know the expected one/system model etc.
From the output it looks like you have TWO applications at the node with IP 1.0.0.2 to node 7.0.0.2.
This could be just a programming error in your scenario.

Just a note, normally FTP traffic is using TCP, not UDP to transfer, so do not call it FTP if you are using UDP!

Regards,
K.

zhao yang

unread,
Sep 23, 2016, 10:19:16 PM9/23/16
to ns-3-users
Thanks,  I ran the laa-wifi-indoor.cc. And operator A is configured to LTE, while operator B is configured to WIFI. Ue num per cell is 2, and each operator has 1 cell. The transport is FTP. And it showed the output. 

在 2016年9月23日星期五 UTC+8下午10:46:05,Konstantinos写道:

zhao yang

unread,
Sep 23, 2016, 10:39:34 PM9/23/16
to ns-3-users
I guess since the FtpTransferHelper can not set  local port. So  each file transfer will send a file at a new port. Thus a new flow will be generated for each new file transfer while the client app number is not incremented.


在 2016年9月23日星期五 UTC+8下午10:46:05,Konstantinos写道:
Hi, 
Reply all
Reply to author
Forward
0 new messages