<?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 Gateway Issues in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/gateway-issues/m-p/3563954#M559865</link>
    <description>Hi All,&lt;BR /&gt;HPUX, 11.11, MC/SG&lt;BR /&gt;&lt;BR /&gt;I had this scenario, a certain IP address, 192.168.10.116 could be ftp'd to and it had a GW of 192.168.224.16, this gateway also for some reason (i inherited this environment) also is the MC/SG package IP. FTP worked with this GW.&lt;BR /&gt;The default gateway on this server is actually. 192.168.224.30.&lt;BR /&gt;&lt;BR /&gt;Now my network buddies went ahead and implemented a change to enable dynamic routing, with OSPF. after the change the ftp IP would not work until I changed its gateway from 192.168.224.16 to 192.168.224.30. This now works using this gateway.&lt;BR /&gt;&lt;BR /&gt;My question, why or what has made the old gateway not to work anymore and only after changing to 192.168.224.30 did it work?&lt;BR /&gt;&lt;BR /&gt;partial out put of netstat -rn before&lt;BR /&gt;&lt;BR /&gt;Destination     Gateway      Flags Refs Intf Pm&lt;BR /&gt;192.168.10.116 192.168.224.16 UGH   0   lan1 0&lt;BR /&gt;&lt;BR /&gt;After change&lt;BR /&gt;Destination     Gateway      Flags Refs Intf Pm&lt;BR /&gt;192.168.10.116 192.168.224.30 UGH   0   lan1 0&lt;BR /&gt;THANKS!&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 14 Jun 2005 11:37:36 GMT</pubDate>
    <dc:creator>Vic S. Kelan</dc:creator>
    <dc:date>2005-06-14T11:37:36Z</dc:date>
    <item>
      <title>Gateway Issues</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/gateway-issues/m-p/3563954#M559865</link>
      <description>Hi All,&lt;BR /&gt;HPUX, 11.11, MC/SG&lt;BR /&gt;&lt;BR /&gt;I had this scenario, a certain IP address, 192.168.10.116 could be ftp'd to and it had a GW of 192.168.224.16, this gateway also for some reason (i inherited this environment) also is the MC/SG package IP. FTP worked with this GW.&lt;BR /&gt;The default gateway on this server is actually. 192.168.224.30.&lt;BR /&gt;&lt;BR /&gt;Now my network buddies went ahead and implemented a change to enable dynamic routing, with OSPF. after the change the ftp IP would not work until I changed its gateway from 192.168.224.16 to 192.168.224.30. This now works using this gateway.&lt;BR /&gt;&lt;BR /&gt;My question, why or what has made the old gateway not to work anymore and only after changing to 192.168.224.30 did it work?&lt;BR /&gt;&lt;BR /&gt;partial out put of netstat -rn before&lt;BR /&gt;&lt;BR /&gt;Destination     Gateway      Flags Refs Intf Pm&lt;BR /&gt;192.168.10.116 192.168.224.16 UGH   0   lan1 0&lt;BR /&gt;&lt;BR /&gt;After change&lt;BR /&gt;Destination     Gateway      Flags Refs Intf Pm&lt;BR /&gt;192.168.10.116 192.168.224.30 UGH   0   lan1 0&lt;BR /&gt;THANKS!&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 14 Jun 2005 11:37:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/gateway-issues/m-p/3563954#M559865</guid>
      <dc:creator>Vic S. Kelan</dc:creator>
      <dc:date>2005-06-14T11:37:36Z</dc:date>
    </item>
    <item>
      <title>Re: Gateway Issues</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/gateway-issues/m-p/3563955#M559866</link>
      <description>ehm was I too vague. )-;</description>
      <pubDate>Tue, 14 Jun 2005 14:36:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/gateway-issues/m-p/3563955#M559866</guid>
      <dc:creator>Vic S. Kelan</dc:creator>
      <dc:date>2005-06-14T14:36:46Z</dc:date>
    </item>
    <item>
      <title>Re: Gateway Issues</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/gateway-issues/m-p/3563956#M559867</link>
      <description>Hi Vic,&lt;BR /&gt;&lt;BR /&gt;It's probably they way they "spanned" or subnetted your network.&lt;BR /&gt;Obviously it was already supernetted because you were in the .10 network &amp;amp; the GW was in the .224&lt;BR /&gt;So what probably happened is they "changed" the supernetting rules &amp;amp; that probably broke your subnet mask. When you moved your IP you probably "fixed" it by moving *back* within the supernet - as defined by your subnet mask.&lt;BR /&gt;But w/o more details that's just an educated guess.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Jeff</description>
      <pubDate>Tue, 14 Jun 2005 15:02:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/gateway-issues/m-p/3563956#M559867</guid>
      <dc:creator>Jeff Schussele</dc:creator>
      <dc:date>2005-06-14T15:02:44Z</dc:date>
    </item>
    <item>
      <title>Re: Gateway Issues</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/gateway-issues/m-p/3563957#M559868</link>
      <description>can u be more clear about the n/w setup ?</description>
      <pubDate>Wed, 15 Jun 2005 08:41:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/gateway-issues/m-p/3563957#M559868</guid>
      <dc:creator>Bejoy C Alias</dc:creator>
      <dc:date>2005-06-15T08:41:45Z</dc:date>
    </item>
  </channel>
</rss>

