On Thu, Oct 3, 2013 at 11:42 AM, Tugrul Erdogan
wrote:
> Hi,
>
> I am using FreeBSD alpha2 amd64 on my router and after packet loaded test
> attack I am taking
> "ping: sendto: No buffer space available" error when running ping from
> router to victim directoio
Hi,
I am using FreeBSD alpha2 amd64 on my router and after packet loaded test
attack I am taking
"ping: sendto: No buffer space available" error when running ping from
router to victim directoion. The nic is "Intel 82599EB". Whenever this
problem began to show, I can track the
On 9/28/12 11:02 PM, Hooman Fazaeli wrote:
On 9/27/2012 9:38 PM, Rudy wrote:
On 09/27/2012 11:00 AM, Rudy wrote:
Rebooting and/or the settings change seems to have stopped the errors.
Here is a pretty little graph showing error rate on em1 for the past 3
days.
http://www.monkeybrains.net/i
On 9/27/2012 9:38 PM, Rudy wrote:
On 09/27/2012 11:00 AM, Rudy wrote:
Rebooting and/or the settings change seems to have stopped the errors.
Here is a pretty little graph showing error rate on em1 for the past 3
days.
http://www.monkeybrains.net/images/ErrorRate-em1.png
Interesting... if
On 09/27/2012 11:00 AM, Rudy wrote:
Rebooting and/or the settings change seems to have stopped the errors.
Here is a pretty little graph showing error rate on em1 for the past 3
days.
http://www.monkeybrains.net/images/ErrorRate-em1.png
Interesting... if I zoom in on the graph, I see the er
On 09/27/2012 11:00 AM, Rudy wrote:
On 09/25/2012 01:37 AM, Hooman Fazaeli wrote:
dev.em.1.link_irq: 6379725883
dev.em.2.link_irq: 6379294926
Based on the strangely high value of dev.em.1.link_irq (which means too
many link
status changes: down -> up -> down -> ), I guess the problem
On 09/25/2012 01:37 AM, Hooman Fazaeli wrote:
dev.em.1.link_irq: 6379725883
dev.em.2.link_irq: 6379294926
Based on the strangely high value of dev.em.1.link_irq (which means too
many link
status changes: down -> up -> down -> ), I guess the problem is the
same as
discussed in these th
On 9/25/2012 11:08 AM, Rudy (bulk) wrote:
On 9/24/12 11:52 PM, Hooman Fazaeli wrote:
sysctl dev.em.1
From the side having the 'No buffer space available' (FreeBSD 8.3 Sep 13 2012)
# sysctl dev.em.1
dev.em.1.%desc: Intel(R) PRO/1000 Network Connection 7.3.2
dev.em.1.%driver: em
dev.em.1.%lo
On 9/25/2012 11:08 AM, Rudy (bulk) wrote:
On 9/24/12 11:52 PM, Hooman Fazaeli wrote:
sysctl dev.em.1
From the side having the 'No buffer space available' (FreeBSD 8.3 Sep 13 2012)
# sysctl dev.em.1
dev.em.1.%desc: Intel(R) PRO/1000 Network Connection 7.3.2
dev.em.1.%driver: em
dev.em.1.%lo
On Sep 25, 2012, at 12:38 AM, "Rudy (bulk)" wrote:
> On 9/24/12 11:52 PM, Hooman Fazaeli wrote:
>> sysctl dev.em.1
>
> From the side having the 'No buffer space available' (FreeBSD 8.3 Sep 13
> 2012)
>
> # sysctl dev.em.1
> dev.em.1.%desc: Intel(R) PRO/1000 Network Connection 7.3.2
> dev.em.
On 9/24/12 11:52 PM, Hooman Fazaeli wrote:
sysctl dev.em.1
From the side having the 'No buffer space available' (FreeBSD 8.3 Sep
13 2012)
# sysctl dev.em.1
dev.em.1.%desc: Intel(R) PRO/1000 Network Connection 7.3.2
dev.em.1.%driver: em
dev.em.1.%location: slot=0 function=0
dev.em.1.%pnpinfo
On 9/24/2012 7:50 PM, Rudy (bulk) wrote:
Sometimes when I try to ping a neighbor machine (plugged directly in with no
switch involved), I get:
ping: sendto: No buffer space available
ping: sendto: No buffer space available
If I reset the interface 'ifconfig em1 down; ifconfig em1 up
On Mon, Sep 24, 2012 at 8:06 PM, Rudy (bulk) wrote:
> On 9/24/12 5:01 PM, Ryan Stone wrote:
>>
>> Can you get the output of netstat -I emX -d?
>
> ...
>
>>
>> I suspect that you are seeing the em TX queue fill up. If so you
>> should see output drops reported by the em interface.
>>
> I do see 20
On 9/24/12 8:49 PM, Erich Dollansky wrote:
Hi,
On Mon, 24 Sep 2012 20:06:22 -0700
"Rudy (bulk)" wrote:
Checking all the interfaces, there are a lot more drops/Ierrs on
em2... The igb devices (PCIe card) seem a lot better than the
Supermicro motherboard em devices. Is this an on-board vs mb t
Hi,
On Mon, 24 Sep 2012 20:06:22 -0700
"Rudy (bulk)" wrote:
> Checking all the interfaces, there are a lot more drops/Ierrs on
> em2... The igb devices (PCIe card) seem a lot better than the
> Supermicro motherboard em devices. Is this an on-board vs mb thing,
> or em vs igb thing?
>
I do not
On 9/24/12 5:01 PM, Ryan Stone wrote:
Can you get the output of netstat -I emX -d?
...
I suspect that you are seeing the em TX queue fill up. If so you
should see output drops reported by the em interface.
I do see 205 in the 'Drop' column. I ran the command twice two hours
apart... I am s
Can you get the output of netstat -I emX -d? You don't need to run
that when the problem is happening -- you just need to run it on the
machine after it exhibits the issue without any reboots in the
interim.
I suspect that you are seeing the em TX queue fill up. If so you
should see output drops
Здравствуйте, Rudy.
check routing table and show which IP you ping.
Вы писали 24 сентября 2012 г., 19:20:28:
Rb> Sometimes when I try to ping a neighbor machine (plugged directly in
Rb> with no switch involved), I get:
Rb> ping: sendto: No buffer space available
Rb> ping: sendt
Sometimes when I try to ping a neighbor machine (plugged directly in
with no switch involved), I get:
ping: sendto: No buffer space available
ping: sendto: No buffer space available
If I reset the interface 'ifconfig em1 down; ifconfig em1 up' the
problem goes away.
The
> "No buffer space available" is ENOBUFS. This error is
> returned when the ifq is full - see IFQ_ENQUEUE in if_var.h.
> You'll almost certainly want to set ifq_len to larger than
> the default for a 10 gigabit driver. This most likely to be a
> combination of ifq_len being too small and inade
"No buffer space available" is ENOBUFS. This error is returned when
the ifq is full - see IFQ_ENQUEUE in if_var.h. You'll almost certainly
want to set ifq_len to larger than the default for a 10 gigabit
driver. This most likely to be a combination of ifq_len being too
small and inadequate txq overf
--- On Mon, 1/26/09, g...@freebsd.org wrote:
> From: g...@freebsd.org
> Subject: Re: freebsd 7.0-RELEASE BUG ping: sendto: No buffer space available
> To: "Rui Paulo"
> Cc: "Liran Liss" , freebsd-net@freebsd.org, "Yony
> Yossef" , jo...@nocre
At Sat, 24 Jan 2009 16:20:06 +,
Rui Paulo wrote:
>
>
> On 24 Jan 2009, at 12:54, Yony Yossef wrote:
>
> > Hi All,
> >
> > I'm facing a temporary network hang on my interfaces following a flood
> > ping/stress udp test.
> >
> > I'm running a netperf UDP test which is giving results but does n
On 24 Jan 2009, at 12:54, Yony Yossef wrote:
Hi All,
I'm facing a temporary network hang on my interfaces following a flood
ping/stress udp test.
I'm running a netperf UDP test which is giving results but does not
return
to the shell.
client output:
UDP UNIDIRECTIONAL SEND TEST from fe80:
Hi All,
I'm facing a temporary network hang on my interfaces following a flood
ping/stress udp test.
I'm running a netperf UDP test which is giving results but does not return
to the shell.
client output:
UDP UNIDIRECTIONAL SEND TEST from fe80::202:c9ff:fe02:e1fe%mtnic0
(fe80::202:c9ff:fe02:e
Synopsis: [if_tun] "ping: sendto: No buffer space available" with TUN interface
(easily reproducable with test program)
State-Changed-From-To: suspended->closed
State-Changed-By: rwatson
State-Changed-When: Sat Mar 8 20:24:15 UTC 2008
State-Changed-Why:
Closing the PR as it appears
8.125.2 ( 192.168.125.2): 56 data bytes
> 64 bytes from 192.168.125.2 : icmp_seq=0 ttl=64 time=0.554 ms
> 64 bytes from 192.168.125.2: icmp_seq=1 ttl=64 time=0.180 ms
> ...
> wait for a while
> ...
> ping: sendto: No buffer space available
> ping: sendto: No buffer space av
ttl=64 time=0.180 ms
...
wait for a while
...
ping: sendto: No buffer space available
ping: sendto: No buffer space available
ping: sendto: No buffer space available
With best regards,
Oleg Dolgov.
tun_icmp_echo_reply.c
Description: Binary data
The following reply was made to PR kern/95665; it has been noted by GNATS.
From: Astrodog <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Cc:
Subject: Re: kern/95665: [if_tun] "ping: sendto: No buffer space available"
with TUN interface (easily reproducable with te
Synopsis: [if_tun] "ping: sendto: No buffer space available" with TUN interface
(easily reproducable with test program)
Responsible-Changed-From-To: net->freebsd-net
Responsible-Changed-By: jmg
Responsible-Changed-When: Mon Oct 2 23:14:29 UTC 2006
Responsible-Changed-Why:
move
On Friday 29 September 2006 13:35, Gleb Smirnoff wrote:
> Bruce,
>
> On Fri, Sep 29, 2006 at 12:30:29PM +0100, Bruce M. Simpson wrote:
> B> >You kept the PR in feedback state for 11 hours, and then you
> B> >suspend the PR! Are you expecting our users to reply immediately?
> B> >
> B> The user re
Bruce,
On Fri, Sep 29, 2006 at 12:30:29PM +0100, Bruce M. Simpson wrote:
B> >You kept the PR in feedback state for 11 hours, and then you
B> >suspend the PR! Are you expecting our users to reply immediately?
B> >
B> The user responded saying they could not reproduce the problem further
B> as
Gleb Smirnoff wrote:
You didn't took it from free pool, but from me, w/o informing
me about it before. Okay. Now, you gave up on the PR quite
quickly, why aren't you returning it back to me?
Sorry! I have been trying to push forward on things and the PR formerly
being assigned to you got lo
Bruce,
On Wed, Sep 27, 2006 at 09:56:31PM +, Bruce M Simpson wrote:
B> Synopsis: [if_tun] "ping: sendto: No buffer space available" with TUN
interface (easily reproducable with test program)
B>
B> State-Changed-From-To: feedback->suspended
B> State-Changed-By:
Synopsis: [if_tun] "ping: sendto: No buffer space available" with TUN interface
(easily reproducable with test program)
State-Changed-From-To: feedback->suspended
State-Changed-By: bms
State-Changed-When: Wed Sep 27 21:56:02 UTC 2006
State-Changed-Why:
Back to the free pool (ca
I have a script in my crontab that runs ping to check the state of the
internet connection. The internet connection is PPTP using kernel ppp.
When there's much load on the connection I get an occasional error mail
from crontab saying
ping: sendto: No buffer space available
I have
36 matches
Mail list logo