netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Fwd: [multipathtcp] Call for contribution to middlebox survey
       [not found] <985BFFF5-B9DB-4F68-8837-24E434FD08AD@sfc.wide.ad.jp>
@ 2010-10-03  9:28 ` Alexander Zimmermann
  0 siblings, 0 replies; only message in thread
From: Alexander Zimmermann @ 2010-10-03  9:28 UTC (permalink / raw)
  To: Netdev

[-- Attachment #1: Type: text/plain, Size: 5194 bytes --]

Hi folks,

the Michio Honda from IETF Multipath TCP WG needs some help...

Alex

Anfang der weitergeleiteten E-Mail:

> Von: Michio Honda <micchie@sfc.wide.ad.jp>
> Datum: 3. Oktober 2010 01:30:57 MESZ
> An: Multipath TCP Mailing List <multipathtcp@ietf.org>, <tcpm@ietf.org>
> Kopie: Mark Handley <m.handley@cs.ucl.ac.uk>
> Betreff: [multipathtcp] Call for contribution to middlebox survey
> 
> Hi, 
> 
> We are surveying middleboxes affecting TCP in the Internet, and we'd like you to contribute to this work by running 1 python script at your available networks, because we want data of as many paths as possible.    
> This script generates test TCP traffic to a server node, and detects various middlebox behavior, for example, it detects how unknown TCP options are treated and if sequence number is rewritten.  
> 
> - Overview of script
> This generates test TCP traffic by using raw socket or pcap. 
> Destinations of the test traffic are port 80, 443 and 34343 on vinson3.sfc.wide.ad.jp, which is located in Japan. 
> The total amount of test traffic is approximately 90 connections (not parallel), and each of them uses approximately maximum 2048Byte.    
> 
> - System requirement
> Our script works on Mac OSX 10.5 or 10.6, Linux (kernel 2.6) and FreeBSD (7.0 or higher).  This also requires python 2.5 or higher, and libpcap
> NOTE. if you try in a virtual machine on Windows, please connect the guest OS via not NAT but bridge.   
> 
> How to run experiment is described below per-OS basis.  
> 
> After the experiment, you will find 3 log files (logxxxxxxxxx.txt) in the same directory as the experiment.  
> Please send them to us (micchie@sfc.wide.ad.jp) and tell me your network information as much as you know (e.g., product name of the broadband router, ISP name, product name of firewall appliance etc...) 
> In addition, let us know if you have hesitation to open these information.  
> This experiment doesn't collect traffic information other than those our script generated.  
> 
> ***** How to run the experiment (Mac OSX) *****
> 
> 1. Filtering RST TCP segment from OS
> Execute a following command by root:
> ipfw add 101 deny tcp from any to vinson3.sfc.wide.ad.jp dst-port 34343,80,443 tcpflags rst
> 
> NOTE: if you are already running ipfw, please add equivalent rules
> After the experiment, you can revert by "ipfw delete 101"
> 
> 2. Executing script
> Download script from http://www.micchie.net/software/tcpexposure/for_distrib.tar.gz, and decompress it to anywhere you like (e.g., tar xzf for_distrib.tar.gz by command line)
> 
> In the for_distrib directory, execute a following command by root:
> sh run-bsd2.sh
> (This will take approximately 30 min.)
> 
> 
> ***** How to run the experiment (Linux) *****
> 
> 1. Filtering RST TCP segment from OS
> Execute following command by root:
> /sbin/iptables -A OUTPUT -p tcp -d vinson3.sfc.wide.ad.jp --tcp-flags RST RST -m multiport --dports 34343,80,443 -j DROP
> 
> NOTE: if you are already running iptables, please add equivalent rules
> After the experiment, you can revert by opposite commands - using -D instead of -A
> 
> 2. Executing script
> Download script from http://www.micchie.net/software/tcpexposure/for_distrib.tar.gz, and decompress it to anywhere you like (e.g., tar xzf for_distrib.tar.gz)
> 
> In the for_distrib directory, execute a following command by root:
> sh run-linux2.sh
> (This will take approximately 30 min.)
> 
> 
> ***** How to run the script (FreeBSD) *****
> 
> 1. Filtering RST TCP segment from OS   
> If you are using neither ipfw nor pf: 
> Load pf kernel module with a following command by root:
> kldload /boot/kernel/pf.ko
> 
> Add following 2 lines to /etc/pf.conf (please replace IFNAME to your outgoing interface name (e.g., em0):
> pass out all
> block out quick on IFNAME proto tcp to vinson3.sfc.wide.ad.jp port {34343,80,443} flags R/R
> 
> Execute following command by root:
> pfctl -e -f /etc/pf.conf
> 
> If you are already running pf, please add equivalent rules
> After the experiment, you can revert settings by  cleaning up /etc/pf.conf and executing "pfctl -d" by root
> 
> If you are already using ipfw:
>  Please add a following rule to ipfw configuration:
>  deny tcp from any to vinson3.sfc.wide.ad.jp dst-port 34343,80,443 tcpflags rst
> 
> 2. Executing script
> Download script from http://www.micchie.net/software/tcpexposure/for_distrib.tar.gz, and decompress it to anywhere you like (e.g., tar xzf for_distrib.tar.gz)
> 
> In the for_distrib directory, execute a following command by root:
> sh run-bsd2.sh
> (This will take approximately 30 min.)
> 
> 
> Best regards,
> - Michio
> 
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp

//
// Dipl.-Inform. Alexander Zimmermann
// Department of Computer Science, Informatik 4
// RWTH Aachen University
// Ahornstr. 55, 52056 Aachen, Germany
// phone: (49-241) 80-21422, fax: (49-241) 80-22222
// email: zimmermann@cs.rwth-aachen.de
// web: http://www.umic-mesh.net
//


[-- Attachment #2: Signierter Teil der Nachricht --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2010-10-03  9:28 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <985BFFF5-B9DB-4F68-8837-24E434FD08AD@sfc.wide.ad.jp>
2010-10-03  9:28 ` Fwd: [multipathtcp] Call for contribution to middlebox survey Alexander Zimmermann

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).