console). Nothing in dmesg, but when I tried to ping the
wireless client, I got this:
ping: sendto: No buffer space available
ping: wrote 192.168.2.18 64 chars, ret=-1
Other traffic on the same server (using other interfaces) worked fine.
What can I do to more thoroughly investigate this, should
On Mon, Jul 21, 2008 at 10:53:23AM -0600, Daniel Melameth wrote:
On Mon, Jul 21, 2008 at 10:39 AM, Joe Warren-Meeks [EMAIL PROTECTED] wrote:
The default limit for number of states is quite low. Try adding the
following to pf.conf and running pfctl -vf /etc/pf.conf
set limit { states
Hi all,
I run OpenBSD 4.3 on my gateway. But when a machine behind the
NAT/gateway uses bittoreent (or gtk-gnutella) I loss packets.
For example when I try to do a ping www.google.com I can see ping:
sendto: No buffer space available (on my gateway)
It's the same if I use gtk-gnutella. I think
.
For example when I try to do a ping www.google.com I can see ping:
sendto: No buffer space available (on my gateway)
It's the same if I use gtk-gnutella. I think it's related to the huge
number of states (about 1500 for bittorent)
Any idea to the problem ?
Thanks for help.
Amaury De Ganseman
-gnutella) I loss packets.
For example when I try to do a ping www.google.com I can see ping:
sendto: No buffer space available (on my gateway)
It's the same if I use gtk-gnutella. I think it's related to the huge
number of states (about 1500 for bittorent)
Any idea to the problem ?
Thanks
On Mon, Jul 21, 2008 at 03:55:41PM +0200, Amaury De Ganseman wrote:
Hey there,
I run OpenBSD 4.3 on my gateway. But when a machine behind the
NAT/gateway uses bittoreent (or gtk-gnutella) I loss packets.
For example when I try to do a ping www.google.com I can see ping:
sendto: No buffer
On Mon, Jul 21, 2008 at 10:39 AM, Joe Warren-Meeks [EMAIL PROTECTED] wrote:
The default limit for number of states is quite low. Try adding the
following to pf.conf and running pfctl -vf /etc/pf.conf
set limit { states 5000, frags 5000, src-nodes 5000 }
You can up the values if they are
We have an OpenBSD 3.8 firewall that has been in production for the
last six months. Until the last week or two, everything has been
great. Recently while diagnosing a problem with the bonded T1 pair,
I noticed the following error while pinging the gateway:
ping: sendto: No buffer space
pinging the gateway:
ping: sendto: No buffer space available
This always coincided with a very high spike (1000-3000ms) in
latency, which would usually go back down to ~0ms and operate
normally. The interface in question is an Intel em connected to a
Cisco 2950 trunk. The other two interfaces
T1 pair,
I noticed the following error while pinging the gateway:
ping: sendto: No buffer space available
This always coincided with a very high spike (1000-3000ms) in
latency, which would usually go back down to ~0ms and operate
normally. The interface in question is an Intel em connected
.
[...]
ping: sendto: No buffer space available
ping: wrote 10.0.0.5 1032 chars, ret=-1
ping: sendto: No buffer space available
ping: wrote 10.0.0.5 1032 chars, ret=-1
ping: sendto: No buffer space available
ping: wrote 10.0.0.5 1032 chars, ret=-1
ping: sendto: No buffer space available
ping: wrote 10.0.0.5
11 matches
Mail list logo
