<?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 Router/GW/ Conflict in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/router-gw-conflict/m-p/3261032#M569211</link>
    <description>j5000ws /hp-ux 11i&lt;BR /&gt;cable modem/linksys router/firewall &lt;BR /&gt;&lt;BR /&gt;I wanted to make sure that I could ping all IP's on my network. &lt;BR /&gt;#1 - I cannot ping my gw or my broadcast subnet, however I can ping the IP address that I assigned, other worksta on my network, &lt;A href="http://www.google.com" target="_blank"&gt;www.google.com&lt;/A&gt; and I can ping the IP that assigned to the unix box from another worksta. &lt;BR /&gt;In my DHCP client table I can see the assigned IP's  for all other worksta on the network, except the unix box. &lt;BR /&gt;I checked my routing tables (netstat -rn/-r ) and the default is setup correctly&lt;BR /&gt;I deleted the route and then added it back. &lt;BR /&gt;&lt;BR /&gt;The problem could be that I'm assigning a unique IP and not letting my DHCP server assign it. &lt;BR /&gt;&lt;BR /&gt;1st I would like to know what is the correct way for the unix machine to recognize the dynamic IP address from my DHCP server without hardcoding a unique IP. There are certain files that must stay in sync for me to boot. &lt;BR /&gt;When I let the DHCP server assign the IP there is a possibility that the IP in netconf could be different from the unique IP address in  /etc/hosts, this file is not updated after a reboot. If the following files are out of sync I cannot boot my system. &lt;BR /&gt;So I did the following:&lt;BR /&gt;&lt;BR /&gt; /etc/hosts  &lt;BR /&gt; assign a unique IP &lt;BR /&gt;  &lt;BR /&gt; /etc/rc.config/netconf &lt;BR /&gt; assign unique IP  &lt;BR /&gt; disable -DHCP_ENABLE=0&lt;BR /&gt;&lt;BR /&gt; etc/nsswitch.conf &lt;BR /&gt; host: files dsn&lt;BR /&gt;&lt;BR /&gt;This may also be a reason why I cannot ping my gw&lt;BR /&gt; &lt;BR /&gt;Thanks&lt;BR /&gt;Julian&lt;BR /&gt;</description>
    <pubDate>Tue, 27 Apr 2004 21:45:18 GMT</pubDate>
    <dc:creator>Julian Snype</dc:creator>
    <dc:date>2004-04-27T21:45:18Z</dc:date>
    <item>
      <title>Router/GW/ Conflict</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/router-gw-conflict/m-p/3261032#M569211</link>
      <description>j5000ws /hp-ux 11i&lt;BR /&gt;cable modem/linksys router/firewall &lt;BR /&gt;&lt;BR /&gt;I wanted to make sure that I could ping all IP's on my network. &lt;BR /&gt;#1 - I cannot ping my gw or my broadcast subnet, however I can ping the IP address that I assigned, other worksta on my network, &lt;A href="http://www.google.com" target="_blank"&gt;www.google.com&lt;/A&gt; and I can ping the IP that assigned to the unix box from another worksta. &lt;BR /&gt;In my DHCP client table I can see the assigned IP's  for all other worksta on the network, except the unix box. &lt;BR /&gt;I checked my routing tables (netstat -rn/-r ) and the default is setup correctly&lt;BR /&gt;I deleted the route and then added it back. &lt;BR /&gt;&lt;BR /&gt;The problem could be that I'm assigning a unique IP and not letting my DHCP server assign it. &lt;BR /&gt;&lt;BR /&gt;1st I would like to know what is the correct way for the unix machine to recognize the dynamic IP address from my DHCP server without hardcoding a unique IP. There are certain files that must stay in sync for me to boot. &lt;BR /&gt;When I let the DHCP server assign the IP there is a possibility that the IP in netconf could be different from the unique IP address in  /etc/hosts, this file is not updated after a reboot. If the following files are out of sync I cannot boot my system. &lt;BR /&gt;So I did the following:&lt;BR /&gt;&lt;BR /&gt; /etc/hosts  &lt;BR /&gt; assign a unique IP &lt;BR /&gt;  &lt;BR /&gt; /etc/rc.config/netconf &lt;BR /&gt; assign unique IP  &lt;BR /&gt; disable -DHCP_ENABLE=0&lt;BR /&gt;&lt;BR /&gt; etc/nsswitch.conf &lt;BR /&gt; host: files dsn&lt;BR /&gt;&lt;BR /&gt;This may also be a reason why I cannot ping my gw&lt;BR /&gt; &lt;BR /&gt;Thanks&lt;BR /&gt;Julian&lt;BR /&gt;</description>
      <pubDate>Tue, 27 Apr 2004 21:45:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/router-gw-conflict/m-p/3261032#M569211</guid>
      <dc:creator>Julian Snype</dc:creator>
      <dc:date>2004-04-27T21:45:18Z</dc:date>
    </item>
    <item>
      <title>Re: Router/GW/ Conflict</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/router-gw-conflict/m-p/3261033#M569212</link>
      <description>Something to check:&lt;BR /&gt;&lt;BR /&gt;subnet compatiability. For the ping to work, you may need to make sure the hp box is on the same network and subnet as the router.&lt;BR /&gt;&lt;BR /&gt;These problems are commonly caused by inconsistencies in network, broadcast address parameters on one machine.&lt;BR /&gt;&lt;BR /&gt;For hpux, check /etc/rc.config.d/netconf&lt;BR /&gt;&lt;BR /&gt;also check ifconfig for all the lan cards.&lt;BR /&gt;&lt;BR /&gt;Do note that hpux does not support two nic cards on the same network. period.&lt;BR /&gt;&lt;BR /&gt;Also, because of recent ping attack viruses, your router may be configured to ignore pings. That should definitely be done to preven outsiders from discovering and attempting to sniff your network.&lt;BR /&gt;&lt;BR /&gt;Does nslookup work?&lt;BR /&gt;&lt;BR /&gt;If nslookup and the internet work, you don't need ping for an 11i box to work.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 27 Apr 2004 22:02:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/router-gw-conflict/m-p/3261033#M569212</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2004-04-27T22:02:19Z</dc:date>
    </item>
    <item>
      <title>Re: Router/GW/ Conflict</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/router-gw-conflict/m-p/3261034#M569213</link>
      <description>If the Linksys is providing the DHCP service then you can simply tell it to use a higher DCHP IP starting address to make room for static addresses at the low end of the range.  Normally the router grabs 192.168.1.1 and DHCP service starts at 192.168.1.2 (Starting IP address) and runs up through Starting IP Address + Number of DHCP Users.  If you want to reserve some addresses for static address use, simply change the Starting IP address to 192.168.1.25 and then you can use the addresses from 192.168.1.2-192.168.1.24 for static addresses.  You can also reduce the Number of DHCP users and then it will leave space at the high end.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="ftp://ftp.linksys.com/pdf/befsr11_befsr41ug.pdf" target="_blank"&gt;ftp://ftp.linksys.com/pdf/befsr11_befsr41ug.pdf&lt;/A&gt;  page 57 (PDF page 32of66)&lt;BR /&gt;&lt;BR /&gt;Just make sure you use a mask of 255.255.255.0 and a default gateway of 192.168.1.1.&lt;BR /&gt;&lt;BR /&gt;If the default gateway is the linksys and it will not respond to pings you may run into problems with dead gateway detection.  The HP likes to consider a gateway dead if it doesn't respond to pings.  You can check with:&lt;BR /&gt;&lt;BR /&gt;ndd -get /dev/ip ip_ire_gw_probe&lt;BR /&gt;&lt;BR /&gt;if it comes back with 0 then it is turned off and it won't bother you.  If it is on you can fix it for good with an edit to /etc/rc.config.d/nddconf&lt;BR /&gt;&lt;BR /&gt;TRANSPORT_NAME:=icmp&lt;BR /&gt;NDD_NAME:=ip_ire_gw_probe&lt;BR /&gt;NDD_VALUE:=0&lt;BR /&gt;&lt;BR /&gt;which will take effect after a reboot.  You can get around the reboot by&lt;BR /&gt;&lt;BR /&gt;ndd -set /dev/ip ip_ire_gw_probe 0&lt;BR /&gt;&lt;BR /&gt;then use route to delete and readd the default gateway.&lt;BR /&gt;&lt;BR /&gt;The Linksys also has an option to turn off pings.  It says it keeps it from responding to pings from the outside but it may also kill off the inside pings.&lt;BR /&gt;Think it is called Block Anonymous Internet Requests and is under Block WAN Requests under Security.&lt;BR /&gt;&lt;BR /&gt;Ron&lt;BR /&gt;</description>
      <pubDate>Wed, 28 Apr 2004 14:43:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/router-gw-conflict/m-p/3261034#M569213</guid>
      <dc:creator>Ron Kinner</dc:creator>
      <dc:date>2004-04-28T14:43:42Z</dc:date>
    </item>
    <item>
      <title>Re: Router/GW/ Conflict</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/router-gw-conflict/m-p/3261035#M569214</link>
      <description>Ron, &lt;BR /&gt;&lt;BR /&gt;Thanks for the info. &lt;BR /&gt;Your synopsis of configuring the Linksys DHCP service was somewhat similar as to how I configured mine. Thanks this confirmed that my configuration was ok.the way it is setup. &lt;BR /&gt;I previously checked NDD and edited nddconf and added those NDD optioins. &lt;BR /&gt;The gw was ok. &lt;BR /&gt;&lt;BR /&gt;There was one bit of info that you mentioned that was a very big help. I enable my WAN and pinged my gw and broadcast subnet successfully. enable it after a successfully ping.&lt;BR /&gt;My Gw/router is configured correctly. This put my mind to rest. Thanks a lot for the documentation this was also a big help.  &lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Julian</description>
      <pubDate>Wed, 28 Apr 2004 17:31:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/router-gw-conflict/m-p/3261035#M569214</guid>
      <dc:creator>Julian Snype</dc:creator>
      <dc:date>2004-04-28T17:31:42Z</dc:date>
    </item>
  </channel>
</rss>

