<?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: Multihomed Blade Server as Dual Webserver in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/multihomed-blade-server-as-dual-webserver/m-p/4492287#M533508</link>
    <description>So what you're saying is there should be one blade for one website on port 80?</description>
    <pubDate>Sat, 05 Sep 2009 16:01:57 GMT</pubDate>
    <dc:creator>steve burk_1</dc:creator>
    <dc:date>2009-09-05T16:01:57Z</dc:date>
    <item>
      <title>Multihomed Blade Server as Dual Webserver</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/multihomed-blade-server-as-dual-webserver/m-p/4492285#M533506</link>
      <description>I have a standard blade with 2 nic's. I want to have one webserver use one nic and another webserver  use the other. One would go out through one firewall and the other through a different firewall. &lt;BR /&gt;Is there anything wrong with this configuration?</description>
      <pubDate>Fri, 04 Sep 2009 19:13:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/multihomed-blade-server-as-dual-webserver/m-p/4492285#M533506</guid>
      <dc:creator>steve burk_1</dc:creator>
      <dc:date>2009-09-04T19:13:46Z</dc:date>
    </item>
    <item>
      <title>Re: Multihomed Blade Server as Dual Webserver</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/multihomed-blade-server-as-dual-webserver/m-p/4492286#M533507</link>
      <description>Yes, there is at least one technical issue: by default, HP-UX network routing selects where to send a packet based on destination address only. &lt;BR /&gt;&lt;BR /&gt;When deciding where to send a packet, the HP-UX system reads the routing table from the beginning to the end. The first matching entry is used; other matching routes are considered only if the first one seems to be failing.&lt;BR /&gt;&lt;BR /&gt;If you set up two default gateways, only one of them (the top-most one in the routing table) will get used. Requests would be coming in through both firewalls, but all responses would be going through just one or the other: a standard case of asymmetric routing. If your firewalls are tracking TCP sessions, they most likely won't like this.&lt;BR /&gt;&lt;BR /&gt;With some advanced configuration, it may be possible to avoid this problem.&lt;BR /&gt;&lt;BR /&gt;Please read this document, particularily from page 10 to the end of the document:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://mayoxide.com/presentations/Understanding_hpux_routing.pdf" target="_blank"&gt;http://mayoxide.com/presentations/Understanding_hpux_routing.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;-----------&lt;BR /&gt;There is also a security/policy issue: the presence of two different firewalls would indicate that there are two security domains (basically, network segments with their own access control rules). &lt;BR /&gt;&lt;BR /&gt;The standard assumption would be that there is a valid reason for separating things into two security domains. Joining them together with a device that is not a firewall is bad enough, but your device is a web server, which tends to be a very prominent target for attacks by definition.&lt;BR /&gt;&lt;BR /&gt;You're giving the potential intruder a 2-for-1 deal: "choose the weaker firewall and you can bypass the stronger one". Most information security people would not be happy at all to find their security structures undermined like this.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Sat, 05 Sep 2009 08:47:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/multihomed-blade-server-as-dual-webserver/m-p/4492286#M533507</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2009-09-05T08:47:46Z</dc:date>
    </item>
    <item>
      <title>Re: Multihomed Blade Server as Dual Webserver</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/multihomed-blade-server-as-dual-webserver/m-p/4492287#M533508</link>
      <description>So what you're saying is there should be one blade for one website on port 80?</description>
      <pubDate>Sat, 05 Sep 2009 16:01:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/multihomed-blade-server-as-dual-webserver/m-p/4492287#M533508</guid>
      <dc:creator>steve burk_1</dc:creator>
      <dc:date>2009-09-05T16:01:57Z</dc:date>
    </item>
    <item>
      <title>Re: Multihomed Blade Server as Dual Webserver</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/multihomed-blade-server-as-dual-webserver/m-p/4492288#M533509</link>
      <description>to fix the routing problem could one do the following:&lt;BR /&gt;&lt;BR /&gt;route add host &lt;BEHIND firewall="" gateway="" address1=""&gt; &amp;lt; blade nic 1&amp;gt;&lt;BR /&gt;&lt;BR /&gt;route add host &lt;BEHIND firewall="" gateway="" address2=""&gt; &amp;lt; blade nic 2&amp;gt;&lt;BR /&gt;&lt;BR /&gt;What do you think??&lt;/BEHIND&gt;&lt;/BEHIND&gt;</description>
      <pubDate>Sat, 05 Sep 2009 19:15:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/multihomed-blade-server-as-dual-webserver/m-p/4492288#M533509</guid>
      <dc:creator>steve burk_1</dc:creator>
      <dc:date>2009-09-05T19:15:01Z</dc:date>
    </item>
    <item>
      <title>Re: Multihomed Blade Server as Dual Webserver</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/multihomed-blade-server-as-dual-webserver/m-p/4492289#M533510</link>
      <description>&amp;gt;route add host &lt;BEHIND firewall="" gateway="" address1=""&gt; &amp;lt; blade nic 1&amp;gt;&lt;BR /&gt;&lt;BR /&gt;&amp;gt;route add host &lt;BEHIND firewall="" gateway="" address2=""&gt; &amp;lt; blade nic 2&amp;gt;&lt;BR /&gt;&lt;BR /&gt;With settings like these, only gateway address1 will be used.&lt;BR /&gt;&lt;BR /&gt;Please, *read the document* I linked. It explains a lot better.&lt;BR /&gt;&lt;BR /&gt;MK&lt;/BEHIND&gt;&lt;/BEHIND&gt;</description>
      <pubDate>Sun, 06 Sep 2009 06:49:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/multihomed-blade-server-as-dual-webserver/m-p/4492289#M533510</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2009-09-06T06:49:26Z</dc:date>
    </item>
  </channel>
</rss>

