{"id":794,"date":"2015-02-09T10:01:50","date_gmt":"2015-02-09T08:01:50","guid":{"rendered":"https:\/\/excentiscom.webhosting.be\/?p=794"},"modified":"2022-06-24T08:30:04","modified_gmt":"2022-06-24T06:30:04","slug":"use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-3","status":"publish","type":"post","link":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-3\/","title":{"rendered":"Use Linux Traffic Control as impairment node in a test environment (part 3)"},"content":{"rendered":"<p>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<p><em>This three-part series describes how an impairment node can be set up using Linux Traffic Control. In the\u00a0<a href=\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-impairment-node-test-environment-part-1\">first post<\/a>\u00a0Linux Traffic control and its queuing disciplines were introduced. The\u00a0<a href=\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-impairment-node-test-environment-part-2\">second part<\/a>\u00a0showed which traffic control configurations are available to impair traffic and how to use them. This third and final part describes how to get an impairment node up and running!<\/em><\/p>\n<h2>Recap<\/h2>\n<p>We already know how Linux Traffic Control works, what queuing disciplines are available for impairing traffic and how to apply one ore more of those\u00a0<em>qdiscs<\/em>\u00a0to an interface.<\/p>\n<p>Our goal is still to create an impairment node device that manipulates traffic between two of its Ethernet interfaces\u00a0<tt>eth0<\/tt>\u00a0and\u00a0<tt>eth1<\/tt>, while managing it from a third interface (e.g.\u00a0<tt>eth2<\/tt>).<\/p>\n<h2>Impairment node system<\/h2>\n<p>First, we need a system on which the impairment node will run. Luckily, both the hardware and software restrictions are minimal.<\/p>\n<p>The hardware should (1) be able to run a Linux operating system and (2) have at least 3 network interfaces. There are multiple vendors of small dedicated network devices (<a href=\"http:\/\/www.portwell.com\/\">Portwell<\/a>,\u00a0<a href=\"http:\/\/www.lannerinc.com\/\">Lanner<\/a>,\u00a0<a href=\"http:\/\/www.pcengines.ch\/\">PCEngines<\/a>,\u2026) suitable for this task, but an older desktop computer should do the job as well. Running multiple impairments configurations in parallel or impairing multicast traffic obviously requires additional network interfaces (unless\u00a0<a href=\"http:\/\/en.wikipedia.org\/wiki\/Virtual_LAN\">VLAN<\/a>s are used).<\/p>\n<p>Since all Traffic Control functionality is located within the Linux kernel, it is available in all modern Linux distributions. So as far as software is concerned, a fresh server installation of any mainstream distribution (<a href=\"https:\/\/getfedora.org\/\">Fedora<\/a>,\u00a0<a href=\"http:\/\/www.ubuntu.com\/\">Ubuntu<\/a>\u00a0or\u00a0<a href=\"https:\/\/www.debian.org\/\">Debian<\/a>) is ok!<\/p>\n<h2>Automation and configuration<\/h2>\n<p>The impairment node should be both easy to configure and easy to start. This means that a user should be able to simply alter a configuration and update the impairment node without going into Traffic Control details.<\/p>\n<p>To achieve this, all Traffic Control operations are hidden within a single shell script, which you can find on\u00a0<a href=\"https:\/\/github.com\/Excentis\/impairment-node\">GitHub<\/a>\u00a0under a permissive license.<\/p>\n<pre>$ tc.sh apply bypass0 [&lt;impconf&gt;]\r\n$ tc.sh clear bypass0<\/pre>\n<p>where:<\/p>\n<ul>\n<li>Operation\u00a0<tt>clear<\/tt>\u00a0removes all existing impairment configurations and resets the interfaces.<\/li>\n<li>Operation\u00a0<tt>apply<\/tt>\u00a0clears everything as well, applies the specified impairment configuration(s) and resets the interfaces.<\/li>\n<li><tt>bypass0<\/tt>\u00a0forms a layer 2 ethernet bridge between\u00a0<tt>eth0<\/tt>\u00a0and\u00a0<tt>eth1<\/tt>\u00a0on which the impairment configuration(s) are applied. You can easily modify the script to allow additional values, such as\u00a0<tt>bypass1<\/tt>\u00a0and map them to a set of interfaces.<\/li>\n<li>If an impairment configuration\u00a0<tt>impconf<\/tt>\u00a0is passed, that single configuration will be applied. Otherwise one or more configuration will be retrieved from the lines of a configuration file\u00a0<tt>tc.conf<\/tt>\u00a0in the same directory as the script.<\/li>\n<\/ul>\n<p>While it is possible to change existing impairment configurations, its simpler and safer (especially during development or debugging) to always start with a clean slate. This is also how the script operates.<\/p>\n<p>Note the script explicitly excludes network management traffic\u00a0&#8211; ARP, ICMP, IGMP, ICMPv6, DHCP and DHCPv6\u00a0&#8211; from impairment, since such traffic may be required to set up an impairment scenario.<\/p>\n<h2>Declarative impairment configurations<\/h2>\n<p>Impairment configurations can be passed to the script in a declarative way, either directly on the command-line or through the configuration file.<\/p>\n<p>Each impairment configuration takes one of the following forms:<\/p>\n<pre>[&lt;vlanid&gt;];&lt;symmetrical-configuration&gt;\r\n[&lt;vlanid&gt;];&lt;downstream-configuration&gt;;&lt;upstream-configuration&gt;<\/pre>\n<p>where:<\/p>\n<ul>\n<li>A non-empty\u00a0<tt>vlanid<\/tt>\u00a0field causes virtual interfaces to be created on\u00a0<tt>bypassX<\/tt>\u00a0for the specified VLAN ID and a layer2 bridge to be created between those virtual interfaces. Only traffic running on that particular VLAN is affected by the impairments.<\/li>\n<li>A single configuration is interpreted as symmetrical: if\u00a0<tt>bypass0<\/tt>\u00a0links interfaces\u00a0<tt>eth0<\/tt>\u00a0and\u00a0<tt>eth1<\/tt>, the impairment is applied to both interfaces.<\/li>\n<li>Two configurations are used to differentiate between\u00a0<em>downstream<\/em>\u00a0and up<em>stream<\/em>\u00a0traffic: if\u00a0<tt>bypass0<\/tt>\u00a0links interfaces\u00a0<tt>eth0<\/tt>\u00a0and\u00a0<tt>eth1<\/tt>, downstream traffic flows from\u00a0<tt>eth0<\/tt>\u00a0to\u00a0<tt>eth1<\/tt>\u00a0and vice versa.<\/li>\n<li>Each impairment configuration consists of either a single qdisc configuration or two qdisc configurations separated by a comma. In the latter case, the qdiscs will be chained together.<\/li>\n<\/ul>\n<p>Some example configurations and how they are handled by the script:<\/p>\n<pre>;netem delay 500ms\r\n3110;netem delay 100ms;netem delay 300ms\r\n3600;tbf rate 100mbit burst 10kbit latency 200ms,netem delay 5ms loss 5%<\/pre>\n<p><img fetchpriority=\"high\" decoding=\"async\" class=\"alignnone wp-image-795 size-full\" src=\"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_configs.png\" alt=\"\" width=\"530\" height=\"460\" srcset=\"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_configs.png 530w, https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_configs-300x260.png 300w\" sizes=\"(max-width: 530px) 100vw, 530px\" \/><\/p>\n<p>As we explained in the previous post, we typically only need the\u00a0<em>netem<\/em>\u00a0and\u00a0<em>tbf<\/em>\u00a0filters, so chaining two different impairments should suffice. The example\u00a0<tt>tc.conf<\/tt>\u00a0file on\u00a0<a href=\"https:\/\/github.com\/Excentis\/impairment-node\">GitHub<\/a>\u00a0contains some more ideas.<\/p>\n<h2>Example output<\/h2>\n<p>The script prints out what it is doing. As an example, we specify a bidirectional impairment configuration for VLAN ID 2000.<\/p>\n<pre>$ sudo .\/tc.sh apply bypass0 \"2000;netem corrupt 10%\"\r\nClearing previous configuration\r\n\u00a0- Removing all bypass0 bridges...done\r\n\u00a0- Removing all existing impairment configurations on the (virtual) bypass0 interfaces...done\r\n\u00a0- Removing all virtual interfaces on the bypass0 interfaces...done\r\n\u00a0- Removing default (non-virtual) bypass0 bridge...done\r\n\u00a0- Bringing bypass0 interfaces down...done\r\nCreating basic configuration\r\n\u00a0- Creating ethernet bridge...done\r\n\u00a0- Bringing default (non-virtual) bypass0 bridge online...done\r\nApplying provided impairment configuration '2000;netem corrupt 10%'\r\nConfiguring VLAN 2000 with bidirectional impairment config:\r\n\u00a0\u00a0 * 'netem corrupt 10%'\r\n\u00a0\u00a0 * 'netem corrupt 10%'\r\n\u00a0- Creating VLAN interfaces...done\r\n\u00a0- Creating bridge between the VLAN interfaces...done\r\n\u00a0- Bringing VLAN bridge online...done\r\n\u00a0- Applying impairment configuration:\r\n\u00a0\u00a0\u00a0 * Constructing root handler...done\r\n\u00a0\u00a0\u00a0 * Constructing non-impaired queue for dhcp, icmp and arp traffic...done\r\n\u00a0\u00a0\u00a0 * Creating impaired queue for other downstream traffic...done\r\n\u00a0\u00a0\u00a0 * Creating impaired queue for other upstream traffic...done\r\n\u00a0- Applying traffic filters...done\r\nRestarting network...done<\/pre>\n<h2>Further steps<\/h2>\n<p>Of course the implementation described here (and available in our\u00a0<a href=\"https:\/\/github.com\/Excentis\/impairment-node\">impairment-node repository on GitHub<\/a>) is specific to our needs and has itself been constantly evolving\u00a0&#8211; allowing two qdisc definitions that are chained together was the latest addition.<\/p>\n<p>The script can be\u00a0<em>freely<\/em>\u00a0adjusted and used (i.e. in accordance with the 3-clause\u00a0<a href=\"http:\/\/opensource.org\/licenses\/BSD-3-Clause\">BSD license<\/a>) to suit other situations.<\/p>\n<ul>\n<li>Do you want to impair traffic on a layer 3 router instead of a layer 2 bridge? Simply install a Linux based router, such as\u00a0<a href=\"http:\/\/vyos.net\/\">VyOS<\/a>, and run your traffic impairments on that. Strip the bridging and virtual interfaces creation from the script. In the case of VyOS, you can also use or enhance their\u00a0<em>traffic policy subsystem<\/em>, so the configuration is integrated in the router\u2019s command-line interface!<\/li>\n<li>Do you want to test different impairments on different physical sets of interfaces, instead of through different VLAN IDs? Adjust the script accordingly, so more bypasses are supported.<\/li>\n<li>You don\u2019t want to exclude network management traffic? Simply remove the traffic filters section from the script, since all other traffic is sent through the impairment by default.<\/li>\n<\/ul>\n<p>Whether you use the provided script directly, adapt it to your needs or simply take this blog post as a starting point for a fresh implementation, I\u2019d love to hear about your specific use cases and the approach you are taking. Feel free to share them through the comments below!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>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\u00a0Linux Traffic &hellip;<\/p>\n","protected":false},"author":4,"featured_media":795,"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":"<!-- This site is optimized with the Yoast SEO plugin v22.4 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Use Linux Traffic Control as impairment node in a test environment (part 3) - 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-3\/\" \/>\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 3) - 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\u00a0Linux Traffic &hellip;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-3\/\" \/>\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=\"2015-02-09T08:01:50+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-06-24T06:30:04+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_configs.png\" \/>\n\t<meta property=\"og:image:width\" content=\"530\" \/>\n\t<meta property=\"og:image:height\" content=\"460\" \/>\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-3\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-3\/\"},\"author\":{\"name\":\"Bram\",\"@id\":\"https:\/\/www.excentis.com\/#\/schema\/person\/14a2ac99879eb7b7d4c1a8d666b7a119\"},\"headline\":\"Use Linux Traffic Control as impairment node in a test environment (part 3)\",\"datePublished\":\"2015-02-09T08:01:50+00:00\",\"dateModified\":\"2022-06-24T06:30:04+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-3\/\"},\"wordCount\":984,\"commentCount\":7,\"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-3\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_configs.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-3\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-3\/\",\"url\":\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-3\/\",\"name\":\"Use Linux Traffic Control as impairment node in a test environment (part 3) - 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-3\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-3\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_configs.png\",\"datePublished\":\"2015-02-09T08:01:50+00:00\",\"dateModified\":\"2022-06-24T06:30:04+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-3\/#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-3\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-3\/#primaryimage\",\"url\":\"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_configs.png\",\"contentUrl\":\"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_configs.png\",\"width\":530,\"height\":460},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-3\/#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 3)\"}]},{\"@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 3) - 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-3\/","og_locale":"en_US","og_type":"article","og_title":"Use Linux Traffic Control as impairment node in a test environment (part 3) - 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\u00a0Linux Traffic &hellip;","og_url":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-3\/","og_site_name":"Excentis","article_publisher":"https:\/\/www.facebook.com\/Excentis\/","article_published_time":"2015-02-09T08:01:50+00:00","article_modified_time":"2022-06-24T06:30:04+00:00","og_image":[{"width":530,"height":460,"url":"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_configs.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-3\/#article","isPartOf":{"@id":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-3\/"},"author":{"name":"Bram","@id":"https:\/\/www.excentis.com\/#\/schema\/person\/14a2ac99879eb7b7d4c1a8d666b7a119"},"headline":"Use Linux Traffic Control as impairment node in a test environment (part 3)","datePublished":"2015-02-09T08:01:50+00:00","dateModified":"2022-06-24T06:30:04+00:00","mainEntityOfPage":{"@id":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-3\/"},"wordCount":984,"commentCount":7,"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-3\/#primaryimage"},"thumbnailUrl":"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_configs.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-3\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-3\/","url":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-3\/","name":"Use Linux Traffic Control as impairment node in a test environment (part 3) - 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-3\/#primaryimage"},"image":{"@id":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-3\/#primaryimage"},"thumbnailUrl":"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_configs.png","datePublished":"2015-02-09T08:01:50+00:00","dateModified":"2022-06-24T06:30:04+00:00","breadcrumb":{"@id":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-3\/#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-3\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-3\/#primaryimage","url":"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_configs.png","contentUrl":"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_configs.png","width":530,"height":460},{"@type":"BreadcrumbList","@id":"https:\/\/www.excentis.com\/blog\/use-linux-traffic-control-as-impairment-node-in-a-test-environment-part-3\/#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 3)"}]},{"@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_configs-530x400.png","featured_image_src_square":"https:\/\/www.excentis.com\/wp-content\/uploads\/linux_tc_configs.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\/794"}],"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=794"}],"version-history":[{"count":1,"href":"https:\/\/www.excentis.com\/wp-json\/wp\/v2\/posts\/794\/revisions"}],"predecessor-version":[{"id":1957,"href":"https:\/\/www.excentis.com\/wp-json\/wp\/v2\/posts\/794\/revisions\/1957"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.excentis.com\/wp-json\/wp\/v2\/media\/795"}],"wp:attachment":[{"href":"https:\/\/www.excentis.com\/wp-json\/wp\/v2\/media?parent=794"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.excentis.com\/wp-json\/wp\/v2\/categories?post=794"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.excentis.com\/wp-json\/wp\/v2\/tags?post=794"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}