{"id":770,"date":"2014-11-24T09:34:40","date_gmt":"2014-11-24T07:34:40","guid":{"rendered":"https:\/\/excentiscom.webhosting.be\/?p=770"},"modified":"2022-06-24T08:32:19","modified_gmt":"2022-06-24T06:32:19","slug":"use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2","status":"publish","type":"post","link":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/","title":{"rendered":"Use Linux Traffic Control as impairment node in a test environment (part 2)"},"content":{"rendered":"

Rigorously testing a network device or distributed service requires complex, realistic network test environments. Linux Traffic Control (tc) with Network Emulation (netem) provides the building blocks to create an impairment node that simulates such networks.<\/p>\n

This three-part series describes how an impairment node can be set up using Linux Traffic Control. In the\u00a0first post<\/a>, Linux Traffic control and its queuing disciplines were introduced. This second part shows which traffic control configurations are available to impair traffic and how to use them. The\u00a0third<\/a> and last part will describe how to get an impairment node up and running!<\/em><\/p>\n

Recap<\/h2>\n

The\u00a0previous<\/a>\u00a0post introduced Linux traffic control and the queuing disciplines that define its behavior. It also described what the default qdisc configuration of a Linux interface looks like. Finally, it showed how this default configuration can be replaced by a hierarchy of custom queuing disciplines.<\/p>\n

Our goal is still to create an Impairment Node device that manipulates traffic between two of its Ethernet interfaces\u00a0eth0<\/tt>\u00a0and\u00a0eth1<\/tt>, while managing it from a third interface (e.g.\u00a0eth2<\/tt>).<\/p>\n

Configuring traffic impairments<\/h2>\n

To impair traffic leaving interface\u00a0eth0<\/tt>, we replace the default root queuing discipline with one of our own. Note that for a symmetrical impairment, the same must be done on the other interface\u00a0eth1<\/tt>!<\/p>\n

Adding a new qdisc to the root of an interface\u2019s qdisc hierarchy (using\u00a0tc qdisc add<\/tt>) actually replaces the default configuration. Deleting a custom configuration (using\u00a0tc qdisc del<\/tt>) actually replaces it with the default.<\/p>\n

While changing a qdisc directly (using\u00a0tc qdisc change<\/tt>\u00a0or\u00a0tc qdisc replace<\/tt>) is also possibly, the examples below start from a clean slate.<\/p>\n

Available impairment configurations<\/h2>\n

So which kinds of impairments are available to simulate network impairments? Let\u2019s have a look!<\/p>\n

Caveat<\/strong>: It is important to note that Traffic Control uses quite odd units. For instance, the\u00a0kbps<\/tt>\u00a0unit denotes\u00a0kibibytes<\/a>\u00a0per second<\/em>. This means that one\u00a0kbps<\/tt>\u00a0equals 1024\u00a0bytes<\/em>\u00a0per second instead of (the expected) 1000\u00a0bits<\/em>\u00a0per second. On the other hand,\u00a0kibibit<\/em>\u00a0(for data) and\u00a0kibibit per second<\/em>\u00a0(for data rate) are both represented by the unit\u00a0kbit<\/tt>. For a full overview, see the\u00a0UNITS<\/em>\u00a0section of the tc\u00a0man page<\/a>\u00a0or this\u00a0faq post<\/a>.<\/p>\n

Throughput<\/h3>\n

To limit the outgoing traffic on an interface, we can use the Token Bucket Filter or\u00a0tbf<\/tt>\u00a0qdisc (man page<\/a>,\u00a0read more<\/a>,\u00a0picture<\/a>). In the\u00a0tbf<\/tt>\u00a0queuing discipline each outgoing traffic byte is serviced by a single\u00a0token.\u00a0<\/em>These tokens are refreshed at the desired output\u00a0rate<\/em>. Tokens are saved up in a\u00a0bucket\u00a0<\/em>of limited size, so smaller bursts of traffic can still be handled at a higher rate.<\/p>\n

\"\"<\/p>\n

This qdisc is typically used to impose a\u00a0soft limit<\/strong>\u00a0on the traffic, which allows limited burst to be sent at line rate, while still respecting the specified rate on average.<\/p>\n

$ tc qdisc add dev eth0 root tbf rate 1mbit burst 32kbit latency 400ms\r\n<\/strong><\/pre>\n
Set the root queuing discipline of eth0 to tbf, with the output rate limited to 1 Mbps. Allows bursts of up to 32kbit to be sent at maximum rate. Packets accumulating a latency of over 400 ms due to the rate limitation are dropped.<\/p><\/blockquote>\n
Using extra options we can limit the\u00a0peak rate<\/em>\u00a0at which bursts themselves are handled. In other words, we can configure the speed at which the\u00a0bucket<\/em>\u00a0gets emptied (read more<\/a>,\u00a0picture<\/a>). By using the same value for both\u00a0rate<\/tt>\u00a0and\u00a0peakrate<\/tt>, we can even put a\u00a0hard throughput limit<\/strong>\u00a0on the output.<\/p>\n
$ tc qdisc add dev eth1 root tbf rate 1mbit burst 32kbit latency 200ms \\ peakrate 1mbit minburst 1520<\/strong><\/pre>\n
Set the root queuing discipline of eth1 to tbf, with the output rate limited to 1 Mbps. Since bursts are also transmitted at a peakrate of 1 Mbps, this is a hard limit. However, allow a minburst of 1520 bytes to be sent at maximum rate, so a typical packet can be sent at once (note 1514 bytes is a typical layer 2 MTU). Packets accumulating a latency of over 200 ms due to the rate limitation are dropped.<\/p><\/blockquote>\n
Latency and jitter<\/h3>\n
Using the\u00a0netem<\/tt>\u00a0qdisc we can emulate network latency and jitter on all outgoing packets (man page<\/a>,\u00a0read more<\/a>). Some examples:<\/p>\n
$ tc qdisc add dev eth0 root netem delay 100ms<\/strong>\r\n<delay packets for 100ms>\r\n\r\n$ tc qdisc add dev eth0 root netem delay 100ms 10ms<\/strong>\r\n<delay packets with value from uniform [90ms-110ms] distribution>\r\n\r\n$ tc qdisc add dev eth0 root netem delay 100ms 10ms 25%<\/strong>\r\n<delay packets with value from uniform [90ms-110ms] distribution and 25% \\\r\n    correlated with value of previous packet>\r\n\r\n$ tc qdisc add dev eth0 root netem delay 100ms 10ms distribution normal<\/strong>\r\n<delay packets with value from normal distribution (mean 100ms, jitter 10ms)>\r\n\r\n$ tc qdisc add dev eth0 root netem delay 100ms 10ms 25% distribution normal<\/strong>\r\n<delay packets with value from normal distribution (mean 100ms, jitter 10ms) \\\r\n    and 25% correlated with value of previous packet><\/pre>\n
Packet loss<\/h2>\n
Using the\u00a0netem<\/tt>\u00a0qdisc packet loss can be emulated as well (man page<\/a>,\u00a0read more<\/a>). Some simple examples:<\/p>\n
$ tc qdisc add dev eth0 root netem loss 0.1%<\/strong>\r\n<drop packets randomly with probability of 0.1%>\r\n\r\n$ tc qdisc add dev eth0 root netem loss 0.3% 25%<\/strong>\r\n<drop packets randomly with probability of 0.3% and 25% correlated with drop \\\r\n    decision for previous packet><\/pre>\n
But netem can even emulate more complex loss mechanism, such as the Gilbert-Elliot scheme. This scheme defines 2 states Good (or drop Gap) and Bad (or drop Burst). The drop chances of both states and the chances of switching between states are all provided. See section 3 of this paper for more info.<\/p>\n
$ tc qdisc add dev eth0 root netem loss gemodel 1% 10% 70% 0.1%<\/strong>\r\n<drop packets using Gilbert-Elliot scheme with probabilities \\\r\n    move-to-burstmode (p) of 1%, move-to-gapmode (r) of 10%, \\\r\n    drop-in-burstmode (1-h) of 70% and drop-in-gapmode (1-k) of 0.1%><\/pre>\n
Duplication and corruption<\/h2>\n
Packet duplication and corruption is also possible with\u00a0netem<\/tt>\u00a0(man page<\/a>,\u00a0read more<\/a>). The examples are self explaining.<\/p>\n
$ tc qdisc add dev eth0 root netem duplicate <chance> [<correlation>]<\/strong>\r\n\r\n$ tc qdisc add dev eth0 root netem corrupt <chance> [<correlation>]<\/strong><\/pre>\n
Reordering<\/h2>\n
Finally,\u00a0netem<\/tt>\u00a0allows packets to be reordered (man page<\/a>,\u00a0read more<\/a>). This is achieved by holding some packets back for a specified amount of time. In other words, reordering will only occur if the interval between packets is smaller than the configured delay!<\/p>\n
Combining multiple impairments<\/h2>\n
Configuring a single impairment is useful for debugging, but to emulate real networks, multiple impairments often need to be active at the same time.<\/p>\n
Multiple\u00a0netem<\/tt>\u00a0impairments can be combined into a\u00a0single<\/em>\u00a0qdisc, as shown in the following example.<\/p>\n
$ tc qdisc add dev eth2 root netem delay 10ms reorder 25% 50% loss 0.2<\/strong><\/pre>\n
To combine these impairments with rate limitation, we need to chain the tbf and netem qdiscs. This process is described in the first post of this series. For example, it would lead to the following commands:<\/p>\n
$ tc qdisc del dev eth0 root\r\n$ tc qdisc add dev eth0 root handle 1: netem delay 10ms reorder 25% 50% loss 0.2%<\/strong>\r\n$ tc qdisc add dev eth0 parent 1: handle 2: tbf rate 1mbit burst 32kbit latency 400ms<\/strong>\r\n$ tc qdisc show dev eth0<\/strong>\r\nqdisc netem 1: root refcnt 2 limit 1000 delay 10.0ms loss 0.2% reorder 25% 50% gap 1\r\nqdisc tbf 2: parent 1: rate 1000Kbit burst 4Kb lat 400.0ms<\/pre>\n
Simply switch the two qdiscs to have the packet\u2019s rate limited first and the impairment applied afterwards.<\/p>\n
Towards an impairment node<\/h2>\n
All buildings blocks are now in place to configure an actual impairment node. This is the subject of the\u00a0third<\/a>\u00a0and last blog post in this series!<\/p>\n","protected":false},"excerpt":{"rendered":"
Rigorously testing a network device or distributed service requires complex, realistic network test environments. Linux Traffic Control (tc) with Network Emulation (netem) provides the building blocks to create an impairment node that simulates such networks. This three-part series describes how an impairment node can be set up using Linux Traffic Control. In the\u00a0first post, Linux …<\/p>\n","protected":false},"author":4,"featured_media":771,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"content-type":"","inline_featured_image":false,"_genesis_block_theme_hide_title":false,"footnotes":""},"categories":[38,63,69],"tags":[],"acf":[],"yoast_head":"\nUse Linux Traffic Control as impairment node in a test environment (part 2) - Excentis<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Use Linux Traffic Control as impairment node in a test environment (part 2) - Excentis\" \/>\n<meta property=\"og:description\" content=\"Rigorously testing a network device or distributed service requires complex, realistic network test environments. Linux Traffic Control (tc) with Network Emulation (netem) provides the building blocks to create an impairment node that simulates such networks. This three-part series describes how an impairment node can be set up using Linux Traffic Control. In the\u00a0first post, Linux …\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/\" \/>\n<meta property=\"og:site_name\" content=\"Excentis\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/Excentis\/\" \/>\n<meta property=\"article:published_time\" content=\"2014-11-24T07:34:40+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-06-24T06:32:19+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_tbf.png\" \/>\n\t<meta property=\"og:image:width\" content=\"536\" \/>\n\t<meta property=\"og:image:height\" content=\"455\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Bram\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@excentis\" \/>\n<meta name=\"twitter:site\" content=\"@excentis\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Bram\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/\"},\"author\":{\"name\":\"Bram\",\"@id\":\"https:\/\/www.excentis.com\/#\/schema\/person\/14a2ac99879eb7b7d4c1a8d666b7a119\"},\"headline\":\"Use Linux Traffic Control as impairment node in a test environment (part 2)\",\"datePublished\":\"2014-11-24T07:34:40+00:00\",\"dateModified\":\"2022-06-24T06:32:19+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/\"},\"wordCount\":939,\"commentCount\":4,\"publisher\":{\"@id\":\"https:\/\/www.excentis.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_tbf.png\",\"articleSection\":[\"Latency\",\"Performance\",\"Throughput\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/\",\"url\":\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/\",\"name\":\"Use Linux Traffic Control as impairment node in a test environment (part 2) - Excentis\",\"isPartOf\":{\"@id\":\"https:\/\/www.excentis.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_tbf.png\",\"datePublished\":\"2014-11-24T07:34:40+00:00\",\"dateModified\":\"2022-06-24T06:32:19+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/#primaryimage\",\"url\":\"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_tbf.png\",\"contentUrl\":\"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_tbf.png\",\"width\":536,\"height\":455},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.excentis.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Use Linux Traffic Control as impairment node in a test environment (part 2)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.excentis.com\/#website\",\"url\":\"https:\/\/www.excentis.com\/\",\"name\":\"Excentis\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/www.excentis.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.excentis.com\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.excentis.com\/#organization\",\"name\":\"Excentis\",\"url\":\"https:\/\/www.excentis.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.excentis.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.excentis.com\/wp-content\/uploads\/logo_excentis_001_1200dpi_sRGB.png\",\"contentUrl\":\"https:\/\/www.excentis.com\/wp-content\/uploads\/logo_excentis_001_1200dpi_sRGB.png\",\"width\":3237,\"height\":450,\"caption\":\"Excentis\"},\"image\":{\"@id\":\"https:\/\/www.excentis.com\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/Excentis\/\",\"https:\/\/twitter.com\/excentis\",\"https:\/\/www.linkedin.com\/company\/excentis\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.excentis.com\/#\/schema\/person\/14a2ac99879eb7b7d4c1a8d666b7a119\",\"name\":\"Bram\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.excentis.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/c2703bf3f7122d24e15d1eba9b10077d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/c2703bf3f7122d24e15d1eba9b10077d?s=96&d=mm&r=g\",\"caption\":\"Bram\"},\"url\":\"https:\/\/www.excentis.com\/author\/excentis_super_admin\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Use Linux Traffic Control as impairment node in a test environment (part 2) - Excentis","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/","og_locale":"en_US","og_type":"article","og_title":"Use Linux Traffic Control as impairment node in a test environment (part 2) - Excentis","og_description":"Rigorously testing a network device or distributed service requires complex, realistic network test environments. Linux Traffic Control (tc) with Network Emulation (netem) provides the building blocks to create an impairment node that simulates such networks. This three-part series describes how an impairment node can be set up using Linux Traffic Control. In the\u00a0first post, Linux …","og_url":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/","og_site_name":"Excentis","article_publisher":"https:\/\/www.facebook.com\/Excentis\/","article_published_time":"2014-11-24T07:34:40+00:00","article_modified_time":"2022-06-24T06:32:19+00:00","og_image":[{"width":536,"height":455,"url":"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_tbf.png","type":"image\/png"}],"author":"Bram","twitter_card":"summary_large_image","twitter_creator":"@excentis","twitter_site":"@excentis","twitter_misc":{"Written by":"Bram","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/#article","isPartOf":{"@id":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/"},"author":{"name":"Bram","@id":"https:\/\/www.excentis.com\/#\/schema\/person\/14a2ac99879eb7b7d4c1a8d666b7a119"},"headline":"Use Linux Traffic Control as impairment node in a test environment (part 2)","datePublished":"2014-11-24T07:34:40+00:00","dateModified":"2022-06-24T06:32:19+00:00","mainEntityOfPage":{"@id":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/"},"wordCount":939,"commentCount":4,"publisher":{"@id":"https:\/\/www.excentis.com\/#organization"},"image":{"@id":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/#primaryimage"},"thumbnailUrl":"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_tbf.png","articleSection":["Latency","Performance","Throughput"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/","url":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/","name":"Use Linux Traffic Control as impairment node in a test environment (part 2) - Excentis","isPartOf":{"@id":"https:\/\/www.excentis.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/#primaryimage"},"image":{"@id":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/#primaryimage"},"thumbnailUrl":"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_tbf.png","datePublished":"2014-11-24T07:34:40+00:00","dateModified":"2022-06-24T06:32:19+00:00","breadcrumb":{"@id":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/#primaryimage","url":"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_tbf.png","contentUrl":"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_tbf.png","width":536,"height":455},{"@type":"BreadcrumbList","@id":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-2\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.excentis.com\/"},{"@type":"ListItem","position":2,"name":"Use Linux Traffic Control as impairment node in a test environment (part 2)"}]},{"@type":"WebSite","@id":"https:\/\/www.excentis.com\/#website","url":"https:\/\/www.excentis.com\/","name":"Excentis","description":"","publisher":{"@id":"https:\/\/www.excentis.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.excentis.com\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.excentis.com\/#organization","name":"Excentis","url":"https:\/\/www.excentis.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.excentis.com\/#\/schema\/logo\/image\/","url":"https:\/\/www.excentis.com\/wp-content\/uploads\/logo_excentis_001_1200dpi_sRGB.png","contentUrl":"https:\/\/www.excentis.com\/wp-content\/uploads\/logo_excentis_001_1200dpi_sRGB.png","width":3237,"height":450,"caption":"Excentis"},"image":{"@id":"https:\/\/www.excentis.com\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/Excentis\/","https:\/\/twitter.com\/excentis","https:\/\/www.linkedin.com\/company\/excentis\/"]},{"@type":"Person","@id":"https:\/\/www.excentis.com\/#\/schema\/person\/14a2ac99879eb7b7d4c1a8d666b7a119","name":"Bram","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.excentis.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/c2703bf3f7122d24e15d1eba9b10077d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/c2703bf3f7122d24e15d1eba9b10077d?s=96&d=mm&r=g","caption":"Bram"},"url":"https:\/\/www.excentis.com\/author\/excentis_super_admin\/"}]}},"featured_image_src":"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_tbf-536x400.png","featured_image_src_square":"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_tbf.png","author_info":{"display_name":"Bram","author_link":"https:\/\/www.excentis.com\/author\/excentis_super_admin\/"},"_links":{"self":[{"href":"https:\/\/www.excentis.com\/wp-json\/wp\/v2\/posts\/770"}],"collection":[{"href":"https:\/\/www.excentis.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.excentis.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.excentis.com\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.excentis.com\/wp-json\/wp\/v2\/comments?post=770"}],"version-history":[{"count":1,"href":"https:\/\/www.excentis.com\/wp-json\/wp\/v2\/posts\/770\/revisions"}],"predecessor-version":[{"id":1966,"href":"https:\/\/www.excentis.com\/wp-json\/wp\/v2\/posts\/770\/revisions\/1966"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.excentis.com\/wp-json\/wp\/v2\/media\/771"}],"wp:attachment":[{"href":"https:\/\/www.excentis.com\/wp-json\/wp\/v2\/media?parent=770"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.excentis.com\/wp-json\/wp\/v2\/categories?post=770"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.excentis.com\/wp-json\/wp\/v2\/tags?post=770"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}