<?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: How to stop loopback address from listening on TCp ports in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/how-to-stop-loopback-address-from-listening-on-tcp-ports/m-p/4973601#M83802</link>
    <description>Using a verbose strace against the application while it is _starting_ (not after it is already running), you should be able to see the calls it is making to setup the listen endpoint.  In particular, you should see it making a call to bind().  Going back in the strace you may see it making the system calls typical of a gethostbyname/getaddrinfo call, and then prior to that, perhaps opening a config file from which it has gotten the name/IP to which it will bind.&lt;BR /&gt;</description>
    <pubDate>Fri, 14 Apr 2006 11:44:02 GMT</pubDate>
    <dc:creator>rick jones</dc:creator>
    <dc:date>2006-04-14T11:44:02Z</dc:date>
    <item>
      <title>How to stop loopback address from listening on TCp ports</title>
      <link>https://community.hpe.com/t5/operating-system-linux/how-to-stop-loopback-address-from-listening-on-tcp-ports/m-p/4973599#M83800</link>
      <description>We have an application running on Linux box.It should listen on IP Address:2471 port , but &lt;BR /&gt;its listening on Loopback address rather.How can i make the eth0 listen in place of loopback address.Thanks for all your advices.&lt;BR /&gt;&lt;BR /&gt;p_ctsce 1348 ctsa    3u  IPv4 107357401            TCP 127.0.0.1:ctsa_in_ctsa (LISTEN)&lt;BR /&gt;</description>
      <pubDate>Thu, 13 Apr 2006 09:05:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/how-to-stop-loopback-address-from-listening-on-tcp-ports/m-p/4973599#M83800</guid>
      <dc:creator>Manoj_36</dc:creator>
      <dc:date>2006-04-13T09:05:27Z</dc:date>
    </item>
    <item>
      <title>Re: How to stop loopback address from listening on TCp ports</title>
      <link>https://community.hpe.com/t5/operating-system-linux/how-to-stop-loopback-address-from-listening-on-tcp-ports/m-p/4973600#M83801</link>
      <description>You should ask to your application provider or developer. Without knowing the application is hard to say. Most network services, like SSH, DNS, SAMBA, HTTP, FTP have a configuration file where you can specify on which interfaces will listen.</description>
      <pubDate>Thu, 13 Apr 2006 11:10:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/how-to-stop-loopback-address-from-listening-on-tcp-ports/m-p/4973600#M83801</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2006-04-13T11:10:45Z</dc:date>
    </item>
    <item>
      <title>Re: How to stop loopback address from listening on TCp ports</title>
      <link>https://community.hpe.com/t5/operating-system-linux/how-to-stop-loopback-address-from-listening-on-tcp-ports/m-p/4973601#M83802</link>
      <description>Using a verbose strace against the application while it is _starting_ (not after it is already running), you should be able to see the calls it is making to setup the listen endpoint.  In particular, you should see it making a call to bind().  Going back in the strace you may see it making the system calls typical of a gethostbyname/getaddrinfo call, and then prior to that, perhaps opening a config file from which it has gotten the name/IP to which it will bind.&lt;BR /&gt;</description>
      <pubDate>Fri, 14 Apr 2006 11:44:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/how-to-stop-loopback-address-from-listening-on-tcp-ports/m-p/4973601#M83802</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2006-04-14T11:44:02Z</dc:date>
    </item>
    <item>
      <title>Re: How to stop loopback address from listening on TCp ports</title>
      <link>https://community.hpe.com/t5/operating-system-linux/how-to-stop-loopback-address-from-listening-on-tcp-ports/m-p/4973602#M83803</link>
      <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;Thanks for all ur response I will do some more digging and update.Though I am still lost.</description>
      <pubDate>Mon, 17 Apr 2006 05:19:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/how-to-stop-loopback-address-from-listening-on-tcp-ports/m-p/4973602#M83803</guid>
      <dc:creator>Manoj_36</dc:creator>
      <dc:date>2006-04-17T05:19:49Z</dc:date>
    </item>
    <item>
      <title>Re: How to stop loopback address from listening on TCp ports</title>
      <link>https://community.hpe.com/t5/operating-system-linux/how-to-stop-loopback-address-from-listening-on-tcp-ports/m-p/4973603#M83804</link>
      <description>It appears you may be running SeaODBC from&lt;BR /&gt;a quick scan of the net.  It is likely&lt;BR /&gt;that such a tool would install listening&lt;BR /&gt;on localhost only.  Otherwise, your databases&lt;BR /&gt;are exposed to the world.&lt;BR /&gt;&lt;BR /&gt;Check the man page for the tool to see if&lt;BR /&gt;they specify the configuration file. &lt;BR /&gt;Likely something like /etc/seaodbc.&lt;BR /&gt;The configuration file may have a line for&lt;BR /&gt;either interfaces (lo) or listen address &lt;BR /&gt;(127.0.0.1).&lt;BR /&gt;&lt;BR /&gt;Consider the above security issue before&lt;BR /&gt;changing the listen address or interface.&lt;BR /&gt;&lt;BR /&gt;Check to see if the daemon supports&lt;BR /&gt;tcpwrappers.  This can be used to secure&lt;BR /&gt;the port.&lt;BR /&gt;&lt;BR /&gt;Alternatively, you can uses SSH port&lt;BR /&gt;forwarding to forward local traffic on &lt;BR /&gt;port 2471 to the sever with the daemon.</description>
      <pubDate>Tue, 18 Apr 2006 14:24:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/how-to-stop-loopback-address-from-listening-on-tcp-ports/m-p/4973603#M83804</guid>
      <dc:creator>Bill Thorsteinson</dc:creator>
      <dc:date>2006-04-18T14:24:47Z</dc:date>
    </item>
    <item>
      <title>Re: How to stop loopback address from listening on TCp ports</title>
      <link>https://community.hpe.com/t5/operating-system-linux/how-to-stop-loopback-address-from-listening-on-tcp-ports/m-p/4973604#M83805</link>
      <description>OK the solutiion is that &lt;BR /&gt;/etc/hosts was missing the entry for server resolution &lt;BR /&gt;&lt;BR /&gt;it was having only &lt;BR /&gt;127.0.0.1 &lt;SERVER-NAME&gt;&lt;BR /&gt;changed that to &lt;BR /&gt;127.0.0.1  localhost loopback&lt;BR /&gt;&lt;BR /&gt;and added&lt;BR /&gt;&lt;BR /&gt;&lt;SERVER ip=""&gt;  &lt;SERVER fqdn=""&gt;   &lt;ALIASES&gt;&lt;BR /&gt;&lt;BR /&gt;That was all&lt;/ALIASES&gt;&lt;/SERVER&gt;&lt;/SERVER&gt;&lt;/SERVER-NAME&gt;</description>
      <pubDate>Fri, 28 Apr 2006 01:54:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/how-to-stop-loopback-address-from-listening-on-tcp-ports/m-p/4973604#M83805</guid>
      <dc:creator>Manoj_36</dc:creator>
      <dc:date>2006-04-28T01:54:42Z</dc:date>
    </item>
    <item>
      <title>Re: How to stop loopback address from listening on TCp ports</title>
      <link>https://community.hpe.com/t5/operating-system-linux/how-to-stop-loopback-address-from-listening-on-tcp-ports/m-p/4973605#M83806</link>
      <description>Solution given in last messg</description>
      <pubDate>Fri, 28 Apr 2006 01:55:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/how-to-stop-loopback-address-from-listening-on-tcp-ports/m-p/4973605#M83806</guid>
      <dc:creator>Manoj_36</dc:creator>
      <dc:date>2006-04-28T01:55:29Z</dc:date>
    </item>
  </channel>
</rss>

