BloatLab 1

This is one of the several public labs dedicated to fixing bufferbloat.

This lab is at the offices of the Internet Systems Consortium which is the home of the f-root server,, the internet archive and many other wonderful projects. They have 10GigE connectivity to the internet.

Presently much of this lab has been dissembled and moved to yurtlab.

IPv4, native IPv6 and 6to4 are being tested on a cluster of 7 routers, 2 switches, a pair of PDUs and a perfsonar machine, and a network measurement box, equipped with multiple gigE and wireless-n interfaces. There are also various other random (and growing) pieces of test gear - olpcs, windows XP boxes, 802.11b gear, etc.

In addition to the normal core machines, there are also 2 meshed cerowrt routers spread throughout their (very large) building, doing network measurements as well.

All machines are in the subdomain. DNS for the lab is served by, signed with dnssec, which is, of course, a cerowrt router, also.

The principal public facing routers (jupiter and europa ) are equipped with strongswan and web and rsync servers for network measurements. Jupiter acts as a real-world native ipv6 gateway, europa used to act as a 6to4 gateway, and is now testing quagga-re. There is also a stock netgear router, also public-facing.

There is a native IPv6 /48 network in place behind the routers, with quagga doing BGP multi-homing (one day). We are in the process of adding snmp monitoring tools. is an x86 box equipped with multiple gigE cards and a wireless card for comparison purposes on the same wire. and, in the same data center are also in use for testing, but are used for production purposes.

All these machines have iperf and netperf running, although not configured the same all the time.

A babelweb instance was used on “io” to monitor the health of the routers.

Testlab Design

All internal IP addresses are of the form: 172.29.X.Y.

For router’s main addresses, Y=1 (cerowrt 3.3 and later) or Y=33. The NETworks are the 172.29.X.Z networks they serve.

The ipv6 subnets follow a similar scheme, except in hexadecimal

2001:4f8:fff8:0X00::/56 per router, where X = the X in the ipv4 address.

What’s the naming scheme? Some more details on the testlab machines

Note this document becomes inaccurate about 5 minutes after written.

See also using the testlab


Name EXT IP EXT IPv6 IP NET MAC STATUS Purpose PDU PORT Jupiter 2001:4f8:3:203::2 16 UP Cerowrt GW, primary DNS server
Europa 2001:4f8:3:203::13 22 UP Cerowrt GW
Io 2001:4f8:3:203::14 172.29.X.Z UP Ubuntu 11.10 test/measurement server
Carpo IN progress - underconfigured Perfsonar x86 data collection box
Carme IN progress - underconfigured freeswitch and load generator
Callisto IN progress - underconfigured openwrt build bot

Sol1 Lab PDU
Sol2 Lab Office PDU


Name IP NET MAC STATUS Purpose PDU Assigned Thebe 2 UP
Leda 19 UP
Elara 20 UP
Aitne 22 UP Testgw Dtaht Netgear-stock 21
“veryremote”: 21
“rc6smoke”: 21


Name IP NET MAC STATUS TBD NETGEAR stock Firmware TBD Buffalo Stock Firmware

To edit this page, submit a pull request to the Github repository.
RSS feed

Recent News & Articles

Dec 3, 2022 Wiki page
Codel Wiki
Jun 11, 2022 Wiki page
More about Bufferbloat
Jun 11, 2022 Wiki page
What Can I Do About Bufferbloat?
Jun 11, 2022 Wiki page
Tests for Bufferbloat
Dec 7, 2021 Wiki page
Getting SQM Running Right

Find us elsewhere

Bufferbloat Mailing Lists
#bufferbloat on Twitter
Google+ group
Archived Bufferbloat pages from the Wayback Machine


Comcast Research Innovation Fund
Nlnet Foundation
Shuttleworth Foundation

Bufferbloat Related Projects

OpenWrt Project
Congestion Control Blog
Flent Network Test Suite
The Cake shaper
CeroWrt (where it all started)

Network Performance Related Resources

Jim Gettys' Blog - The chairman of the Fjord
Toke's Blog - Karlstad University's work on bloat
Voip Users Conference - Weekly Videoconference mostly about voip
Candelatech - A wifi testing company that "gets it".