Klaus Weide <[EMAIL PROTECTED]> wrote:
> It gave the above response but then refused a connection to
> the port. It's also curious that the port number (,5,0) was
> always the same, in several attempts.
>
> I don't have time to check with the RFCs now, but obviously
> saying, in effect, "reach me at this number" when, in effect,
> you don't accept connections there can't be right.
OK, here's what's wrong. It correctly creates a socket, binds it to a system-
selected port, and does a listen() on it. I verified it with netstat(1).
However, for some reason the response returned on the control connection is
bogus. The IP address is correct as is the high octet of the port number, but
for some reason, the low octet of the port number is always 0. I looked at the
code and it looks OK, so this will require a more thorough investigation. I'll
do it sometime. In any case this has nothing to do with Lynx.
> Well, you might have a firewall or something that is to blame,
> rather than the software.
Oh no, I don't have any firewalls! I am an agent of the International Free
Computing Task Force, and firewalls are by definition an obstacle to Free
Computing that must be brought down. When I ordered my dedicated ARPA Internet
connection, I instructed my ISP very clearly to make my connection wide open
without any firewalls whatsoever.
--
Michael Sokolov Harhan Computer Operation Facility
Special Agent 615 N GOOD LATIMER EXPY #4
International Free Computing Task Force DALLAS TX 75204-5852 USA
Phone: +1-214-824-7693
ARPA TCP/SMTP: [EMAIL PROTECTED]
