<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Traffic Engineering with SDN in Software Defined Networking</title>
    <link>https://community.hpe.com/t5/software-defined-networking/traffic-engineering-with-sdn/m-p/6871844#M943</link>
    <description>&lt;P&gt;It worked out as a charm, thank you very much!&lt;/P&gt;</description>
    <pubDate>Thu, 23 Jun 2016 14:20:27 GMT</pubDate>
    <dc:creator>fabioasilva</dc:creator>
    <dc:date>2016-06-23T14:20:27Z</dc:date>
    <item>
      <title>Traffic Engineering with SDN</title>
      <link>https://community.hpe.com/t5/software-defined-networking/traffic-engineering-with-sdn/m-p/6871137#M941</link>
      <description>&lt;P&gt;Hi everyone. I am trying to develop a traffic engineering simulation sdn app, but I'm having trouble to get the traffic to go to the hosts.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Imagine this scenarium:&lt;BR /&gt;&lt;BR /&gt;h0 &amp;lt;--&amp;gt; s0 &amp;lt;--&amp;gt; s1 &amp;lt;---&amp;gt; h1&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm pinging h1 on the h0 CLI and s0 gets the first packet, applies a rule and all next pings match the rule. When I check the HP Controller Inferface via Firefox, I can see through the flows interface of each switch that s0 and s1 are getting packets that match the flow entry. Still, h0 ins't pinging h1... There are images attached to show the problem.&lt;/P&gt;&lt;P&gt;NOTE: I'm using a custom topology on mininet and I specified that the port between a switch and a host is 500.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jun 2016 20:50:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/software-defined-networking/traffic-engineering-with-sdn/m-p/6871137#M941</guid>
      <dc:creator>fabioasilva</dc:creator>
      <dc:date>2016-06-21T20:50:04Z</dc:date>
    </item>
    <item>
      <title>Re: Traffic Engineering with SDN</title>
      <link>https://community.hpe.com/t5/software-defined-networking/traffic-engineering-with-sdn/m-p/6871449#M942</link>
      <description>&lt;P&gt;I noticed that in s0.png, you have a flow that matches ipv4_src=10.0.0.1,ipv4_dst=10.0.0.2 and applies a set_field[vlan_vid:1] action to that packet before outputting to port 1.&lt;/P&gt;&lt;P&gt;I'm not sure how mininet handles vlan tagging, but I don't think that hosts send packets with an 802.1q header. You might need to include push_vlan (in order to add the 802.1q header) for packets arriving from hosts, so that they can traverse the port 500 link between the switches. Then you'd also need a pop_vlan action to strip that vlan tag when the packet is output to the other host port.&lt;/P&gt;&lt;P&gt;Someone please correct me if this is bad information. :)&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jun 2016 19:06:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/software-defined-networking/traffic-engineering-with-sdn/m-p/6871449#M942</guid>
      <dc:creator>ShaunWackerly</dc:creator>
      <dc:date>2016-06-22T19:06:34Z</dc:date>
    </item>
    <item>
      <title>Re: Traffic Engineering with SDN</title>
      <link>https://community.hpe.com/t5/software-defined-networking/traffic-engineering-with-sdn/m-p/6871844#M943</link>
      <description>&lt;P&gt;It worked out as a charm, thank you very much!&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jun 2016 14:20:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/software-defined-networking/traffic-engineering-with-sdn/m-p/6871844#M943</guid>
      <dc:creator>fabioasilva</dc:creator>
      <dc:date>2016-06-23T14:20:27Z</dc:date>
    </item>
  </channel>
</rss>

