<?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: Equivalen to SO_BSDCOMPAT in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/equivalen-to-so-bsdcompat/m-p/3638493#M85266</link>
    <description>If the target machine discards the message because there is no process reading on the requested port number, it sends an ICMP message to your machine which will cause the next system call on the socket to return&lt;BR /&gt;  ECONNREFUSED.  Since delivery of ICMP messages is not guarenteed you may not recieve this notification on the first transaction.&lt;BR /&gt;&lt;BR /&gt;  Remember that your socket must "connected" in order to receive the ICMP errors.  Also verify that Linux will return on "unconnected" sockets.  This may cause porting problems if your application isn't ready for it, so Alan tells me they've added a SO_BSDCOMPAT flag which can be set for Linux kernels after 2.x&lt;BR /&gt;</description>
    <pubDate>Thu, 29 Sep 2005 23:34:23 GMT</pubDate>
    <dc:creator>Mugilvannan</dc:creator>
    <dc:date>2005-09-29T23:34:23Z</dc:date>
    <item>
      <title>Equivalen to SO_BSDCOMPAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/equivalen-to-so-bsdcompat/m-p/3638492#M85265</link>
      <description>SO_BSDCOMPAT is obsolete since the 2.4 kernels and now 2.5 and later&lt;BR /&gt;kernels log a warning every time it is used.&lt;BR /&gt;&lt;BR /&gt;Is there some thing equivalent to SO_BSDCOMPAT that can be used to in order to make sure that "ICMP errors recieved for a UDP socket will  not be passed"</description>
      <pubDate>Thu, 29 Sep 2005 14:18:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/equivalen-to-so-bsdcompat/m-p/3638492#M85265</guid>
      <dc:creator>Srinivas Krishnappa Sha</dc:creator>
      <dc:date>2005-09-29T14:18:08Z</dc:date>
    </item>
    <item>
      <title>Re: Equivalen to SO_BSDCOMPAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/equivalen-to-so-bsdcompat/m-p/3638493#M85266</link>
      <description>If the target machine discards the message because there is no process reading on the requested port number, it sends an ICMP message to your machine which will cause the next system call on the socket to return&lt;BR /&gt;  ECONNREFUSED.  Since delivery of ICMP messages is not guarenteed you may not recieve this notification on the first transaction.&lt;BR /&gt;&lt;BR /&gt;  Remember that your socket must "connected" in order to receive the ICMP errors.  Also verify that Linux will return on "unconnected" sockets.  This may cause porting problems if your application isn't ready for it, so Alan tells me they've added a SO_BSDCOMPAT flag which can be set for Linux kernels after 2.x&lt;BR /&gt;</description>
      <pubDate>Thu, 29 Sep 2005 23:34:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/equivalen-to-so-bsdcompat/m-p/3638493#M85266</guid>
      <dc:creator>Mugilvannan</dc:creator>
      <dc:date>2005-09-29T23:34:23Z</dc:date>
    </item>
  </channel>
</rss>

