Hi Wouter,
Please keep in mind the storage controler (Perc H755) is _not_ yet
supported by OpenBSD.
Cheers,
Laurent
Le 14/12/2023 à 15:43, Wouter Prins a écrit :
Thank you Laurent and Claudio,
We have an identical setup (hardware specs), i am sure we need this in
the near future. :)
/Wo
Thank you Laurent and Claudio,
We have an identical setup (hardware specs), i am sure we need this in the
near future. :)
/Wouter
On Thu, Dec 14, 2023 at 3:08 PM Claudio Jeker
wrote:
> On Tue, Nov 28, 2023 at 05:55:03PM +0100, Laurent CARON wrote:
> >
> > Le 28/11/2023 à 17:46, Claudio Jeker a
On Tue, Nov 28, 2023 at 05:55:03PM +0100, Laurent CARON wrote:
>
> Le 28/11/2023 à 17:46, Claudio Jeker a écrit :
> > The problem is that the symbol nkmempages moved into .bss and is therefor
> > no longer modifiable by config(8). I think you can still use ukc via
> > boot -c to alter it (but that
Le 28/11/2023 à 17:46, Claudio Jeker a écrit :
The problem is that the symbol nkmempages moved into .bss and is therefor
no longer modifiable by config(8). I think you can still use ukc via
boot -c to alter it (but that is not sticky).
The alternative is to set "option NKMEMPAGES=131072" in yo
On Tue, Nov 28, 2023 at 04:50:05PM +0100, Laurent CARON wrote:
> Le 28/11/2023 à 12:12, Claudio Jeker a écrit :
> > So the problem is that the malloc space is filled by
> > a) 26540K of devbuf -- because of the multiqueue support in ixl
> > b) 63493K of ACPI -- what the heck ACPI?!?
> > and then th
Le 28/11/2023 à 12:12, Claudio Jeker a écrit :
So the problem is that the malloc space is filled by
a) 26540K of devbuf -- because of the multiqueue support in ixl
b) 63493K of ACPI -- what the heck ACPI?!?
and then there is not enough space for rtable. A full table requires
in your example 50816
On Mon, Nov 27, 2023 at 05:51:25PM +0100, Laurent CARON wrote:
> Please find attached the relevant info:
>
> vmstat-m_SP_with_bgpd -> vmstat -m SP with bgpd
>
> vmstat-m_SMP_without_bgpd -> vmstat -m SMP without bgpd
>
> vmstat-m_SMP_with_bgpd_0{01..11} -> vmstat -m SMP with bgpd until crash.
>
Hi Claudio,
Should you need remote access to the server, this is of course possible.
Le 27/11/2023 à 17:51, Laurent CARON a écrit :
Please find attached the relevant info:
vmstat-m_SP_with_bgpd -> vmstat -m SP with bgpd
vmstat-m_SMP_without_bgpd -> vmstat -m SMP without bgpd
vmstat-m_SMP_wi
;
> - BGPd crashes with "panic: malloc: out of space in kmem_map" (please see
> screenshot).
>
> - When launching 'bgpd -dv' on the console, logs are showing:
>
> send_rtmsg: action 1, prefix 179.62.148.0/24: No buffer space available
> send_rtmsg: action 1, pr
d_rtmsg: action 1, prefix 179.62.148.0/24: No buffer space available
send_rtmsg: action 1, prefix 176.59.72.0/23: No buffer space available
send_rtmsg: action 1, prefix 176.59.70.0/23: No buffer space available
send_rtmsg: action 1, prefix 176.59.74.0/23: No buffer space available
send_rtmsg: act
On 6/28/22 02:48, Stuart Henderson wrote:
Did you try "ifconfig ix0 down" and "ifconfig ix0 up" when it was in the
failure condition? (Wondering whether you tried and it failed, or whether
you didn't try that before rebooting).
Yes sir an "ifconfig ix0 down"/"ifconfig ix0 up" was attempted due
ce this was done the network gateway device became
> inoperable and began again with the
>
> "No buffer space available" as in
>
> 0# ping www.google.com
> ping: Warning: www.google.com has multiple addresses; using 108.177.122.103
> PING www.google.com (108.177.122.1
determine what
triggers the condition and error. The IT Director and his team powered
down the telco vendor's/upstream equipment into which the ix0 device is
connected. Once this was done the network gateway device became
inoperable and began again with the
"No buffer space
On June 25, 2022 3:45:11 PM GMT-03:00, Stuart Henderson
wrote:
>On 2022-06-24, Boyd Stephens wrote:
>> On 6/23/22 05:34, Stuart Henderson wrote:
>>> How do the following look?
>>>
>>> pfctl -si
>>> systat -b mbuf
>>> vmstat -m
>>>
>>> Comparing normal + failed might be useful too.
>>>
>>>
On 2022-06-24, Boyd Stephens wrote:
> On 6/23/22 05:34, Stuart Henderson wrote:
>> How do the following look?
>>
>> pfctl -si
>> systat -b mbuf
>> vmstat -m
>>
>> Comparing normal + failed might be useful too.
>>
>> Are you using queues in pf?
>>
>> The ifconfig output you included looks norma
On 6/23/22 05:34, Stuart Henderson wrote:
How do the following look?
pfctl -si
systat -b mbuf
vmstat -m
Comparing normal + failed might be useful too.
Are you using queues in pf?
The ifconfig output you included looks normal. (rxpause/txpause is
"has negotiated flow control" and doesn't indic
s the ix0 device becomes inaccessible and when a
>> ping/traceroute/... command is attempted from the device through the
>> external network interface facing the Internet ie ix0 the following
>> error occurs
>>
>> # ping 8.8.8.8
>> PING 8.8.8.8 (8.8.8.8): 56 dat
mpted from the device through the
external network interface facing the Internet ie ix0 the following
error occurs
# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
ping: sendmsg: No buffer space available
ping: wrote 8.8.8.8 64 chars, ret=-1
ping: sendmsg: No buffer space available
ping:
ernal network interface facing the Internet ie ix0 the following
error occurs
# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
ping: sendmsg: No buffer space available
ping: wrote 8.8.8.8 64 chars, ret=-1
ping: sendmsg: No buffer space available
ping: wrote 8.8.8.8 64 chars, ret=-1
a netstat -n
I deployed two changes in my PF config.
(1) Bigger Queue
I rearranged some queues and gave the queue holding the DNS traffic more
bandwidth and a higher qlimit on the affected interface.
bnd_flows = "1024"
bnd_qlimit = "1024"
guest_local = "850M"
queue guest_local parent guest_root bandwidth $
FWIW: We experienced "sendto failed: No buffer space available" as well. QOS is
not configured, but the firewall is connected to a satellite link that drops
between 5-10% packets average. The explanation fits in with our situation.
-Original Message-
From: owner-m...@openb
On 2020-04-16, William Ahern wrote:
> I'm no network administrator, but a 3% failure rate would be very high on a
> physical interface. vlan4 is presumably the interface your Apple device
> passes through, right? Investigate why all the dropped packets. Start with
> your queuing rules: examine/ena
On Thu, Apr 16, 2020 at 10:28:55AM +0200, Ben wrote:
> > AFAIU, ENOBUFS happens when the NIC transmit queue is full. Have you looked
> > at the interface statistics to see if there are many dropped packets? Try,
> > e.g.,
> >
> > $ netstat -ni
>
> NameMtu Network Address I
> AFAIU, ENOBUFS happens when the NIC transmit queue is full. Have you looked
> at the interface statistics to see if there are many dropped packets? Try,
> e.g.,
>
> $ netstat -ni
NameMtu Network Address Ipkts IfailOpkts
Ofail Colls
lo0 32768
On Wed, Apr 15, 2020 at 10:53:49PM +0200, Ben wrote:
> I have exactly one device - an Apple smartphone - within one of the
> subnets, that Unbound is not able to send "some" data. The log tells us
> "sendto failed: No buffer space available". Beside the error messag
I could find on this topic, it seems that I am
unable to understand what my problem exactly is. In hope you might set
some light on this for me.
I have exactly one device - an Apple smartphone - within one of the
subnets, that Unbound is not able to send "some" data. The log tells us
&
On 20/02/16 13:52, Stuart Henderson wrote:
Are the carp interfaces "up" (i.e. master) when you see these messages?
Yes always.
On both firewalls I have net.inet.carp.log=3 and I haven't logged any
carp up/down - MASTER/BACKUP transition messages.
On the other hand, on backup firewall I just
;cvs up -D 2016/02/01'?
>>
>
> I went back to 2016/02/01 and 2016/01/12 (packet.c) and I have the same
> problem
> so it doesn't seem like a dhcrelay problem.
>
> I changed it to print the interfaces
> Feb 17 18:04:28 dhcrelay: send_packet: No buffer s
short?
Anyway I pushed it to 30 bpf devices and see how it goes.
G
Unfortunately that wasn't the problem...
Feb 19 09:10:42 dhcrelay: send_packet: No buffer space available carp48
# fstat|grep bpf|wc -l
19
any more ideas?
thanks
G
ghtly older source e.g. 'cvs up -D 2016/02/01'?
:>
:
:I went back to 2016/02/01 and 2016/01/12 (packet.c) and I have the same
:problem
:so it doesn't seem like a dhcrelay problem.
:
:I changed it to print the interfaces
:Feb 17 18:04:28 dhcrelay: send_packet: No buffer space ava
2016/02/01'?
:>
:
:I went back to 2016/02/01 and 2016/01/12 (packet.c) and I have the same
:problem
:so it doesn't seem like a dhcrelay problem.
:
:I changed it to print the interfaces
:Feb 17 18:04:28 dhcrelay: send_packet: No buffer space available on carp63
:Feb 18 09:16:35 dh
problem.
I changed it to print the interfaces
Feb 17 18:04:28 dhcrelay: send_packet: No buffer space available on carp63
Feb 18 09:16:35 dhcrelay: send_packet: No buffer space available on carp32
Feb 18 09:27:45 dhcrelay: send_packet: No buffer space available on carp32
but there is no network/r
On 2016-02-13, Kapetanakis Giannis wrote:
> On 12/02/16 18:56, Stuart Henderson wrote:
>> On 2016-02-12, Kapetanakis Giannis wrote:
>>> Hi,
>>>
>>> I have a carped firewall which is using dhcrelay to forward dhcp
>>> requests to another carped dhcp server.
>>> After upgrade to Feb 4 snapshot I'm
On 12/02/16 18:56, Stuart Henderson wrote:
On 2016-02-12, Kapetanakis Giannis wrote:
Hi,
I have a carped firewall which is using dhcrelay to forward dhcp
requests to another carped dhcp server.
After upgrade to Feb 4 snapshot I'm seeing these in my logs:
What version were you running before?
On 2016-02-12, Kapetanakis Giannis wrote:
> Hi,
>
> I have a carped firewall which is using dhcrelay to forward dhcp
> requests to another carped dhcp server.
> After upgrade to Feb 4 snapshot I'm seeing these in my logs:
What version were you running before?
To establish whether it's a dhcrel
On 02/12/16 12:15, Kapetanakis Giannis wrote:
I have a carped firewall which is using dhcrelay to forward dhcp
requests to another carped dhcp server.
After upgrade to Feb 4 snapshot I'm seeing these in my logs:
Feb 8 21:00:04 dhcrelay: send_packet: No buffer space available
Feb 9 16:
Hi,
I have a carped firewall which is using dhcrelay to forward dhcp
requests to another carped dhcp server.
After upgrade to Feb 4 snapshot I'm seeing these in my logs:
Feb 8 21:00:04 dhcrelay: send_packet: No buffer space available
Feb 9 16:47:02 dhcrelay: send_packet: No buffer
On 2012-07-13, Limaunion wrote:
> hi all! I'm running unbound as a caching resolver in an ALIX box running
> OpenBSD 5.1.
>
> For some reason I'm getting many of these kind of errors:
>
> Jul 13 10:56:29 pfire unbound: [11449:0] notice: sendto failed: No
> buffer
:0] notice: sendto failed: No
buffer space available
Jul 13 10:56:29 pfire unbound: [11449:0] notice: remote address is
8.8.8.8 port 53
Jul 13 10:56:29 pfire unbound: [11449:0] notice: sendto failed: No
buffer space available
Jul 13 10:56:29 pfire unbound: [11449:0] notice: remote address is
8.8.8.8 por
to failed: No
> buffer space available
> Jul 13 10:56:29 pfire unbound: [11449:0] notice: remote address is
> 8.8.8.8 port 53
> Jul 13 10:56:29 pfire unbound: [11449:0] notice: sendto failed: No
> buffer space available
> Jul 13 10:56:29 pfire unbound: [11449:0] notice: remote address
hi all! I'm running unbound as a caching resolver in an ALIX box running
OpenBSD 5.1.
For some reason I'm getting many of these kind of errors:
Jul 13 10:56:29 pfire unbound: [11449:0] notice: sendto failed: No
buffer space available
Jul 13 10:56:29 pfire unbound: [11449:0] noti
: OSPFD: No buffer space available
Hello List :)
i came through a problem and i need your opinion about it, i have noticed that
some times i get this type of errors in my /var/log/daemon file and these times
my ospf adjacency goes to loading and full again as you see on the logs a
little
2011/4/1 Mindless Gr :
> Hello List :)
>
> i came through a problem and i need your opinion about it, i have noticed that
> some times i get this type of errors in my /var/log/daemon file and these
> times
> my ospf adjacency goes to loading and full again as you see on the logs a
> little
> rese
:)
Apr 1 06:41:51 brdr0 ospfd[21953]: send_packet: error sending packet on
interface em1: No buffer space available
Apr 1 06:43:01 brdr0 last message repeated 3 times
Apr 1 06:43:21 brdr0 ospfd[21953]: recv_db_description: seq num mismatch, bad
flags
Apr 1 06:43:21 brdr0 ospfd[21953
a long time. And in our setup
replacing hfsc is not an option - I even run a customized kernel with
1024 queues per one level instead of the default 64."
Based on that I reverted back to the hfsc scheduler and bumped the
qlimit levels to the following. Since I've done this, I'm no
On 02/08/11 08:43, Jeff Ross wrote:
Stuart Henderson wrote:
Are you using altq?
Yes, using the hfsc scheduler. I think that was the hint I needed. udp
packets were all being assigned to the dns queue so I added another
match rule to put openvpn traffic into the default queue.
Here's what I ha
Stuart Henderson wrote:
Are you using altq?
Yes, using the hfsc scheduler. I think that was the hint I needed.
udp packets were all being assigned to the dns queue so I added another
match rule to put openvpn traffic into the default queue.
Here's what I have now:
match in all scrub
Are you using altq?
On 2011-02-07, Jeff Ross wrote:
> On 02/07/11 12:33, Christiano F. Haesbaert wrote:
>> On 7 February 2011 16:53, Jeff Ross wrote:
>>> Greetings,
>>>
>>> I found this explanation for the following OpenVPN error
>>> &qu
On 02/07/11 12:33, Christiano F. Haesbaert wrote:
On 7 February 2011 16:53, Jeff Ross wrote:
Greetings,
I found this explanation for the following OpenVPN error
"write UDPv4: No buffer space available (code=55)"
"No buffer space available is reported by the kernel net
On 7 February 2011 16:53, Jeff Ross wrote:
> Greetings,
>
> I found this explanation for the following OpenVPN error
> "write UDPv4: No buffer space available (code=55)"
>
> "No buffer space available is reported by the kernel network layer when
> thekernel&
Greetings,
I found this explanation for the following OpenVPN error
"write UDPv4: No buffer space available (code=55)"
"No buffer space available is reported by the kernel network layer when
thekernel's transmit buffer is full - i.e. the network connection is
runnin
Hello List,
Apologies for the potentially newbie question, but I am having
difficulty why the above error has been cropping up in my logs.
The server has been idle since its setup with no traffic flowing
through it (I've got SNMP monitoring to back-up that statement)
apart from my occasional
2009/4/9 ropers :
> 2009/4/9 Piotrek Kapczuk :
>>
>> More information you may find here
>> http://89.161.133.197/pub/x/problem.txt
>
> No I can't. I'm getting a HTTP 404 on that link.
Yeah sorry. Forget about it. I think I figured this out. I think it is
a queuing problem.
Sorry and thanks for yo
2009/4/9 Piotrek Kapczuk :
>
> More information you may find here
> http://89.161.133.197/pub/x/problem.txt
No I can't. I'm getting a HTTP 404 on that link.
Hi
I have a problem. Lately I start seeing No buffer space available"
errors. Server worked flawlessly for a few months and now it drops
packets. Hardware is PCENGINES ALIX Geode CPU.
More information you may find here
http://89.161.133.197/pub/x/problem.txt
It doesn't seem like
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
erface i have hfsc queing active. On server i have DHCPD server,
> DNS (bind), PF+queing, Postfix + sasl + postgrey + clamd for small group
> of users.
> Server working for 100 hosts.
>
> My problem: In my logs i'm getting following message:
>dhcpd: send_packet: No buffe
, Postfix + sasl + postgrey + clamd for small group of
users.
Server working for 100 hosts.
My problem: In my logs i'm getting following message:
dhcpd: send_packet: No buffer space available
I tried to change my NIC, change values for sysctl, but this did not help
me... Someone had si
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
Claudio Jeker wrote:
On Thu, Feb 01, 2007 at 09:32:17AM +0100, Federico Giannici wrote:
Claudio Jeker wrote:
On Wed, Jan 31, 2007 at 06:21:57PM +0100, Adriaan wrote:
On 1/31/07, Bret Lambert <[EMAIL PROTECTED]> wrote:
[snip]
Running and tuning OpenBSD network servers
in a production environme
On Thu, Feb 01, 2007 at 09:32:17AM +0100, Federico Giannici wrote:
> Claudio Jeker wrote:
> >On Wed, Jan 31, 2007 at 06:21:57PM +0100, Adriaan wrote:
> >>On 1/31/07, Bret Lambert <[EMAIL PROTECTED]> wrote:
> >>[snip]
> >>>Running and tuning OpenBSD network servers
> >>>in a production environment:
Claudio Jeker wrote:
On Wed, Jan 31, 2007 at 06:21:57PM +0100, Adriaan wrote:
On 1/31/07, Bret Lambert <[EMAIL PROTECTED]> wrote:
[snip]
Running and tuning OpenBSD network servers
in a production environment:
http://www.openbsd.org/papers/tuning-openbsd.ps
may have the info you're looking for
On Wed, Jan 31, 2007 at 06:21:57PM +0100, Adriaan wrote:
> On 1/31/07, Bret Lambert <[EMAIL PROTECTED]> wrote:
> [snip]
> >
> >Running and tuning OpenBSD network servers
> >in a production environment:
> >
> >http://www.openbsd.org/papers/tuning-openbsd.ps
> >
> >may have the info you're looking fo
On 1/31/07, Federico Giannici <[EMAIL PROTECTED]> wrote:
Adriaan wrote:
> On 1/31/07, Bret Lambert <[EMAIL PROTECTED]> wrote:
> [snip]
>>
>> Running and tuning OpenBSD network servers
>> in a production environment:
>>
>> http://www.openbsd.org/papers/tuning-openbsd.ps
>>
>> may have the info you
Adriaan wrote:
On 1/31/07, Bret Lambert <[EMAIL PROTECTED]> wrote:
[snip]
Running and tuning OpenBSD network servers
in a production environment:
http://www.openbsd.org/papers/tuning-openbsd.ps
may have the info you're looking for.
IIRC Theo said he would throw Henning in the ocean for that
On 1/31/07, Bret Lambert <[EMAIL PROTECTED]> wrote:
[snip]
Running and tuning OpenBSD network servers
in a production environment:
http://www.openbsd.org/papers/tuning-openbsd.ps
may have the info you're looking for.
IIRC Theo said he would throw Henning in the ocean for that paper ;)
=Adri
> If I tried to ping through the outgoing interface the "No buffer space
> available" error occurred.
>
> When the traffic decreased the error disappeared.
>
> What "buffer space" it is talking about?
> Is there some parameter (kernel, sysctl, ALTQ, etc...)
We have a PC with OpenBSD 4.0-stable i386 that we use as a
firewall/gateway. It has a lot of HFSC queues.
Today we had a flood if traffic and the outgoing interface started to
"loss" packets.
If I tried to ping through the outgoing interface the "No buffer space
available&
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
Thus spake David Coppa ([EMAIL PROTECTED]) [15/04/06 06:39]:
: Hi,
: pppoe(4) link on openbsd 3.9, nmap 4.01
:
: This is my error:
:
: root:/root:9# pfctl -F all
: rules cleared
: nat cleared
: 0 tables deleted.
: altq cleared
: 207 states cleared
: source tracking entries cleared
: pf: statistic
On Saturday, April 15, 2006, 10:41:09, nocfed wrote:
> The power went out at my house and now I can't login to my server.
Unless you've got a UPS you'll have to wait for the power to come back
on.
--
[EMAIL PROTECTED] "Behind every successful organization stands one
Rod Dorman
Hello,
The power went out at my house and now I can't login to my server.
On Sat, 2006-04-15 at 03:56 +0200, Chris Alatakis wrote:
> # pfctl -F all && pfctl -d
> # nmap -vv -sP '0.0.0.*'
>
> Starting nmap 3.81 ( http://www.insecure.org/nmap/ ) at 2006-04-15 01:58 UCT
> sendto in send_ip_packet: sendto(3, packet, 40, 0, 62.201.118.82, 16
# pfctl -F all && pfctl -d
# nmap -vv -sP '0.0.0.*'
Starting nmap 3.81 ( http://www.insecure.org/nmap/ ) at 2006-04-15 01:58 UCT
sendto in send_ip_packet: sendto(3, packet, 40, 0, 62.201.118.82, 16) =>
No buffer space available
Sleeping 15 seconds then retrying
ope
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
months. Communications in/out of the box would just stop or the machine
> >would
> >> crash. We were able to log in at the console. A ping command returned
> >the error
> >> message "no buffer space available." I searched the list archives and
> >fou
le to log in at the console. A ping command returned
the error
> message "no buffer space available." I searched the list archives and
found a
> few references to this error message along with some suggestions, but
nothing
> that ever said what fixed the problem.
>
It
ping command returned the
> error
> message "no buffer space available." I searched the list archives and found a
> few references to this error message along with some suggestions, but nothing
> that ever said what fixed the problem.
>
> We may have fixed this problem on our
One of my servers started having problems after it had been stable for about 10
months. Communications in/out of the box would just stop or the machine would
crash. We were able to log in at the console. A ping command returned the error
message "no buffer space available." I searche
> ping: no buffer space available
>
> Today I found the same error on a linux host, both hosts did not accept
> any connections any more neither were able to initiate any on that
> interface. A ifconfig down/up fixed it on the openbsd box. A reboot
> seemed necessary on the l
Hello,
I have had the following error on Openbsd 3.6/Sparc with a 3com 905:
ping: no buffer space available
Today I found the same error on a linux host, both hosts did not accept
any connections any more neither were able to initiate any on that
interface. A ifconfig down/up fixed it on the
94 matches
Mail list logo
