<?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: network routing problem ? in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/network-routing-problem/m-p/2885949#M89005</link>
    <description>can you give me a netstat -r on the Linux box please.&lt;BR /&gt;&lt;BR /&gt;Also run a couple of traceroute commands to the router and to a point beyond the router.&lt;BR /&gt;&lt;BR /&gt;Nice diagram.&lt;BR /&gt;&lt;BR /&gt;P</description>
    <pubDate>Mon, 20 Jan 2003 20:32:49 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2003-01-20T20:32:49Z</dc:date>
    <item>
      <title>network routing problem ?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-routing-problem/m-p/2885948#M89004</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;see the attachment for my problem.&lt;BR /&gt;&lt;BR /&gt;thnx. &lt;BR /&gt;&lt;BR /&gt;rgds. &lt;BR /&gt;&lt;BR /&gt;Steven&lt;BR /&gt;</description>
      <pubDate>Mon, 20 Jan 2003 20:17:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-routing-problem/m-p/2885948#M89004</guid>
      <dc:creator>Steven Mertens</dc:creator>
      <dc:date>2003-01-20T20:17:46Z</dc:date>
    </item>
    <item>
      <title>Re: network routing problem ?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-routing-problem/m-p/2885949#M89005</link>
      <description>can you give me a netstat -r on the Linux box please.&lt;BR /&gt;&lt;BR /&gt;Also run a couple of traceroute commands to the router and to a point beyond the router.&lt;BR /&gt;&lt;BR /&gt;Nice diagram.&lt;BR /&gt;&lt;BR /&gt;P</description>
      <pubDate>Mon, 20 Jan 2003 20:32:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-routing-problem/m-p/2885949#M89005</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-01-20T20:32:49Z</dc:date>
    </item>
    <item>
      <title>Re: network routing problem ?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-routing-problem/m-p/2885950#M89006</link>
      <description>There is a security option to ignore pings which come too close together.  Would think that would apply to both NICs but who knows.  It's to prevent simple DOS attacks.  That's why when you ping your Cisco it will only reply to every other ping.  In a previous post a user claimed the file:&lt;BR /&gt;/proc/sys/net/ipv4/icmp_echoreply_rate&lt;BR /&gt;controlled the response.  He said putting a 0 in the file would make it respond to all pings.  The same thread also suggested that a bad driver could cause this sort of thing.  I have also seen certain HP cards which were sensitive to interference which would fail pings randomly.&lt;BR /&gt;&lt;BR /&gt;You could also try swapping the IP addresses and Ethernet cables to see if the problem moved.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;netstat -s might tell you something.&lt;BR /&gt;&lt;BR /&gt;Look at your tcpdump file again and verify that working pings and failing pings both have the same source IP.  &lt;BR /&gt;&lt;BR /&gt;Wouldn't hurt to do &lt;BR /&gt;sh interface&lt;BR /&gt;on the router and see if you have any obvious problems.  You could also do an extended ping from the router and see if you see the same result.&lt;BR /&gt;&lt;BR /&gt;Ron</description>
      <pubDate>Tue, 21 Jan 2003 16:51:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-routing-problem/m-p/2885950#M89006</guid>
      <dc:creator>Ron Kinner</dc:creator>
      <dc:date>2003-01-21T16:51:08Z</dc:date>
    </item>
    <item>
      <title>Re: network routing problem ?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-routing-problem/m-p/2885951#M89007</link>
      <description>As a last resort, you could replace the nic (eth0) with a known good one.  If it is old, then it could be in the process of failing.</description>
      <pubDate>Thu, 23 Jan 2003 00:52:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-routing-problem/m-p/2885951#M89007</guid>
      <dc:creator>Sunshine Aguilar</dc:creator>
      <dc:date>2003-01-23T00:52:58Z</dc:date>
    </item>
    <item>
      <title>Re: network routing problem ?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-routing-problem/m-p/2885952#M89008</link>
      <description>check the mac of both, and verify after ping with arp command, for the other ip from the remote machine which is in the same network, THis is the first step to check, then if the same guy is responding for both the ip's then stop the routed, as both the network cards are in the same network, you dont require it, and try again</description>
      <pubDate>Thu, 23 Jan 2003 06:54:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-routing-problem/m-p/2885952#M89008</guid>
      <dc:creator>Chakravarthi</dc:creator>
      <dc:date>2003-01-23T06:54:02Z</dc:date>
    </item>
  </channel>
</rss>

