On Fri, 15 Jun 2001 [EMAIL PROTECTED] wrote:
>
> > You can fix this by upping the socket buffer that ping asks for (look
> > for setsockopt( ... SO_RCVBUF ...)) and then tuning the kernel to
> > allow larger socket buffers. The file to fiddle with is
> > /proc/sys/net/core/rmem_max.
>
>
> You can fix this by upping the socket buffer that ping asks for (look
> for setsockopt( ... SO_RCVBUF ...)) and then tuning the kernel to
> allow larger socket buffers. The file to fiddle with is
> /proc/sys/net/core/rmem_max.
Currently it is set to 65535. I doubled it several times and
[EMAIL PROTECTED] wrote:
> ...
> 2. A "ping -f -s 64589" to a machine running kernel 2.2.19 results in 0%
> packet loss. By incrementing the packetsize by one "ping -f -s 64590" or
> higher, I consistently see 80% packet loss. ifconfig on the receiving
> machine shows no anomolies.
> ...
> 4.
José Luis Domingo López wrote:
>
> On Thursday, 14 June 2001, at 14:17:11 -0700,
> [EMAIL PROTECTED] wrote:
>
> >
> > 1. When pinging a machine using kernel 2.2.19 I consistently get an 80%
> > packet loss when doing a ping -f with a packet size of 64590 or higher.
> >
> What happens here is
[EMAIL PROTECTED] wrote:
...
2. A ping -f -s 64589 to a machine running kernel 2.2.19 results in 0%
packet loss. By incrementing the packetsize by one ping -f -s 64590 or
higher, I consistently see 80% packet loss. ifconfig on the receiving
machine shows no anomolies.
...
4. Linux version
José Luis Domingo López wrote:
On Thursday, 14 June 2001, at 14:17:11 -0700,
[EMAIL PROTECTED] wrote:
1. When pinging a machine using kernel 2.2.19 I consistently get an 80%
packet loss when doing a ping -f with a packet size of 64590 or higher.
What happens here is (under kernel
You can fix this by upping the socket buffer that ping asks for (look
for setsockopt( ... SO_RCVBUF ...)) and then tuning the kernel to
allow larger socket buffers. The file to fiddle with is
/proc/sys/net/core/rmem_max.
Currently it is set to 65535. I doubled it several times and each
On Fri, 15 Jun 2001 [EMAIL PROTECTED] wrote:
You can fix this by upping the socket buffer that ping asks for (look
for setsockopt( ... SO_RCVBUF ...)) and then tuning the kernel to
allow larger socket buffers. The file to fiddle with is
/proc/sys/net/core/rmem_max.
Currently it is
Odds are it's a raw socket receive buffer issue. Stock pings only ask for
a ~96k socket buffer, which means that they can only hold one ~64k packet
at a time. So, if you're ever slow grabbing packets out of the buffer,
you're going to drop traffic.
You can fix this by upping the socket buffer
On Thursday, 14 June 2001, at 14:17:11 -0700,
[EMAIL PROTECTED] wrote:
>
> 1. When pinging a machine using kernel 2.2.19 I consistently get an 80%
> packet loss when doing a ping -f with a packet size of 64590 or higher.
>
What happens here is (under kernel 2.2.19):
ping -f -s 49092 localhost
1. When pinging a machine using kernel 2.2.19 I consistently get an 80%
packet loss when doing a ping -f with a packet size of 64590 or higher.
2. A "ping -f -s 64589" to a machine running kernel 2.2.19 results in 0%
packet loss. By incrementing the packetsize by one "ping -f -s 64590" or
1. When pinging a machine using kernel 2.2.19 I consistently get an 80%
packet loss when doing a ping -f with a packet size of 64590 or higher.
2. A ping -f -s 64589 to a machine running kernel 2.2.19 results in 0%
packet loss. By incrementing the packetsize by one ping -f -s 64590 or
higher,
On Thursday, 14 June 2001, at 14:17:11 -0700,
[EMAIL PROTECTED] wrote:
1. When pinging a machine using kernel 2.2.19 I consistently get an 80%
packet loss when doing a ping -f with a packet size of 64590 or higher.
What happens here is (under kernel 2.2.19):
ping -f -s 49092 localhost --
Odds are it's a raw socket receive buffer issue. Stock pings only ask for
a ~96k socket buffer, which means that they can only hold one ~64k packet
at a time. So, if you're ever slow grabbing packets out of the buffer,
you're going to drop traffic.
You can fix this by upping the socket buffer
14 matches
Mail list logo
