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 this
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 {
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
:
> 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)
The default limit for number of states is quite low. Try adding the
following to pf.conf and running pfctl
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 it's
la) 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)
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-gn
I'm seeing some sendto: No buffer space available errors along with some ssh
session hangs. The symptoms are intermitent and look a lot like this
thread.
http://monkey.org/openbsd/archive/misc/0309/msg00827.html
The system is 4.1 stable generic with the sangoma wanpipe driver. Most
traff
On Mon, Mar 19, 2007 at 01:40:02PM +0100, Walter Doerr wrote:
> Hello,
>
> I am using an OpenBSD 4.0 box connected to a 2Mbit SDSL line in
> Germany (using user space PPP).
>
> When pinging a host across the SDSL line, I get an occasional
> "sendto: No buffer space av
Hello,
I am using an OpenBSD 4.0 box connected to a 2Mbit SDSL line in
Germany (using user space PPP).
When pinging a host across the SDSL line, I get an occasional
"sendto: No buffer space available" message:
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=566 ttl=254 time=62.674 ms
64
2007/3/15, Claudio Jeker <[EMAIL PROTECTED]>:
I think I mentionened this already a few times but I'll do it again.
"sendto: No buffer space available" means an ENOBUF error was returned.
On modern systems ENOBUF is almost only generated by the interfaces and
their queues
On Thu, Mar 15, 2007 at 05:42:48PM +0100, Walter Doerr wrote:
> Hello,
>
> I am using an OpenBSD 4.0 box connected to a 2Mbit SDSL line in
> Germany (using user space PPP).
>
> When pinging a host across the SDSL line, I get an occasional
> "sendto: No buffer space avai
Hello,
I am using an OpenBSD 4.0 box connected to a 2Mbit SDSL line in
Germany (using user space PPP).
When pinging a host across the SDSL line, I get an occasional
"sendto: No buffer space available" message:
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=566 ttl=254 time=62.674 ms
64
th the bonded 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 connecte
d 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
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
ime -> wow.
[...]
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: w
17 matches
Mail list logo
