ust go down without
EN> leaving any errors behind, now this morning it went down but didn't cut
EN> my ssh connection to the box and I got this error:
EN> ping: sendto: No buffer space available
EN> From what I have found this relates to protocols like udp and icmp, I
EN> ass
behind, now this morning it went down but didn't cut my ssh
> connection to the box and I got this error:
>
> ping: sendto: No buffer space available
>
> From what I have found this relates to protocols like udp and icmp, I
> assume this can occur with p2p but also vpn protocols
>> Hi!
>>
>> I'm running FreeBSD 8.0. Some times my network just go down without
>> leaving any errors behind, now this morning it went down but didn't cut my
>> ssh connection to the box and I got this error:
>>
>> ping: sendto: No buffer space
Hi!
I'm running FreeBSD 8.0. Some times my network just go down without
leaving any errors behind, now this morning it went down but didn't cut
my ssh connection to the box and I got this error:
ping: sendto: No buffer space available
From what I have found this relates to prot
.
Message on the console:
ping: sendto: no buffer space available
Question 1: is it supposed to be fixed automatically within
a few minutes? This gateway is important in my network...
Question 2: is there some tuning I can do? Here is some output:
root# sysctl -a | grep space | grep
On Thu, 31 Jul 2003 06:25 am, Haesu wrote:
> Hmmm... i had truss running but the moment it died it was running
> gettimeoftheday() so i am not sure :-/
If it is software, the other thing to try might be sockstat if your not
already aware of it (it lists all the sockets being used by which program
world market for maybe five computers."
- IBM Chairman Thomas Watson, 1943
->-Original Message-
->From: Haesu [mailto:[EMAIL PROTECTED]
->Sent: Wednesday, July 30, 2003 4:26 PM
->To: Dave Byrne; [EMAIL PROTECTED]; [EMAIL PROTECTED]
->Subject: Re: sendto:
nfiguration, the only
> > difference is just the IP address of each interface.
> >
> > None of them fail but this one box...
> >
> > Everyday, this box stops all networking. I can still console in and stuff.. When
> > I typed 'ping 127.0.0.1' at the con
27.0.0.1' at the console after networking locked up, it says:
> ping: sendto: No buffer space available
>
> The only solution seems to be rebooting it everyday... It happens every 12 hours
> or so...
>
> This is not related with mbuf, etc either, as netstat -m doesn&#
Original Message -
> From: Haesu <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Wednesday, July 30, 2003 9:32 AM
> Subject: sendto: No buffer space available
>
>
> > Hello,
> >
> > We have a FreeBSD box here that we use t
t;[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, July 30, 2003 9:32 AM
Subject: sendto: No buffer space available
> Hello,
>
> We have a FreeBSD box here that we use to route some GRE tunnels and ipv6
gif tunnels. We use zebra for dynam
.
None of them fail but this one box...
Everyday, this box stops all networking. I can still console in and stuff.. When
I typed 'ping 127.0.0.1' at the console after networking locked up, it says:
ping: sendto: No buffer space available
The only solution seems to be rebooting it everyday...
* Jaime <[EMAIL PROTECTED]> [2003-06-18 12:28]:
> On Wednesday, June 18, 2003, at 07:17 AM, Loz wrote:
> >Sounds familiar - a friend had a Linux box cracked over the weekend...
> >apparently russian script kiddies using a php gallery exploit. Sorry I
> >don't have any more details, but I do know t
On Wednesday, June 18, 2003, at 07:17 AM, Loz wrote:
Sounds familiar - a friend had a Linux box cracked over the weekend...
apparently russian script kiddies using a php gallery exploit. Sorry I
don't have any more details, but I do know that in his case at least
nothing else was compromised. He f
* Jaime <[EMAIL PROTECTED]> [2003-06-18 00:49]:
> The clues to a crack are evident, too. A process "/usr/sbin/nscd"
> is running on the box according to top and ps, but the file does not
> exist. Further more, I never told such a process to execute. Shortly
> after a reboot, a netstat comm
On Tuesday, June 17, 2003, at 09:36 PM, Bill Moran wrote:
I found a web page that claims that nscd is a Debian program called
"name service cache daemon". (Cache only DNS server?) So if it's
connecting
to any port other than DNS, it's probably a trojan pretending to be
nscd.
I think that I fou
Jaime wrote:
FWIW, I think that I found the problem. With the help of our ISP,
we've found that one of my servers has been dumping so many packets out to
the Internet that our router was dropping packets. I've unplugged it at
this point and we do not have the same symptoms at this time.
FWIW, I think that I found the problem. With the help of our ISP,
we've found that one of my servers has been dumping so many packets out to
the Internet that our router was dropping packets. I've unplugged it at
this point and we do not have the same symptoms at this time.
The c
Bill Moran writes:
> So the comment that I made that it was either a driver, NIC, or link-level
> problem was near the mark?
>
Seems to me that it is. I'd suspect a link level problem myself, based on
the description of the problem.
> I spent a while looking through the source to get a better i
Gary Jennejohn wrote:
Bill Moran writes:
[EMAIL PROTECTED] wrote:
It looks like something is causing it to pile up packets in the
buffers temporarily. Any thoughts? In the mean time, I will see if I can
dig up a PCI ethernet card.
Yes, but it doesn't look like the pile is deep enough tha
Bill Moran writes:
> > [EMAIL PROTECTED] wrote:
> > It looks like something is causing it to pile up packets in the
> > buffers temporarily. Any thoughts? In the mean time, I will see if I can
> > dig up a PCI ethernet card.
>
> Yes, but it doesn't look like the pile is deep enough that it
[EMAIL PROTECTED] wrote:
On Tue, 17 Jun 2003, Bill Moran wrote:
I think that the NIC is on the logic board. I can try to install
a PCI card and use that in its place to see if the problem goes away.
Should I bother?
I would. There are two possibilities that I would consider here:
a) The
On Tue, 17 Jun 2003, Bill Moran wrote:
> > I think that the NIC is on the logic board. I can try to install
> > a PCI card and use that in its place to see if the problem goes away.
> > Should I bother?
>
> I would. There are two possibilities that I would consider here:
> a) The NIC has gone
[EMAIL PROTECTED] wrote:
On Tue, 17 Jun 2003, Bill Moran wrote:
What make/model of NIC are you using?
cerberus# ifconfig -a
fxp0: flags=8843 mtu 1500
inet 10.0.3.2 netmask 0xff00 broadcast 10.0.3.255
ether 00:e0:81:21:45:8c
media: Ethernet autoselect (10baseT/UTP)
On Tue, 17 Jun 2003, Bill Moran wrote:
> What make/model of NIC are you using?
cerberus# ifconfig -a
fxp0: flags=8843 mtu 1500
inet 10.0.3.2 netmask 0xff00 broadcast 10.0.3.255
ether 00:e0:81:21:45:8c
media: Ethernet autoselect (10baseT/UTP)
status: active
fxp1:
line and that there is a
problem on the ethernet interface of the router (which leads to the
firewall).
The pings will run just fine for several minutes at a time and
then begin to output this:
ping: sendto: No buffer space available
This will go on for anywhere from 15 seconds t
On Tue, 17 Jun 2003, lbland wrote:
> I don't know, but it may be a router loop problem in the ISP router
> tables. Those tables can change dynamically and can cause intermittent
> issues like you explained.
I had three pings going at the same time. One to the ISP's DNS
resolver, one to th
there is a
problem on the ethernet interface of the router (which leads to the
firewall).
The pings will run just fine for several minutes at a time and
then begin to output this:
ping: sendto: No buffer space available
This will go on for anywhere from 15 seconds to 5 mi
28 matches
Mail list logo
