August 2013 - Test - lists.nanog.org

TCP Performance
by Nick Olsen 27 Aug '13

27 Aug '13

Greetings all, I've got an issue I was hoping to put a few more eyes on. Here's the scenario. Downloading a file at our Border is multiple orders of magnitude faster then a few hops out. Using the same 128MB test file, I tested at two different locations. As well as between them. Using multiple connections improves throughput, However it's the single stream issue we're looking at right now. All testing servers in question are Centos Linux. Orlando Datapath: Cogent>Orlando Border Router (Mikrotik)>HP Procurve Switch> Server Results: 2013-08-29 05:04:09 (52.6 MB/s) - `128mbfile.tgz' saved [127926272/127926272] Cocoa NOC Datapath: Cogent>Orlando Border Router (Mikrotik)>Licensed Microwave Link (300+Mb/s Capacity)>East Orange Router (Mikrotik)> Licensed Microwave Link (300+Mb/s Capacity)>Cocoa Router (Mikrotik)>Licensed Microwave Link (300+Mb/s Capacity)>Colo Router (Mikrotik)>NOC Router (Mikrotik)>HP Procurve Switch>Server Results: 2013-08-26 13:42:25 (398 KB/s) - `128mbfile.tgz' saved [127926272/127926272] Orlando-Cocoa NOC Datapath: Orlando Server>HP Procurve Switch>Orlando Border Router (Mikrotik)>Licensed Microwave Link (300+Mb/s Capacity)>East Orange Router (Mikrotik)> Licensed Microwave Link (300+Mb/s Capacity)>Cocoa Router (Mikrotik)>Licensed Microwave Link (300+Mb/s Capacity)>Colo Router (Mikrotik)>NOC Router(Mikrotik)>HP Procurve Switch>ServerResults: 2013-08-26 13:56:25 (3.31 MB/s) - `128mbfile.tgz' saved [134217728/134217728] Now, For the fun of it. I ran Iperf single TCP between our Cocoa and Orlando POP's. Just like the HTTP test above. (Server has a 100Mb/s port). It maxes out the port, Unlike the HTTP test. [root@ded01 ~]# iperf -c 208.90.219.18------------------------------------------------------------Cli ent connecting to 208.90.219.18, TCP port 5001TCP window size: 16.0 KByte (default)------------------------------------------------------------[ 3] local 206.208.56.130 port 47281 connected with 208.90.219.18 port 5001[ ID] Interval Transfer Bandwidth[ 3] 0.0-10.0 sec 114 MBytes 95.7 Mbits/sec Here's associated packet captures for each transfer. As well as full wget output and traceroutes for each test. As you can see, The tests crossing the wireless links show about 3x more TCP re-transmits/dup ACK's. But I'm not sure I'm sold this could show such a huge drop in throughput. Other then that, nothing really stands out to me as to why these transfers are so much slower. Intra-network iperf testing shows full throughput the whole way with single connection. As well as UDP testing. One thing to note is the Iperf testing has far less TCP re-transmit/dup acks then any of the HTTP testing, Crossing the same Microwave Links and routers. http://cdn.141networks.com/files/captures.zip I appreciate any insight anyone might have. Thanks! Nick Olsen Network Operations (855) FLSPEED x106

2 1

ATT.net postmaster contact
by Drew Weaver 27 Aug '13

27 Aug '13

Howdy, Does anyone know of a good/working ATT.net postmaster contact? We have been trying for several weeks to get an IP that has never been used before removed from the ATT.net blacklist and we aren't getting replies through the forms on their site. Thanks, -Drew

2 1

[NANOG-announce] NANOG Fellowship Program
by Betty Burke <betty＠nanog.org> 26 Aug '13

26 Aug '13

NANOGers: The NANOG's Fellowship <https://www.nanog.org/resources/fellowships> program is announced. The Fellowship program awards two Fellows an opportunity to attend a NANOG Meeting, with the following benefits: • Hotel accommodations at the meeting hotel • Round-trip economy class airfare to the meeting • A small stipend • A NANOG Committee Member Mentor during the meeting *NANOG 59 FELLOWS APPLY NOW!* The Fellowship application found at Abha Ahuja Fellowship<http://nanog.org/resources/fellowships/abha>, and Operator of Tomorrow Fellowship<http://nanog.org/resources/fellowships/Operatoroftomorrow>, will remain *open from August 26, 2013 until 5:00 PM PST on September 9, 2013*. Applications received after that date will be considered for the next NANOG Meeting. NANOG 59 Fellows will be notified by September 18, 2013. *KNOW SOMEONE THAT WOULD BE INTERESTED?* Help spread the word; NANOG Fellowships are available for NANOG 59<http://www.nanog.org/meetings/nanog59/home> ! Please send your questions to fellowship(a)nanog.org. Sincerely, Betty Burke On behalf of the NANOG Fellowship Selection Committee -- Betty Burke NANOG Executive Director 48377 Fremont Boulevard, Suite 117 Fremont, CA 94538 Tel: +1 510 492 4030 _______________________________________________ NANOG-announce mailing list NANOG-announce(a)mailman.nanog.org http://mailman.nanog.org/mailman/listinfo/nanog-announce

1 0

Seeking members for Open IX standards committees
by David Temkin 26 Aug '13

26 Aug '13

The Open IX Board is seeking members for the standards committees that will draft the Data Center/MMR and IXP standards. Each group will have a chair that will be responsible for their committees output. For the initial bodies, the board will pick the chairs - but it is hoped that the committees can be self organizing in the future and would meet on an infrequent basis once the initial standards are complete. If you are interested in working in either of these groups, please send a few lines to board(a)open-ix.org stating which committee you'd like to work on, what your qualifications are, and whether or not you'd like to be considered for chairmanship. Membership is non-discriminatory and all are welcome to volunteer regardless of your industry or employer. For more information on Open-IX, see http://open-ix.org/OIX-Framework-Latest.pdf Regards, -Dave Temkin for the Open-IX Board

1 0

Google contact
by Lumir Srchlm 26 Aug '13

26 Aug '13

Can someone from Google contact me off-list please. After many submissions to have our IP space fixed for geolocation still looking for Slovak Google and Polish news... Thanks Lumir

1 0

CableWiFi SSID in Washington DC?
by Drew Linsalata 26 Aug '13

26 Aug '13

I know, completely non-operational and off topic, but have any of you folks in the DC area seen the CableWiFi SSID around town? Traveling next week and I can't get confirmation nor denial that my Optimum Online account will get me wifi access down there.

5 5

A split window multi ping program
by sharon saadon 26 Aug '13

26 Aug '13

Hello, At the passing month, i looked for some small program that can ping to multiply servers in a split window or a program with a split dos windows, i did not found it, So i developed one :) You can download it here.. http://www.sharontools.com/products/9ping.php Regards, Sharon Saadon

3 4

RE: A split window multi ping program
by John Souvestre 25 Aug '13

25 Aug '13

Hello Sharon. >>> At the passing month, i looked for some small program that can ping to multiply servers in a split window or a program with a split dos windows, i did not found it, So i developed one :) Take a look at MultiPing, from Nessoft: http://www.nessoft.com/multiping/ John John Souvestre - New Orleans LA - (504) 454-0899

1 0

WaPo writes about vulnerabilities in Supermicro IPMIs
by Jay Ashworth 25 Aug '13

25 Aug '13

Presumably, everyone else's are very religious as well. Is anyone here stupid enough not to put the management interfaces behind a firewall/VPN? http://www.washingtonpost.com/blogs/the-switch/wp/2013/08/14/researchers-fi… And should I be nervous that Usenix pointed me *there* for the story, rather than a tech press outlet? Cheers, -- jra -- Jay R. Ashworth Baylink jra(a)baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA #natog +1 727 647 1274

11 14

Last Call and Draft program for RIPE 67
by Filiz Yilmaz 24 Aug '13

24 Aug '13

Dear Colleagues, A list of currently accepted RIPE 67 Plenary talks, BoFs, Tutorials and Workshops is now published at: https://ripe67.ripe.net/programme/meeting-plan/draft-programme/ There are still few slots remaining for a final RIPE 67 programme and RIPE Programme Committee will accept new proposals until 9 September 2013. This is our last call for you to submit your proposals. Kind regards Filiz Yilmaz for RIPE Programme Committee Begin forwarded message: > From: Filiz Yilmaz <koalafil(a)gmail.com> > Subject: Updated CFP for RIPE 67 > Date: 12 Jul 2013 11:22:52 GMT+02:00 > To: "ripe-list(a)ripe.net" <ripe-list(a)ripe.net> > > Dear colleagues, > > RIPE PC is now also accepting "Workshop" proposals for RIPE 67. > > Please find the updated CFP with pointers to all possible presentation formats below and at: > https://ripe67.ripe.net/programme/cfp/ > > Note that the deadline for submissions is still 4 August 2013. > > Kind regards > > Filiz Yilmaz > Chair, RIPE Programme Committee > http://www.ripe.net/ripe/meetings/ripe-meetings/pc > > ------------------ > > Call for Presentations > > A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. > > RIPE 67 will take place from 14-18 October 2013 in Athens, Greece. > > The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary session presentations, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 67. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: > > • IPv6 deployment > • Managing IPv4 scarcity in operations > • Commercial transactions of IPv4 addresses > • Data centre technologies > • Network and DNS operations > • Internet governance and regulatory practices > • Network and routing security > • Content delivery > • Internet peering and mobile data exchange > > Submissions > > RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and not attempt a product demonstration. > > The RIPE PC accepts proposals for different presentation formats, including plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. See the full descriptions of these formats at > https://ripe67.ripe.net/programme/i-want-to-present/presentation-formats/ > > Presenters who are proposing a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. > > In addition to presentations selected in advance for the plenary, the RIPE PC also offers several time slots for “lightning talks”, which are selected immediately before or during the conference. > > The following general requirements apply: > > • Proposals for plenary session presentations, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 4 August 2013, using the meeting submission system (https://ripe67.ripe.net/submit-topic/) Proposals submitted after this date will be considered on a space-available basis. > > • Lightning talks should also be submitted using the meeting submission system (https://ripe67.ripe.net/submit-topic/) and can be submitted just days before the RIPE Meeting starts or even during the meeting week. The allocation of lightning talk slots will be announced in short notice – in some cases on the same day but often one day prior to the relevant session. > > • Presenters should indicate how much time they will require. See more information on time slot allocations per presentation format (https://ripe67.ripe.net/programme/i-want-to-present/presentation-formats/) > > • Proposals for talks will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panelists, presenters and moderators. > > • Due to potential technical issues, it is expected that most, if not all, presenters/panelists will be physically present at the RIPE Meeting. > > If you have any questions or requests concerning content submissions, please email pc [at] ripe [dot] net. > > ------------------

1 0