<?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: bonding - ping dup! in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/bonding-ping-dup/m-p/3348040#M13477</link>
    <description>bonding run correct,&lt;BR /&gt;if I remove one cable all traffic flow to the second interface and yes, I have a bond0 interface.</description>
    <pubDate>Tue, 03 Aug 2004 09:58:55 GMT</pubDate>
    <dc:creator>Stefano Galbusera</dc:creator>
    <dc:date>2004-08-03T09:58:55Z</dc:date>
    <item>
      <title>bonding - ping dup!</title>
      <link>https://community.hpe.com/t5/operating-system-linux/bonding-ping-dup/m-p/3348038#M13475</link>
      <description>Hi,&lt;BR /&gt;I have configure some linux server with two network interfaces in active-backup bonding (kernel 2.4.21-15.Elsmp RedHatES3U2)&lt;BR /&gt;&lt;BR /&gt;when I ping them I recive a dup! (icmp_seq=0 ttl=63 time=0.373 ms (DUP!))&lt;BR /&gt;why?&lt;BR /&gt;tnx&lt;BR /&gt;                             Steve</description>
      <pubDate>Tue, 03 Aug 2004 08:48:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/bonding-ping-dup/m-p/3348038#M13475</guid>
      <dc:creator>Stefano Galbusera</dc:creator>
      <dc:date>2004-08-03T08:48:52Z</dc:date>
    </item>
    <item>
      <title>Re: bonding - ping dup!</title>
      <link>https://community.hpe.com/t5/operating-system-linux/bonding-ping-dup/m-p/3348039#M13476</link>
      <description>I think it might be letting you know its bonded. Try deactiving one of the two NIC's and pinging again.&lt;BR /&gt;&lt;BR /&gt;Also, if you do a service network restart you should see an indication concerning bonding.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 03 Aug 2004 09:23:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/bonding-ping-dup/m-p/3348039#M13476</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2004-08-03T09:23:51Z</dc:date>
    </item>
    <item>
      <title>Re: bonding - ping dup!</title>
      <link>https://community.hpe.com/t5/operating-system-linux/bonding-ping-dup/m-p/3348040#M13477</link>
      <description>bonding run correct,&lt;BR /&gt;if I remove one cable all traffic flow to the second interface and yes, I have a bond0 interface.</description>
      <pubDate>Tue, 03 Aug 2004 09:58:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/bonding-ping-dup/m-p/3348040#M13477</guid>
      <dc:creator>Stefano Galbusera</dc:creator>
      <dc:date>2004-08-03T09:58:55Z</dc:date>
    </item>
    <item>
      <title>Re: bonding - ping dup!</title>
      <link>https://community.hpe.com/t5/operating-system-linux/bonding-ping-dup/m-p/3348041#M13478</link>
      <description>You have also to make the switch work.&lt;BR /&gt;On Cisco switches it's called "etherchannel"-feature which have to be activated on the ports your server plugs in.</description>
      <pubDate>Wed, 11 Aug 2004 13:18:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/bonding-ping-dup/m-p/3348041#M13478</guid>
      <dc:creator>Daniel Ettle</dc:creator>
      <dc:date>2004-08-11T13:18:37Z</dc:date>
    </item>
  </channel>
</rss>

