-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Len Conrad mentioned the following,
|
[ snip ]
|>> Suggestions with how to proceed debugging, please.
|>>
|>> I'm trying to get the dmesg.boot for the 4.7 and 4.10 boxes now, sorry.
Do you have a problem with the resolver libraries on your new install?
Mike Silbersack wrote:
>
> FWIW, when doing some benchmarking of apache vs thttpd a long while ago, I
> found results similar to Lars. When I used one program for benchmarking,
> the TIME_WAIT sockets would build up on the client side. When I used
> another program, the TIME_WAIT sockets built u
On Tue, 11 Jan 2005, Lars Erik Gullerud wrote:
You didn't mention what MTA you are using, so I don't know if this is a
similar (application-level) issue, or if it's FreeBSD 4.10 that causes some
additional delay before initiating a TCP CLOSE, but either way, this might be
the behaviour you are o
We have a windows mailserver that relays its outbound to a fbsd
gateway. We changed to a different fbsd gateway running 4.10. Windows
then began having trouble sending to 4.10. Windows "netstat -an"
shows dozens of lines like this:
source IP desitination IP
On Mon, 10 Jan 2005, Len Conrad wrote:
We have a windows mailserver that relays its outbound to a fbsd gateway. We
changed to a different fbsd gateway running 4.10. Windows then began having
trouble sending to 4.10. Windows "netstat -an" shows dozens of lines like
this:
source IP
On 2005-01-10 11:26, Len Conrad <[EMAIL PROTECTED]> wrote:
>> Just off the top of my head...
>>
>> You mentioned the freebsd machine is the gateway. Do you have a
>> firewall on the host blocking connections from the windows machine?
>
> a forgotten detail is that the windows machine sends just fi
Just off the top of my head...
You mentioned the freebsd machine is the gateway. Do you have a firewall
on the host blocking connections from the windows machine?
a forgotten detail is that the windows machine sends just fine to the 4.10
gateway for a few minutes, but the time_wait inevitably b
On Mon, 10 Jan 2005, Len Conrad wrote:
We have a windows mailserver that relays its outbound to a fbsd gateway. We
changed to a different fbsd gateway running 4.10. Windows then began having
trouble sending to 4.10. Windows "netstat -an" shows dozens of lines like
this:
source IP
On Mon, 10 Jan 2005 10:53:39 -0600, Len Conrad <[EMAIL PROTECTED]> wrote:
>
> We have a windows mailserver that relays its outbound to a fbsd
> gateway. We changed to a different fbsd gateway running 4.10. Windows then
> began having trouble sending to 4.10. Windows "netstat -an" shows dozens
>
