Mikhail Teterin wrote:
Hello!
I just noticed, that on my recent "6.1-STABLE #4: Thu Jun 8" amd64 system
attempts to connect to a bogus port (like ) hang instead of failing
with "Connection refused" immediately, as they on other systems.
Using sysctl net.inet.tcp.blackhole=1 ?
--
Pawel
_
On 6/27/06, Mikhail Teterin <[EMAIL PROTECTED]> wrote:
Hello!
I just noticed, that on my recent "6.1-STABLE #4: Thu Jun 8" amd64 system
attempts to connect to a bogus port (like ) hang instead of failing
with "Connection refused" immediately, as they on other systems.
My first thought is
вівторок 27 червень 2006 15:05, Pawel Worach написав:
> > I just noticed, that on my recent "6.1-STABLE #4: Thu Jun 8" amd64
> > system attempts to connect to a bogus port (like ) hang instead of
> > failing with "Connection refused" immediately, as they on other systems.
>
> Using sysctl net.
вівторок 27 червень 2006 15:07, Andrew Pantyukhin написав:
> My first thought is net.inet.tcp.blackhole sysctl.
Yep, set to 2... I wonder, who did this here and why -- the machine is on the
LAN behind firewalls... One of the TCL's http tests is failing because of
this.
Thanks a lot, Andrew and
Hello!
I just noticed, that on my recent "6.1-STABLE #4: Thu Jun 8" amd64 system
attempts to connect to a bogus port (like ) hang instead of failing
with "Connection refused" immediately, as they on other systems.
Why would this be? There is nothing listening: ``netstat -n | grep '' is
e
