<?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: netstat vs netconf file ?? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/netstat-vs-netconf-file/m-p/4871943#M563558</link>
    <description>thanks</description>
    <pubDate>Tue, 23 Nov 2004 14:31:28 GMT</pubDate>
    <dc:creator>MikeL_4</dc:creator>
    <dc:date>2004-11-23T14:31:28Z</dc:date>
    <item>
      <title>netstat vs netconf file ??</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/netstat-vs-netconf-file/m-p/4871940#M563555</link>
      <description>Being somewhat confused to say the lease on network issues, how can I ensure that all static routes from a netstat -rn command are in the netconf file to ensure we don't loose anything after a reboot???&lt;BR /&gt;&lt;BR /&gt;netstat -rn example:&lt;BR /&gt;Routing tablesDestination           Gateway            Flags   Refs Interface  Pmtu127.0.0.1             127.0.0.1          UH        0  lo0        4136155.90.119.139        155.90.119.139     UH        0  lan1       4136192.168.229.139       192.168.229.139    UH        0  lan3       4136192.168.229.138       192.168.229.138    UH        0  lan3:1     4136155.90.35.139         155.90.35.139      UH        0  lan2:1     4136155.90.35.138         155.90.35.138      UH        0  lan2       4136192.168.223.139       192.168.223.139    UH        0  lan0       4136198.147.143.37        155.90.35.130      UGH       0  lan2:1        0165.79.232.18         155.90.35.139      UH        0  lan2:1        0172.17.101.142        155.90.35.130      UGH       0  lan2:1        0172.17.101.143        155.90.35.130      UGH       0  lan2:1        0192.168.223.128       192.168.223.139    U         2  lan0       1500192.168.229.128       192.168.229.139    U         3  lan3       1500192.168.229.128       192.168.229.138    U         3  lan3:1     1500155.90.119.128        155.90.119.139     U         2  lan1       1500155.90.35.128         155.90.35.138      U         3  lan2       1500155.90.35.128         155.90.35.139      U         3  lan2:1     1500155.90.0.0            155.90.119.130     UG        0  lan1          010.0.0.0              155.90.119.130     UG        0  lan1          0127.0.0.0             127.0.0.1          U         0  lo0           0default               155.90.119.130     UG        0  lan1          0</description>
      <pubDate>Tue, 23 Nov 2004 11:34:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/netstat-vs-netconf-file/m-p/4871940#M563555</guid>
      <dc:creator>MikeL_4</dc:creator>
      <dc:date>2004-11-23T11:34:01Z</dc:date>
    </item>
    <item>
      <title>Re: netstat vs netconf file ??</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/netstat-vs-netconf-file/m-p/4871941#M563556</link>
      <description>Manually compare the output of this command to the /etc/rc.config.d/netconf file.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;It should all tie back in directly.&lt;BR /&gt;&lt;BR /&gt;You need to understand the concept that if the ip address is 192.168.0.10 and the netmaks is 255.255.255.0 the network 192.168.0 &lt;BR /&gt;&lt;BR /&gt;Knowing this you can tie back all the entries in this output back to the netconf file.&lt;BR /&gt;&lt;BR /&gt;I know no way of automating this, its a sysadmin eyeball to screen task.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 23 Nov 2004 11:42:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/netstat-vs-netconf-file/m-p/4871941#M563556</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2004-11-23T11:42:26Z</dc:date>
    </item>
    <item>
      <title>Re: netstat vs netconf file ??</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/netstat-vs-netconf-file/m-p/4871942#M563557</link>
      <description>I believe the static routes are stored in /etc/rc.config.d/netconf.  This is very, very much a "look but don't touch" sort of file. The set_parms utility is the main update mechanism for this file.  You can cat or pg or more the file and see if the routes are there, and then confirm by adding another static route via the "route" command, verify the netstat -rn output and then look in the file to see if the new route is there.  We don't have static routes on our system, and I'm reluctant to play with something network oriented on a live box.&lt;BR /&gt;&lt;BR /&gt;Hope this helps,&lt;BR /&gt;mark</description>
      <pubDate>Tue, 23 Nov 2004 11:49:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/netstat-vs-netconf-file/m-p/4871942#M563557</guid>
      <dc:creator>Mark Greene_1</dc:creator>
      <dc:date>2004-11-23T11:49:26Z</dc:date>
    </item>
    <item>
      <title>Re: netstat vs netconf file ??</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/netstat-vs-netconf-file/m-p/4871943#M563558</link>
      <description>thanks</description>
      <pubDate>Tue, 23 Nov 2004 14:31:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/netstat-vs-netconf-file/m-p/4871943#M563558</guid>
      <dc:creator>MikeL_4</dc:creator>
      <dc:date>2004-11-23T14:31:28Z</dc:date>
    </item>
  </channel>
</rss>

