[erlang-bugs] : Follow up: [BUG] gen_tcp:connect/3, 4 returns socket for closed port

[Edwin Fine]

Raimo,

Yes, it must be a port that is open in the firewall but have no listening
socket.
I have not tried it on other targets (I only have Windows and Linux, and I
tried connecting from Linux to Windows XP).

Hope this helps.

On Tue, Sep 9, 2008 at 3:12 AM, Raimo Niskanen <
raimo+erlang-bugs@REDACTED <raimo%2Berlang-bugs@REDACTED>>wrote:

> On Mon, Sep 08, 2008 at 08:43:22AM -0400, Edwin Fine wrote:
> > Raimo,
> >
> > Thanks for the response. Good luck finding the bug. I just confirmed that
> it
> > is still present on R12B-4. Please note that you need to connect to a
> port
> > that is open but with no program using it (e.g. one could try port 80
> > without httpd running). Sorry to state the obvious, it's a bad habit of
> > mine.
>
> Nono, please state the obvious. People often leave out the
> obvious, that they think. And it turns out to be non-obvous.
>
> But on the other hand it may be confusing too. Do you mean
> that it must be a port that is open in the firewall
> but have no listening socket so you get the RST response
> from the TCP stack on the target machine (that is supposed
> to be Windows XP.  Have you tried other targets? Since you
> report having seen SYN in RST out on the target for all
> connection attempts it should not matter).
>
> >
> > Regards,
> > Edwin Fine
> >
> > On Mon, Sep 8, 2008 at 6:00 AM, Raimo Niskanen <
> > raimo+erlang-bugs@REDACTED<raimo%2Berlang-bugs@REDACTED><
> raimo%2Berlang-bugs@REDACTED<raimo%252Berlang-bugs@REDACTED>
> >>wrote:
> >
> > > On Sun, Sep 07, 2008 at 03:23:21PM -0400, Edwin Fine wrote:
> > > > Hi OTP Team,
> > > >
> > > > I realize you have been very busy with the R12B-4 release, and this
> is
> > > not a
> > > > complaint or criticism, just a request for info.
> > >
> > > Perhaps it should be...
> > >
> > > >
> > > > I reported this bug some weeks ago and have not received an
> > > acknowledgment.
> > > > I simply want to know if you accepted it, rejected it, or fixed it
> > > already
> > >
> > > You are right, we have been busy with the release.
> > >
> > > Your problem (as we say in swedish) fell between the chairs.
> > > If it is an inet_drv bug it is one guys problem, an SMP bug
> > > another guys problem. But enough excuses...
> > > we will look into it now. It sounds serious.
> > >
> > > > (and if so, in which release the fix appears). I have had to code
> around
> > > > this and would like to know if I can remove that code.
> > > >
> > > > Link to original bug report:
> > > > http://www.erlang.org/pipermail/erlang-bugs/2008-August/000931.html
> > > >
> > > > Best regards,
> > > > Edwin Fine
> > >
> > > > _______________________________________________
> > > > erlang-bugs mailing list
> > > > erlang-bugs@REDACTED
> > > > http://www.erlang.org/mailman/listinfo/erlang-bugs
> > >
> > > --
> > >
> > > / Raimo Niskanen, Erlang/OTP, Ericsson AB
> > >
> > >
>
> > _______________________________________________
> > erlang-bugs mailing list
> > erlang-bugs@REDACTED
> > http://www.erlang.org/mailman/listinfo/erlang-bugs
>
> --
>
> / Raimo Niskanen, Erlang/OTP, Ericsson AB
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-bugs/attachments/20080909/c621d220/attachment.htm>