<?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: Traceroute multiple interface in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/traceroute-multiple-interface/m-p/4548838#M534062</link>
    <description>use -s &lt;IP_ADDR&gt; as the source IP address:&lt;BR /&gt;&lt;BR /&gt;man traceroute&lt;BR /&gt;    -s addr     Use the IPv4 or IPv6 address addr (which usually is given&lt;BR /&gt;                  as an IPv4/IPv6 number, not a hostname) as the source&lt;BR /&gt;                  address in outgoing probe packets.  On hosts with more&lt;BR /&gt;                  than one IPv4/IPv6 address, this option can be used to&lt;BR /&gt;                  force the source address to be something other than the&lt;BR /&gt;                  IPv4/IPv6 address of the interface the probe packet is&lt;BR /&gt;                  sent on.  If the IPv4/IPv6 address is not one of this&lt;BR /&gt;                  machine's interface addresses, an error is returned and&lt;BR /&gt;                  nothing is sent.  (See the -i flag for another way to do&lt;BR /&gt;                  this.)&lt;BR /&gt;Regards&lt;BR /&gt;sujit&lt;/IP_ADDR&gt;</description>
    <pubDate>Sat, 12 Dec 2009 16:47:59 GMT</pubDate>
    <dc:creator>sujit kumar singh</dc:creator>
    <dc:date>2009-12-12T16:47:59Z</dc:date>
    <item>
      <title>Traceroute multiple interface</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/traceroute-multiple-interface/m-p/4548836#M534060</link>
      <description>Hi all&lt;BR /&gt;I'm going to configure 2 NICs&lt;BR /&gt;Server has 2 lancards.&lt;BR /&gt;&lt;BR /&gt;here is network info..&lt;BR /&gt;[rx2:/]netstat -ni&lt;BR /&gt;Name      Mtu    Network         Address         Ipkts     Ierrs  Opkts    Oerrs  Coll&lt;BR /&gt;lan0        1500   130.21.0.0       130.21.0.17      3824559 0      2519256   0      0   &lt;BR /&gt;lo0         4136   127.0.0.0         127.0.0.1         307255  0      307255    0      0   &lt;BR /&gt;lan5       1500    192.168.10.0     192.168.10.2    17964    0      16453     0      0 &lt;BR /&gt;&lt;BR /&gt;[rx2:/]netstat -nr&lt;BR /&gt;Routing tables&lt;BR /&gt;Destination           Gateway            Flags    Refs   Interface  Pmtu&lt;BR /&gt;127.0.0.1             127.0.0.1             UH         0    lo0        4136&lt;BR /&gt;130.21.0.17          130.21.0.17           UH        0    lan0       4136&lt;BR /&gt;192.168.10.2         192.168.10.2         UH        0    lan5       4136&lt;BR /&gt;192.168.10.0         192.168.10.2         U          2    lan5       1500&lt;BR /&gt;130.21.0.0            130.21.0.17          U          2    lan0       1500&lt;BR /&gt;192.168.10.0         192.168.10.254      UG        0    lan5          0&lt;BR /&gt;127.0.0.0             127.0.0.1             U          0    lo0           0&lt;BR /&gt;default               130.21.0.61          UG        0    lan0          0&lt;BR /&gt;&lt;BR /&gt;When I used to traceroute 192.168.10.254, I'm getting back like below.&lt;BR /&gt;&lt;BR /&gt;[rx2:/]traceroute 192.168.10.254&lt;BR /&gt;traceroute: Warning: Multiple interfaces found; using 130.21.0.17 @ lan0&lt;BR /&gt;traceroute to 192.168.10.254 (192.168.10.254), 30 hops max, 40 byte packets&lt;BR /&gt;&lt;BR /&gt;I wonder that obviously ip 192.168.10.254 is routed on @lan5, but it responds from @lan0&lt;BR /&gt;&lt;BR /&gt;I think it should respond from @lan5. am I thinking wrong?&lt;BR /&gt;&lt;BR /&gt;how can I get back from @lan5 whenever I traceroute 192.168.10.x network interface @lan5</description>
      <pubDate>Sat, 12 Dec 2009 05:32:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/traceroute-multiple-interface/m-p/4548836#M534060</guid>
      <dc:creator>file system</dc:creator>
      <dc:date>2009-12-12T05:32:18Z</dc:date>
    </item>
    <item>
      <title>Re: Traceroute multiple interface</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/traceroute-multiple-interface/m-p/4548837#M534061</link>
      <description>&lt;!--!*#--&gt;      man traceroute&lt;BR /&gt;&lt;BR /&gt;Look for "multi".</description>
      <pubDate>Sat, 12 Dec 2009 06:09:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/traceroute-multiple-interface/m-p/4548837#M534061</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2009-12-12T06:09:29Z</dc:date>
    </item>
    <item>
      <title>Re: Traceroute multiple interface</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/traceroute-multiple-interface/m-p/4548838#M534062</link>
      <description>use -s &lt;IP_ADDR&gt; as the source IP address:&lt;BR /&gt;&lt;BR /&gt;man traceroute&lt;BR /&gt;    -s addr     Use the IPv4 or IPv6 address addr (which usually is given&lt;BR /&gt;                  as an IPv4/IPv6 number, not a hostname) as the source&lt;BR /&gt;                  address in outgoing probe packets.  On hosts with more&lt;BR /&gt;                  than one IPv4/IPv6 address, this option can be used to&lt;BR /&gt;                  force the source address to be something other than the&lt;BR /&gt;                  IPv4/IPv6 address of the interface the probe packet is&lt;BR /&gt;                  sent on.  If the IPv4/IPv6 address is not one of this&lt;BR /&gt;                  machine's interface addresses, an error is returned and&lt;BR /&gt;                  nothing is sent.  (See the -i flag for another way to do&lt;BR /&gt;                  this.)&lt;BR /&gt;Regards&lt;BR /&gt;sujit&lt;/IP_ADDR&gt;</description>
      <pubDate>Sat, 12 Dec 2009 16:47:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/traceroute-multiple-interface/m-p/4548838#M534062</guid>
      <dc:creator>sujit kumar singh</dc:creator>
      <dc:date>2009-12-12T16:47:59Z</dc:date>
    </item>
  </channel>
</rss>

