<?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: Outgoing IP packets routing in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/outgoing-ip-packets-routing/m-p/3391460#M566950</link>
    <description>Hi Enrico,&lt;BR /&gt;&lt;BR /&gt;If lan0 is unplugged, then the default behaviour is *not* to route all the packets through lan1 if they are on different subnets. In your 'netstat -rn' output you can see two routes with the flag "U" flag indicating that network is directly routed through the local interface. That route is determined automatically based on the IP address and subnetmask you configure for the interface.&lt;BR /&gt;&lt;BR /&gt;Post for your 'netstat -rn'.&lt;BR /&gt;&lt;BR /&gt;-Sri</description>
    <pubDate>Fri, 01 Oct 2004 08:41:14 GMT</pubDate>
    <dc:creator>Sridhar Bhaskarla</dc:creator>
    <dc:date>2004-10-01T08:41:14Z</dc:date>
    <item>
      <title>Outgoing IP packets routing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/outgoing-ip-packets-routing/m-p/3391456#M566946</link>
      <description>Hello colleagues,&lt;BR /&gt;I've a machine equipped with two LAN cards, configured on different IP subnetworks; even if the subnetworks are logically different, they are mixed through some devices (i.e. there's a hub where the two IP networks are connected to);&lt;BR /&gt;when the lan0 is unplugged I want that the outgoing IP packets are "blocked", instead they are sent through the lan1 (different subnetwork); we don't use default gateways; how can I force to route the outgoing packets ONLY on the LAN card belonging to the proper subnetwork?&lt;BR /&gt;&lt;BR /&gt;BTW: this problem makes Kerberos fail when the lan0 (first one declared in the /etc/hosts) is unplugged but the lan1 is connected.&lt;BR /&gt;&lt;BR /&gt;Thaks&lt;BR /&gt;Enrico</description>
      <pubDate>Fri, 01 Oct 2004 07:30:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/outgoing-ip-packets-routing/m-p/3391456#M566946</guid>
      <dc:creator>Enrico Venturi</dc:creator>
      <dc:date>2004-10-01T07:30:40Z</dc:date>
    </item>
    <item>
      <title>Re: Outgoing IP packets routing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/outgoing-ip-packets-routing/m-p/3391457#M566947</link>
      <description>We can control with route table entries there.&lt;BR /&gt;&lt;BR /&gt;By deafult it will be routing every network entries using default entries. Can you post your routing and lan configurations as,&lt;BR /&gt;&lt;BR /&gt; #netstat -rn&lt;BR /&gt; #netstat -in&lt;BR /&gt;&lt;BR /&gt; #grep -v '^#' /etc/rc.config.d/netconf &lt;BR /&gt;&lt;BR /&gt;we can modify routing informations so that we can send packets based on it via networks.&lt;BR /&gt;&lt;BR /&gt;Example:&lt;BR /&gt;&lt;BR /&gt; destination gateway&lt;BR /&gt; &lt;LAN1 ip=""&gt;   &lt;LAN1 ip=""&gt;&lt;BR /&gt; &lt;LAN1 ip="" network=""&gt; &lt;LAN1 ip=""&gt;&lt;BR /&gt; &lt;BR /&gt;like that we can manage. You have removed default so that we can block any other packets transmission other than defined on routing  can be blocked / not routed there.&lt;BR /&gt;&lt;BR /&gt;May be because of hostname resolvation / ip-address resolvation ,  "Kerberos fail when the lan0 (first one declared in the /etc/hosts) is unplugged but the lan1 is connected" there.&lt;BR /&gt;&lt;BR /&gt;check as nslookup hostname / ip-address&lt;BR /&gt;&lt;BR /&gt;You have to use lan1 if you disconnect lan0 from the same network machine there.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LAN1&gt;&lt;/LAN1&gt;&lt;/LAN1&gt;&lt;/LAN1&gt;</description>
      <pubDate>Fri, 01 Oct 2004 08:20:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/outgoing-ip-packets-routing/m-p/3391457#M566947</guid>
      <dc:creator>Muthukumar_5</dc:creator>
      <dc:date>2004-10-01T08:20:02Z</dc:date>
    </item>
    <item>
      <title>Re: Outgoing IP packets routing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/outgoing-ip-packets-routing/m-p/3391458#M566948</link>
      <description>What I understand from your question is You want to direct IP traffic to the card which is connected at the time. &lt;BR /&gt;&lt;BR /&gt;In my view: This is possible as: &lt;BR /&gt;&lt;BR /&gt;- Make your second NIC a standby one, when you disconnect the primary/main NIC, make the standby NIC to take over..there would be some sofware available for it. &lt;BR /&gt;&lt;BR /&gt;- If you want to use both NIC's at a time and when one fails, other should take care of IP traffic of other. This is possible using IP Alissing. You have to put an alias in the DNS..(check for it)..&lt;BR /&gt;Or at application level you have to manage it by saying that "IP1:NIC1|IP2:NIC2" shall take care of your IP traffic. &lt;BR /&gt;For incoming traffic for your server, still it is difficult unless the applications are just internal..then you can change peers and client too in similar too. In theory it might be easy, but at application level you will have to do lot of things. &lt;BR /&gt;Try aliasing at DNS level, that would be best.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Prashant</description>
      <pubDate>Fri, 01 Oct 2004 08:32:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/outgoing-ip-packets-routing/m-p/3391458#M566948</guid>
      <dc:creator>Prashant Zanwar_4</dc:creator>
      <dc:date>2004-10-01T08:32:06Z</dc:date>
    </item>
    <item>
      <title>Re: Outgoing IP packets routing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/outgoing-ip-packets-routing/m-p/3391459#M566949</link>
      <description>No,&lt;BR /&gt;I want to direct subnetwork1 traffic to lan1&lt;BR /&gt;and subnetwork2 traffic to lan2.</description>
      <pubDate>Fri, 01 Oct 2004 08:34:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/outgoing-ip-packets-routing/m-p/3391459#M566949</guid>
      <dc:creator>Enrico Venturi</dc:creator>
      <dc:date>2004-10-01T08:34:52Z</dc:date>
    </item>
    <item>
      <title>Re: Outgoing IP packets routing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/outgoing-ip-packets-routing/m-p/3391460#M566950</link>
      <description>Hi Enrico,&lt;BR /&gt;&lt;BR /&gt;If lan0 is unplugged, then the default behaviour is *not* to route all the packets through lan1 if they are on different subnets. In your 'netstat -rn' output you can see two routes with the flag "U" flag indicating that network is directly routed through the local interface. That route is determined automatically based on the IP address and subnetmask you configure for the interface.&lt;BR /&gt;&lt;BR /&gt;Post for your 'netstat -rn'.&lt;BR /&gt;&lt;BR /&gt;-Sri</description>
      <pubDate>Fri, 01 Oct 2004 08:41:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/outgoing-ip-packets-routing/m-p/3391460#M566950</guid>
      <dc:creator>Sridhar Bhaskarla</dc:creator>
      <dc:date>2004-10-01T08:41:14Z</dc:date>
    </item>
    <item>
      <title>Re: Outgoing IP packets routing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/outgoing-ip-packets-routing/m-p/3391461#M566951</link>
      <description>IC..Hmm..&lt;BR /&gt;&lt;BR /&gt;You have to address this at application level than at host level. &lt;BR /&gt;&lt;BR /&gt;Applications shall not talk at hostname level. There shall communicate at NIC hardware address and/or IP address only. &lt;BR /&gt;&lt;BR /&gt;Otherwise create a logical name to your host and talk on that level. &lt;BR /&gt;&lt;BR /&gt;IP       hostname&lt;BR /&gt;&lt;IP&gt;     logicalhostname&lt;BR /&gt;&lt;BR /&gt;As we do in serviceguard...use a logical hostname/package name for application. &lt;BR /&gt;This takes care of it.&lt;BR /&gt;Application are bind to talk on logical hostname level this time.&lt;BR /&gt;&lt;BR /&gt;Prashant&lt;/IP&gt;</description>
      <pubDate>Fri, 01 Oct 2004 08:42:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/outgoing-ip-packets-routing/m-p/3391461#M566951</guid>
      <dc:creator>Prashant Zanwar_4</dc:creator>
      <dc:date>2004-10-01T08:42:36Z</dc:date>
    </item>
    <item>
      <title>Re: Outgoing IP packets routing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/outgoing-ip-packets-routing/m-p/3391462#M566952</link>
      <description>You _may_  (I've never tried it myself) get the behaviour you want if you set ip_strong_es_model to a value of 1.</description>
      <pubDate>Sat, 02 Oct 2004 22:07:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/outgoing-ip-packets-routing/m-p/3391462#M566952</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2004-10-02T22:07:50Z</dc:date>
    </item>
    <item>
      <title>Re: Outgoing IP packets routing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/outgoing-ip-packets-routing/m-p/3391463#M566953</link>
      <description>Hi Enrico,&lt;BR /&gt;&lt;BR /&gt;You should look to disable IP forwarding. By default, I guess, this is enabled. &lt;BR /&gt;&lt;BR /&gt;Search in this forum with that keyword for more details.&lt;BR /&gt;&lt;BR /&gt;set the ndd parameter&lt;BR /&gt;&lt;BR /&gt;ndd -set /dev/ip ip_forwarding 0&lt;BR /&gt;&lt;BR /&gt;Edit /etc/rc.config.d/nddconf and put an entry like this&lt;BR /&gt;&lt;BR /&gt;TRANSPORT_NAME=ip &lt;BR /&gt;NDD_NAME=ip_forwarding&lt;BR /&gt;NDD_VALUE=0&lt;BR /&gt;&lt;BR /&gt;This will retain the ndd setting after reboots.&lt;BR /&gt;&lt;BR /&gt;With regards,&lt;BR /&gt;Mohan.</description>
      <pubDate>Sun, 03 Oct 2004 04:33:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/outgoing-ip-packets-routing/m-p/3391463#M566953</guid>
      <dc:creator>Mohanasundaram_1</dc:creator>
      <dc:date>2004-10-03T04:33:11Z</dc:date>
    </item>
  </channel>
</rss>

