<?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: Outbound connection through floating IP in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/outbound-connection-through-floating-ip/m-p/2470186#M775475</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;There is an interesting discussion about this at:-&lt;BR /&gt;&lt;A href="http://docs.hp.com/hpux/onlinedocs/B3936-90026/B3936-90026.html" target="_blank"&gt;http://docs.hp.com/hpux/onlinedocs/B3936-90026/B3936-90026.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;The section that is significant is the following:-&lt;BR /&gt;&lt;BR /&gt;Call bind() before connect() &lt;BR /&gt;&lt;BR /&gt;When an application initiates its own connection, it should first call bind(2), specifying the application IP address before calling connect(2). Otherwise the connect request will be sent using the stationary IP address of the system's outbound LAN interface rather than the desired relocatable application IP address. The client will receive this IP address from the accept(2) call, possibly confusing the client software and preventing it from working correctly. &lt;BR /&gt;-----------------------------------------------&lt;BR /&gt;&lt;BR /&gt;Thus you must code your application to use the relocatable IP address if it is initiating connections.&lt;BR /&gt;&lt;BR /&gt;If you are need to force 'standard applications' (such as ftp for instance) to use the relocatable address then it seems that your only option is to ensure that the relocatable address is the only address on that interface (also discussed at the above URL).&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;John&lt;BR /&gt;</description>
    <pubDate>Tue, 05 Dec 2000 10:56:48 GMT</pubDate>
    <dc:creator>John Palmer</dc:creator>
    <dc:date>2000-12-05T10:56:48Z</dc:date>
    <item>
      <title>Outbound connection through floating IP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/outbound-connection-through-floating-ip/m-p/2470184#M775473</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I have a MCSG cluster with two nodes.&lt;BR /&gt;All incoming traffic comes to the system through the floating IP. &lt;BR /&gt;&lt;BR /&gt;Is there any way to ensure that all outbound connections from the system  ( where ever the package is running )  use the floating IP rather than the system IP.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance to all those who can reply.&lt;BR /&gt;&lt;BR /&gt;Pramod &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 04 Dec 2000 16:55:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/outbound-connection-through-floating-ip/m-p/2470184#M775473</guid>
      <dc:creator>Pramod_4</dc:creator>
      <dc:date>2000-12-04T16:55:23Z</dc:date>
    </item>
    <item>
      <title>Re: Outbound connection through floating IP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/outbound-connection-through-floating-ip/m-p/2470185#M775474</link>
      <description>Pramod, take a look at your routing tables. Run the command netstat -nr. Check out the "Interface" field.  Each entry in your routing table will use the specified interface to route outbound traffic. &lt;BR /&gt;&lt;BR /&gt;Tony</description>
      <pubDate>Mon, 04 Dec 2000 18:28:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/outbound-connection-through-floating-ip/m-p/2470185#M775474</guid>
      <dc:creator>Anthony deRito</dc:creator>
      <dc:date>2000-12-04T18:28:26Z</dc:date>
    </item>
    <item>
      <title>Re: Outbound connection through floating IP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/outbound-connection-through-floating-ip/m-p/2470186#M775475</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;There is an interesting discussion about this at:-&lt;BR /&gt;&lt;A href="http://docs.hp.com/hpux/onlinedocs/B3936-90026/B3936-90026.html" target="_blank"&gt;http://docs.hp.com/hpux/onlinedocs/B3936-90026/B3936-90026.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;The section that is significant is the following:-&lt;BR /&gt;&lt;BR /&gt;Call bind() before connect() &lt;BR /&gt;&lt;BR /&gt;When an application initiates its own connection, it should first call bind(2), specifying the application IP address before calling connect(2). Otherwise the connect request will be sent using the stationary IP address of the system's outbound LAN interface rather than the desired relocatable application IP address. The client will receive this IP address from the accept(2) call, possibly confusing the client software and preventing it from working correctly. &lt;BR /&gt;-----------------------------------------------&lt;BR /&gt;&lt;BR /&gt;Thus you must code your application to use the relocatable IP address if it is initiating connections.&lt;BR /&gt;&lt;BR /&gt;If you are need to force 'standard applications' (such as ftp for instance) to use the relocatable address then it seems that your only option is to ensure that the relocatable address is the only address on that interface (also discussed at the above URL).&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;John&lt;BR /&gt;</description>
      <pubDate>Tue, 05 Dec 2000 10:56:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/outbound-connection-through-floating-ip/m-p/2470186#M775475</guid>
      <dc:creator>John Palmer</dc:creator>
      <dc:date>2000-12-05T10:56:48Z</dc:date>
    </item>
    <item>
      <title>Re: Outbound connection through floating IP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/outbound-connection-through-floating-ip/m-p/2470187#M775476</link>
      <description>Hi, folks!&lt;BR /&gt;&lt;BR /&gt;Generally, the application should be configurable to bind() itself to a specific relocatable IP-address instead of binding to INADDR_ANY.&lt;BR /&gt;&lt;BR /&gt;Using 11.x You may use a static route to force outgoing traffic to be stamped with the 'right' source address...&lt;BR /&gt;&lt;BR /&gt;# route add &lt;DEST&gt; &lt;RELOC&gt; 0&lt;BR /&gt;&lt;BR /&gt;You could add such a route during pkg start and remove during halt. But be careful, not to disturb heartbeat traffic using this trick!&lt;BR /&gt;&lt;BR /&gt;Regards...&lt;BR /&gt; Dietmar.&lt;/RELOC&gt;&lt;/DEST&gt;</description>
      <pubDate>Tue, 05 Dec 2000 13:41:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/outbound-connection-through-floating-ip/m-p/2470187#M775476</guid>
      <dc:creator>Dietmar Konermann</dc:creator>
      <dc:date>2000-12-05T13:41:28Z</dc:date>
    </item>
    <item>
      <title>Re: Outbound connection through floating IP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/outbound-connection-through-floating-ip/m-p/2470188#M775477</link>
      <description>John:&lt;BR /&gt;&lt;BR /&gt;It?s a running application, which uses many third part API?s and where we don?t have any control on it.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 07 Dec 2000 21:25:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/outbound-connection-through-floating-ip/m-p/2470188#M775477</guid>
      <dc:creator>Pramod_4</dc:creator>
      <dc:date>2000-12-07T21:25:18Z</dc:date>
    </item>
  </channel>
</rss>

