Re: Clarification required in the iperf_self application

[Balraj Singh <balrajsingh@xxxxxxxx>]

Hi Udita,

I use this app with Xen to test the mirage tcp/ip stack.  I haven't tried it with tun/tap on unix, though your steps seem right and it should have worked.  I'll look into it and let you know.

Balraj

On Sat, Jun 22, 2013 at 4:37 PM, Udita Gangwal <psxug2@xxxxxxxxxxxxxxxx> wrote:

Hello All,

I am trying to make the iperf_self application run which is present in the mirage-skeleton. I have used the 4.00.1+mirage-unix version.

I tried to run the app using the commands:

mirari configure --unix iperf_self.conf
mirari build --unix iperf_self.conf
sudo ./mir-iperf_self

Before executing these commands, I also used the ocaml-tuntap to create the tap interfaces and then assigned IP addresses to the 2 interfaces:

sudo ./tunctl.native add tap1
sudo ./tunctl.native add tap2
sudo ifconfig tap1 10.100.100.101 netmask 255.255.255.0
sudo ifconfig tap2 10.100.100.102 netmask 255.255.255.0


I saw that only the iperf server was being set up on a tap interface, but not the iperf client. I then modified the code iperf_self.ml a little; now both the server and the client are being set up on two different tap interfaces.

After the iperf client is set up, the function "iperfclient" is called in the code. The "iperfclient" function then makes use of the pcb.connect function as follows:

lwt conn = Net.Tcp.Pcb.connect tt ~dest_ip:ip ~dest_port:port in
...

However, I do not see the SYN messages being transmitted to the server from the client (using tcpdump on the interfaces).

Could anyone please point out if I have missed anything here? Or is there something else that has to be done too?

Many Thanks,
Udita

This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.