Re: ping: sendto: No buffer space available
Hi, Erik. You can not find out what buffer you have overflow. This error message cover many network buffers, sadly In my case I have some fortune I try and get that error disappeared by trying these: kern.ipc.maxsockbuf=1048576 net.graph.maxdgram=524288 net.graph.recvspace=524288 I do not know what that mean, but that work. beleave me Another sad thing there is no man, no documentations, no any FAQ for all sysctl variables, but you can find some info in mail lists Good luck. Вы писали 24 апреля 2010 г., 14:06:37: EN Hi! EN I'm running FreeBSD 8.0. Some times my network just 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 assume this can occur with p2p but also vpn protocols like l2tp. EN Is there some way that I can set limits on these protocols such that EN they will not use up all available buffer space? Or some way to increase EN buffer? EN Or is the problem something completely different? I've got two vr EN interfaces on a VIA Nehemiah ITX. EN Thanks, Erik -- С уважением, Eugen Konkov mailto:kes-...@yandex.ru http://kes.net.ua ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ping: sendto: No buffer space available
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 protocols like udp and icmp, I assume this can occur with p2p but also vpn protocols like l2tp. Is there some way that I can set limits on these protocols such that they will not use up all available buffer space? Or some way to increase buffer? Or is the problem something completely different? I've got two vr interfaces on a VIA Nehemiah ITX. Thanks, Erik -- Erik Nørgaard Ph: +34.666334818/+34.915211157 http://www.locolomo.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ping: sendto: No buffer space available
I almost forgot! And if you find out the reason for shortage you can tweak it with the appropiate sysctl value. At the moment I'm not sure which value you should tweak, but if you search for this issue, maybe you can find the appropiate net. values. Regards, MB. On 24 April 2010 22:35, Balázs Mátéffy repcs...@gmail.com wrote: Hello, I had a similar problem sometimes on one or two of my machines, look up netstat -m, usually if you run out of buffer space you have to tweak the mbuf memory size. You can see the memory usage current / cache / total, if the current or cache is the same value as the total, you have memory shortage. You can search for it, there are plenty of mail list archives about issue like this. Hope this helps! Best Regards, MB. On 24 April 2010 13:06, Erik Norgaard norga...@locolomo.org wrote: 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 protocols like udp and icmp, I assume this can occur with p2p but also vpn protocols like l2tp. Is there some way that I can set limits on these protocols such that they will not use up all available buffer space? Or some way to increase buffer? Or is the problem something completely different? I've got two vr interfaces on a VIA Nehemiah ITX. Thanks, Erik -- Erik Nørgaard Ph: +34.666334818/+34.915211157 http://www.locolomo.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ping: sendto: No buffer space available
Hello, I had a similar problem sometimes on one or two of my machines, look up netstat -m, usually if you run out of buffer space you have to tweak the mbuf memory size. You can see the memory usage current / cache / total, if the current or cache is the same value as the total, you have memory shortage. You can search for it, there are plenty of mail list archives about issue like this. Hope this helps! Best Regards, MB. On 24 April 2010 13:06, Erik Norgaard norga...@locolomo.org wrote: 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 protocols like udp and icmp, I assume this can occur with p2p but also vpn protocols like l2tp. Is there some way that I can set limits on these protocols such that they will not use up all available buffer space? Or some way to increase buffer? Or is the problem something completely different? I've got two vr interfaces on a VIA Nehemiah ITX. Thanks, Erik -- Erik Nørgaard Ph: +34.666334818/+34.915211157 http://www.locolomo.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
[gateway 4.9] sendto: no buffer space available
Hello, Hardware: PC, 128 Mo, 2 interfaces 3Com 3c905-TX Software: 4.9, generic kernel; from the initial distribution no special configuration Suddenly, this PC acting as a gateway stops forwarding packets, I was in a hurry so I just noticed that ICMP ping packets failed. 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 net net.local.stream.sendspace: 8192 net.local.stream.recvspace: 8192 net.local.dgram.recvspace: 4096 net.inet.tcp.sendspace: 32768 net.inet.tcp.recvspace: 57344 net.inet.udp.recvspace: 42080 net.inet.raw.recvspace: 8192 Thanks, -- Jacques Beigbeder| [EMAIL PROTECTED] Service de Prestations Informatiques | http://www.spi.ens.fr Ecole normale supérieure | 45 rue d'Ulm |Tel : (+33 1)1 44 32 37 96 F75230 Paris cedex 05|Fax : (+33 1)1 44 32 20 75 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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 dynamic routing running zebra, bgpd, ospfd, and ospf6d. We have about 12 FreeBSD boxes with exact same configuration, 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 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't show any issues. The box has one IP address and IPv6 address in addition to 127.0.0.1 on lo0 interface. It also has a ds0 interface with 10.5.5.5/30 assigned to ds0. This is exact same configuration on all other boxes, and none of them fail but this one. I've swapped out NICs with different vendors 3 times (tried, xl, dc, and now rl) I've also swapped out the whole box, and also swapped out the whole hard drive and did full reinstall. And problem still persists and it's definately not hardware as I swapped everything out... (unless the 3 NIC vendors above are all exhibiting same issue) I tried to look on Google but nothing useful that corelates to this particular issue.. Any help would be very appreciated :) Thanks, -hc The box is running FreeBSD 4.8-STABLE FreeBSD necsis 4.8-STABLE FreeBSD 4.8-STABLE #0: Tue Jul 29 13:10:11 GMT 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/router i386 Following is output of netstat -s AFTER the networking locks up with no buffer space available error: tcp: 30115 packets sent 17167 data packets (1232152 bytes) 301 data packets (54320 bytes) retransmitted 0 resends initiated by MTU discovery 12416 ack-only packets (10931 delayed) 0 URG only packets 0 window probe packets 41 window update packets 280 control packets 28010 packets received 16762 acks (for 1236693 bytes) 140 duplicate acks 0 acks for unsent data 13205 packets (567038 bytes) received in-sequence 43 completely duplicate packets (818 bytes) 0 old duplicate packets 2 packets with some dup. data (38 bytes duped) 9 out-of-order packets (240 bytes) 0 packets (0 bytes) of data after window 0 window probes 31 window update packets 0 packets received after close 0 discarded for bad checksums 0 discarded for bad header offset fields 0 discarded because packet too short 252 connection requests 18 connection accepts 6 bad connection attempts 0 listen queue overflows 30 connections established (including accepts) 288 connections closed (including 10 drops) 23 connections updated cached RTT on close 23 connections updated cached RTT variance on close 11 connections updated cached ssthresh on close 164 embryonic connections dropped 16643 segments updated rtt (of 16929 attempts) 1566 retransmit timeouts 10 connections dropped by rexmit timeout 0 persist timeouts 0 connections dropped by persist timeout 161 keepalive timeouts 0 keepalive probes sent 161 connections dropped by keepalive 96 correct ACK header predictions 10392 correct data packet header predictions 19 syncache entries added 6 retransmitted 2 dupsyn 0 dropped 18 completed 0 bucket overflow 0 cache overflow 0 reset 0 stale 0 aborted 0 badack 1 unreach 0 zone failures 0 cookies sent 0 cookies received udp: 196 datagrams received 0 with incomplete header 0 with bad data length field 0 with bad checksum 1 with no checksum 61 dropped due to no socket 3 broadcast/multicast datagrams dropped due to no socket 0 dropped due to full socket buffers 0 not for hashed pcb 132 delivered 132 datagrams output ip: 2154646 total packets received 0 bad header checksums 0 with size smaller than minimum 0 with data size data length 0 with ip length max ip packet size 0 with header length data size 0 with data length header length 0 with bad options 0 with incorrect version number 366 fragments received 0 fragments
Re: sendto: No buffer space available
I use a freebsd box as a gateway for my home network. It uses a dialup internet connection. When my ISP is having network problems, I will get the precise same issue. I have also had the modem crash, and also got the same problem. I could fix it by killing ppp and restarting it.That clears the tcp buffers for ppp. I suspect you possibly have a bad NIC or perhaps some other network issue that's intermittent. Taking down the interface might clear the buffers... NEOFAST.NET North East Oregon FAST Net mark(at)neofast.net - 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 to route some GRE tunnels and ipv6 gif tunnels. We use zebra for dynamic routing running zebra, bgpd, ospfd, and ospf6d. We have about 12 FreeBSD boxes with exact same configuration, 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 console after networking locked up, it says: ping: sendto: No buffer space available --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.504 / Virus Database: 302 - Release Date: 7/24/03 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sendto: No buffer space available
I did ifconfig down/up on all interfaces, and that didn't help... The only way to clear it up seems like rebooting the whole box.. This one isn't related to any ppp, it has gre tunnels which are kernel based... This is bazzarre problem.. none of the other boxes exhibit this problem ever.. Thanks, -hc -- Sincerely, Haesu C. TowardEX Technologies, Inc. WWW: http://www.towardex.com E-mail: [EMAIL PROTECTED] Cell: (978) 394-2867 On Wed, Jul 30, 2003 at 10:02:02AM -0700, Mark Koskenmaki wrote: I use a freebsd box as a gateway for my home network. It uses a dialup internet connection. When my ISP is having network problems, I will get the precise same issue. I have also had the modem crash, and also got the same problem. I could fix it by killing ppp and restarting it.That clears the tcp buffers for ppp. I suspect you possibly have a bad NIC or perhaps some other network issue that's intermittent. Taking down the interface might clear the buffers... NEOFAST.NET North East Oregon FAST Net mark(at)neofast.net - 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 to route some GRE tunnels and ipv6 gif tunnels. We use zebra for dynamic routing running zebra, bgpd, ospfd, and ospf6d. We have about 12 FreeBSD boxes with exact same configuration, 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 console after networking locked up, it says: ping: sendto: No buffer space available --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.504 / Virus Database: 302 - Release Date: 7/24/03 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sendto: No buffer space available
I had the same exact problem. I traced it to be a bug in some software
that opened a domain socket(2) but could not connect(2) and never closed
the descriptor returned.
something like:
sd = socket(AF_UNIX, SOCK_STREAM, 0);
...
if(connect(sd, (struct sockaddr *)saddr, sizeof(saddr)) 0) {
return -1;
}
where close(2) was skipped on sd if the connect failed.
over a period of time (12-18hrs), these unconnected sockets would fill
up the available buffer space, and exhibit the same symptoms you are
having. even running ifconfig would fail with No buffer space available.
from intro(2):
55 ENOBUFS No buffer space available. An operation on a socket or pipe
was not performed because the system lacked sufficient buffer space or
because a queue was full.
Fixing that bug fixed the problem. I doubt you have a hardware problem,
I would try narrowing down what software is causing the lockup. truss(1)
might help you out here.
Dave
On Wed, 2003-07-30 at 09:32, Haesu wrote:
Hello,
We have a FreeBSD box here that we use to route some GRE tunnels and ipv6 gif
tunnels. We use zebra for dynamic routing running zebra, bgpd, ospfd, and ospf6d.
We have about 12 FreeBSD boxes with exact same configuration, 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 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't show any
issues.
The box has one IP address and IPv6 address in addition to 127.0.0.1 on lo0
interface. It also has a ds0 interface with 10.5.5.5/30 assigned to ds0.
This is exact same configuration on all other boxes, and none of them fail but
this one.
I've swapped out NICs with different vendors 3 times (tried, xl, dc, and now rl)
I've also swapped out the whole box, and also swapped out the whole hard drive
and did full reinstall. And problem still persists and it's definately not
hardware as I swapped everything out... (unless the 3 NIC vendors above are all
exhibiting same issue)
I tried to look on Google but nothing useful that corelates to this particular
issue..
Any help would be very appreciated :)
Thanks,
-hc
The box is running FreeBSD 4.8-STABLE
FreeBSD necsis 4.8-STABLE FreeBSD 4.8-STABLE #0: Tue Jul 29 13:10:11 GMT 2003
[EMAIL PROTECTED]:/usr/src/sys/compile/router i386
Following is output of netstat -s AFTER the networking locks up with no buffer
space available error:
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sendto: No buffer space available
Hmmm... i had truss running but the moment it died it was running gettimeoftheday() so
i am not sure :-/
I tried different ports on the switch.. It's a cisco switch btw, and other freebsd
boxes on that switch
are not exhibiting similar problem
I'll try putting this behind a hub or something other than cisco just for kicks but if
anyone has any further ideas/suggestions, i'd really appreciate it.
Thank you!
-hc
--
Sincerely,
Haesu C.
TowardEX Technologies, Inc.
WWW: http://www.towardex.com
E-mail: [EMAIL PROTECTED]
Cell: (978) 394-2867
On Wed, Jul 30, 2003 at 11:36:35AM -0700, Dave Byrne wrote:
I had the same exact problem. I traced it to be a bug in some software
that opened a domain socket(2) but could not connect(2) and never closed
the descriptor returned.
something like:
sd = socket(AF_UNIX, SOCK_STREAM, 0);
...
if(connect(sd, (struct sockaddr *)saddr, sizeof(saddr)) 0) {
return -1;
}
where close(2) was skipped on sd if the connect failed.
over a period of time (12-18hrs), these unconnected sockets would fill
up the available buffer space, and exhibit the same symptoms you are
having. even running ifconfig would fail with No buffer space available.
from intro(2):
55 ENOBUFS No buffer space available. An operation on a socket or pipe
was not performed because the system lacked sufficient buffer space or
because a queue was full.
Fixing that bug fixed the problem. I doubt you have a hardware problem,
I would try narrowing down what software is causing the lockup. truss(1)
might help you out here.
Dave
On Wed, 2003-07-30 at 09:32, Haesu wrote:
Hello,
We have a FreeBSD box here that we use to route some GRE tunnels and ipv6 gif
tunnels. We use zebra for dynamic routing running zebra, bgpd, ospfd, and ospf6d.
We have about 12 FreeBSD boxes with exact same configuration, 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 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't show any
issues.
The box has one IP address and IPv6 address in addition to 127.0.0.1 on lo0
interface. It also has a ds0 interface with 10.5.5.5/30 assigned to ds0.
This is exact same configuration on all other boxes, and none of them fail but
this one.
I've swapped out NICs with different vendors 3 times (tried, xl, dc, and now rl)
I've also swapped out the whole box, and also swapped out the whole hard drive
and did full reinstall. And problem still persists and it's definately not
hardware as I swapped everything out... (unless the 3 NIC vendors above are all
exhibiting same issue)
I tried to look on Google but nothing useful that corelates to this particular
issue..
Any help would be very appreciated :)
Thanks,
-hc
The box is running FreeBSD 4.8-STABLE
FreeBSD necsis 4.8-STABLE FreeBSD 4.8-STABLE #0: Tue Jul 29 13:10:11 GMT 2003
[EMAIL PROTECTED]:/usr/src/sys/compile/router i386
Following is output of netstat -s AFTER the networking locks up with no buffer
space available error:
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isp
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: sendto: No buffer space available
I think heading down the path of switchign out network
gear is a bad idea, this is definitely something in
the software.
I have had this error a few times when messing with
the TCP window sizes, net.inet.tcp.sendspace and
net.inet.tcp.recvspace. When I set them to something
over 128000 I would get the error. The solution was
set the number of mbufs to 128000. Doing so allowed
me to make the window sizes 256000 and eliminated
the error.
-good luck
-mtl
--
Michael Lapinski
Computer Scientist
GE Research
I think there is a 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: No buffer space available
-
-
-Hmmm... i had truss running but the moment it died it was
-running gettimeoftheday() so i am not sure :-/
-
-I tried different ports on the switch.. It's a cisco switch
-btw, and other freebsd boxes on that switch
-are not exhibiting similar problem
-
-I'll try putting this behind a hub or something other than
-cisco just for kicks but if anyone has any further
-ideas/suggestions, i'd really appreciate it.
-
-Thank you!
-
--hc
-
---
-Sincerely,
- Haesu C.
- TowardEX Technologies, Inc.
- WWW: http://www.towardex.com
- E-mail: [EMAIL PROTECTED]
- Cell: (978) 394-2867
-
-On Wed, Jul 30, 2003 at 11:36:35AM -0700, Dave Byrne wrote:
- I had the same exact problem. I traced it to be a bug in
-some software
- that opened a domain socket(2) but could not connect(2) and
-never closed
- the descriptor returned.
-
- something like:
-
- sd = socket(AF_UNIX, SOCK_STREAM, 0);
- ...
- if(connect(sd, (struct sockaddr *)saddr, sizeof(saddr)) 0) {
-return -1;
- }
-
- where close(2) was skipped on sd if the connect failed.
-
- over a period of time (12-18hrs), these unconnected sockets
-would fill
- up the available buffer space, and exhibit the same symptoms you are
- having. even running ifconfig would fail with No buffer
-space available.
-
- from intro(2):
- 55 ENOBUFS No buffer space available. An operation on a
-socket or pipe
- was not performed because the system lacked sufficient
-buffer space or
- because a queue was full.
-
- Fixing that bug fixed the problem. I doubt you have a
-hardware problem,
- I would try narrowing down what software is causing the
-lockup. truss(1)
- might help you out here.
-
-
-
- Dave
-
-
-
-
- On Wed, 2003-07-30 at 09:32, Haesu wrote:
- Hello,
-
- We have a FreeBSD box here that we use to route some GRE
-tunnels and ipv6 gif tunnels. We use zebra for dynamic
-routing running zebra, bgpd, ospfd, and ospf6d.
-
- We have about 12 FreeBSD boxes with exact same
-configuration, 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 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't show any
- issues.
-
- The box has one IP address and IPv6 address in addition
-to 127.0.0.1 on lo0
- interface. It also has a ds0 interface with 10.5.5.5/30
-assigned to ds0.
- This is exact same configuration on all other boxes, and
-none of them fail but
- this one.
-
- I've swapped out NICs with different vendors 3 times
-(tried, xl, dc, and now rl)
-
- I've also swapped out the whole box, and also swapped out
-the whole hard drive
- and did full reinstall. And problem still persists and
-it's definately not
- hardware as I swapped everything out... (unless the 3 NIC
-vendors above are all
- exhibiting same issue)
-
- I tried to look on Google but nothing useful that
-corelates to this particular
- issue..
-
- Any help would be very appreciated :)
-
- Thanks,
- -hc
-
- The box is running FreeBSD 4.8-STABLE
- FreeBSD necsis 4.8-STABLE FreeBSD 4.8-STABLE #0: Tue Jul
-29 13:10:11 GMT 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/router i386
-
- Following is output of netstat -s AFTER the networking
-locks up with no buffer
- space available error:
-
-
- ___
- [EMAIL PROTECTED] mailing list
- http://lists.freebsd.org/mailman/listinfo/freebsd-isp
- To unsubscribe, send any mail to
-[EMAIL PROTECTED]
-
-___
-[EMAIL PROTECTED] mailing list
-http://lists.freebsd.org/mailman/listinfo/freebsd-isp
-To unsubscribe, send any mail to [EMAIL PROTECTED]
-
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo
Re: sendto: No buffer space available
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 programs). JacobRhoden - http://rhoden.id.au/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ping: sendto: No buffer space available
* 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 that in his case at least nothing else was compromised. He found all the answers he needed on Google. So only his Gallery install was compomised? Or was there a more direct effect, e.g. a backdoor or rootkit install? No other damage apart from a little trojan ping flooding the network and filling up log files. More details on the Gallery exploit at http://www.linuxadvisory.com/articles.php?articleId=35page=3 HTH /loz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ping: sendto: No buffer space available
* 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 command showed a connection to 37303 on a remote host. I was the only person logged in and I did not initiate that connection. 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 found all the answers he needed on Google. good luck, /loz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ping: sendto: No buffer space available
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 found all the answers he needed on Google. So only his Gallery install was compomised? Or was there a more direct effect, e.g. a backdoor or rootkit install? Thanks in advance, Jaime ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ping: sendto: No buffer space available
I've been noticing for a few days that my network's performance is less than good. When I checked on it, I found that the firewall attempting to ping the ISP's DNS resolver would have hiccups. The ISP claims that there is nothing wrong on the T-1 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 to 5 minutes, during which we're effectively not connected to the Internet at all. An occasional ping will work, but only about 1 in 20 and it seems random. Then, just as suddenly, the connection will work again. I'm not completely sure what this means, but I found the following command in the mailing list archives: cerberus# sysctl -a | grep intr_qu net.inet.ip.intr_queue_maxlen: 50 net.inet.ip.intr_queue_drops: 6987 Does anyone have any suggestions or tips? Thanks in advance, Jaime -- To affect the quality of the day, that is the highest of arts. - Henry David Thoreau, _Where_I_Live_ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ping: sendto: No buffer space available
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 the far end of the T-1, and one to the ethernet interface on the router at my site. The router and firewall are on opposite ends of the same cable. When the pings to the DNS resolver gave the No buffer space message, so did the other two pings. This means that the break down is not any further up stream than the router. I'm now running pings to a host on the same LAN as the firewall. The next time that the No buffer space message appears on the pings to the DNS resolver, I'll check the pings to the internal host. If they have the same problem, then I'm experiencing an OS level issue of some kind. OK, it happened while I was typing this. :) Results: internal host remained ping-able while the other three pings were all giving No buffer space messages. This is starting to sound like some kind of packet over-load on the public side of my FreeBSD/ipfw based firewall. Does anyone have any advice on how to confirm this? bash-2.05b$ uname -a FreeBSD cerberus.cairodurham.org. 4.7-STABLE FreeBSD 4.7-STABLE #0: Sat Oct 12 12:54:03 EDT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CERBERUS i386 Thanks in advance, Jaime ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ping: sendto: No buffer space available
Jaime wrote: I've been noticing for a few days that my network's performance is less than good. When I checked on it, I found that the firewall attempting to ping the ISP's DNS resolver would have hiccups. The ISP claims that there is nothing wrong on the T-1 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 to 5 minutes, during which we're effectively not connected to the Internet at all. An occasional ping will work, but only about 1 in 20 and it seems random. Then, just as suddenly, the connection will work again. I'm not completely sure what this means, but I found the following command in the mailing list archives: cerberus# sysctl -a | grep intr_qu net.inet.ip.intr_queue_maxlen: 50 net.inet.ip.intr_queue_drops: 6987 Does anyone have any suggestions or tips? What make/model of NIC are you using? The only time I've ever seen this, the only thing that solved the problem was swapping the network card out for a better one. That's not to say it isn't a driver problem, as the new network card used a different driver as well. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ping: sendto: No buffer space available
On Tue, 17 Jun 2003, Bill Moran wrote: What make/model of NIC are you using? cerberus# ifconfig -a fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST 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: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 10.1.1.1 netmask 0x broadcast 10.1.255.255 ether 00:e0:81:21:45:8d media: Ethernet autoselect (100baseTX full-duplex) status: active lp0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 ppp0: flags=8010POINTOPOINT,MULTICAST mtu 1500 sl0: flags=c010POINTOPOINT,LINK2,MULTICAST mtu 552 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 The interface in question is 10.0.3.2. That interface has worked fine for over a year. That driver is in use on several other systems for several years each. No problems until now. The only time I've ever seen this, the only thing that solved the problem was swapping the network card out for a better one. That's not to say it isn't a driver problem, as the new network card used a different driver as well. 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? FWIW, a reboot of the system did not help. Jaime ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ping: sendto: No buffer space available
[EMAIL PROTECTED] wrote: On Tue, 17 Jun 2003, Bill Moran wrote: What make/model of NIC are you using? cerberus# ifconfig -a fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST 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 SNIP The interface in question is 10.0.3.2. That interface has worked fine for over a year. That driver is in use on several other systems for several years each. No problems until now. I, too, have use Intel cards with the fxp driver quite often, with no problems. The only time I've ever seen this, the only thing that solved the problem was swapping the network card out for a better one. That's not to say it isn't a driver problem, as the new network card used a different driver as well. 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 flaky with age b) Newer drivers don't talk to that particular NIC as well as the old Did you notice this starting to happen after a particular upgrade? You may be able to correlate this with a particular update to the driver by looking at dates in the cvs logs. This is hearsay, and I have no personal experience with it, but I've seen lots of complaints across the lists about onboard cards that use the fxp driver not being very good. I've never had (nor heard of) any problems with the PCI versions. Another possibility is hardware ... have you added any hardware or changed any BIOS settings? There's the possibility of interrupt problems. I'm just shooting out ideas for you to work with. Please distill everything I've said through your own experience. i.e. take it with a grain of salt, as I don't _know_ what your problem is. FWIW, a reboot of the system did not help. Never helped for me either. You may want to check, but in my experience the output of 'netstat -m' will also tell you that you have plenty of network buffers available. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ping: sendto: No buffer space available
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 flaky with age b) Newer drivers don't talk to that particular NIC as well as the old Did you notice this starting to happen after a particular upgrade? You may be able to correlate this with a particular update to the driver by looking at dates in the cvs logs. Nope. The problem is only a few days old and the OS is 4.7-Stable. I think that the last update was in February or so. This is hearsay, and I have no personal experience with it, but I've seen lots of complaints across the lists about onboard cards that use the fxp driver not being very good. I've never had (nor heard of) any problems with the PCI versions. Hrm An interesting thought Another possibility is hardware ... have you added any hardware or changed any BIOS settings? There's the possibility of interrupt problems. No. The system was up for more than 2 months before the problems began. I'm just shooting out ideas for you to work with. Please distill everything I've said through your own experience. i.e. take it with a grain of salt, as I don't _know_ what your problem is. I always try to take email list advice this way. :) Never helped for me either. You may want to check, but in my experience the output of 'netstat -m' will also tell you that you have plenty of network buffers available. bash-2.05b$ netstat -m 144/768/26624 mbufs in use (current/peak/max): 139 mbufs allocated to data 5 mbufs allocated to packet headers 138/572/6656 mbuf clusters in use (current/peak/max) 1336 Kbytes allocated to network (6% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines That was durring normal operation. The following are at the tail end of one of the outages: bash-2.05b$ netstat -m 477/768/26624 mbufs in use (current/peak/max): 386 mbufs allocated to data 91 mbufs allocated to packet headers 384/572/6656 mbuf clusters in use (current/peak/max) 1336 Kbytes allocated to network (6% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines bash-2.05b$ netstat -m 476/768/26624 mbufs in use (current/peak/max): 387 mbufs allocated to data 89 mbufs allocated to packet headers 385/572/6656 mbuf clusters in use (current/peak/max) 1336 Kbytes allocated to network (6% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines bash-2.05b$ netstat -m 182/768/26624 mbufs in use (current/peak/max): 149 mbufs allocated to data 33 mbufs allocated to packet headers 147/572/6656 mbuf clusters in use (current/peak/max) 1336 Kbytes allocated to network (6% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines bash-2.05b$ netstat -m 156/768/26624 mbufs in use (current/peak/max): 153 mbufs allocated to data 3 mbufs allocated to packet headers 151/572/6656 mbuf clusters in use (current/peak/max) 1336 Kbytes allocated to network (6% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines bash-2.05b$ netstat -m 135/768/26624 mbufs in use (current/peak/max): 134 mbufs allocated to data 1 mbufs allocated to packet headers 132/572/6656 mbuf clusters in use (current/peak/max) 1336 Kbytes allocated to network (6% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines bash-2.05b$ netstat -m 144/768/26624 mbufs in use (current/peak/max): 139 mbufs allocated to data 5 mbufs allocated to packet headers 136/572/6656 mbuf clusters in use (current/peak/max) 1336 Kbytes allocated to network (6% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines 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. Thanks, Jaime ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ping: sendto: No buffer space available
[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 NIC has gone flaky with age b) Newer drivers don't talk to that particular NIC as well as the old Another possibility that bites me in the ass when I'm not looking is link-level problems. Occasionally I've had weird issues that were resolved by replacing a switch or patch cable, or by moving to a different port on a switch. As usual ... just throwing ideas at you. Never helped for me either. You may want to check, but in my experience the output of 'netstat -m' will also tell you that you have plenty of network buffers available. bash-2.05b$ netstat -m 144/768/26624 mbufs in use (current/peak/max): 139 mbufs allocated to data 5 mbufs allocated to packet headers 138/572/6656 mbuf clusters in use (current/peak/max) 1336 Kbytes allocated to network (6% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines That was durring normal operation. The following are at the tail end of one of the outages: bash-2.05b$ netstat -m 477/768/26624 mbufs in use (current/peak/max): 386 mbufs allocated to data 91 mbufs allocated to packet headers 384/572/6656 mbuf clusters in use (current/peak/max) 1336 Kbytes allocated to network (6% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines snip additional netstat -m output 144/768/26624 mbufs in use (current/peak/max): 139 mbufs allocated to data 5 mbufs allocated to packet headers 136/572/6656 mbuf clusters in use (current/peak/max) 1336 Kbytes allocated to network (6% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines 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 should have run out of buffer space. This one is a bit of a shot in the dark, but try using rndcontrol to increase the entropy collection. I'm not sure why I think this might help, but I have some vague memory of it helping somewhere. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ping: sendto: No buffer space available
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 should have run out of buffer space. The ``No buffer space available'' message generally has _nothing at all_ to do with whether there are enough mbufs available. It really means that the send queue in the driver is full and no further packets can be added to it until it drains soemwhat. The message indicates that, for some reason, the driver can't send out any packets on the wire. For some reason most people think that this message means they've run out of mbufs. Examination of the source would quickly disabuse them of this idea. --- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org gj[at]denx.de ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ping: sendto: No buffer space available
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 that it should have run out of buffer space. The ``No buffer space available'' message generally has _nothing at all_ to do with whether there are enough mbufs available. It really means that the send queue in the driver is full and no further packets can be added to it until it drains soemwhat. The message indicates that, for some reason, the driver can't send out any packets on the wire. So the comment that I made that it was either a driver, NIC, or link-level problem was near the mark? For some reason most people think that this message means they've run out of mbufs. Examination of the source would quickly disabuse them of this idea. My original comment was meant to say that. But apparently I didn't communicate well enough. I spent a while looking through the source to get a better idea of where that error originates, and only got frustrated. As a favor, can you point me to the area of the source from which I can learn more of this? -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ping: sendto: No buffer space available
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 idea of where that error originates, and only got frustrated. As a favor, can you point me to the area of the source from which I can learn more of this? In -current things have changed, so I could now be wrong. Most of the drivers now return ENOBUFS if they really can't get an mbuf, but I haven't examined all the drivers to see under just which circumstances they return ENOBUFS. However, I was thinking of the macro IF_HANDOFF(), which uses if_handoff() which uses _IF_QFULL(), all of which are defined in /sys/net/if_var.h. _IF_QFULL() actually checks whether the send queue is full. IF_HANDOFF() is invoked (among other places) in /sys/net/netisr.c and /sys/net/if_ethersubr.c. I remember running into this situation while debugging ISDN drivers, many of which use IF_HANDOFF(). Most moden ethernet drivers don't seem to use it any more. --- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org gj[at]denx.de ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ping: sendto: No buffer space available
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 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 command showed a connection to 37303 on a remote host. I was the only person logged in and I did not initiate that connection. Obviously, I'll be taking steps to find the crack and remote it. :) If anyone wants to suggest something to check, I'd appreciate it. Jaime -- To affect the quality of the day, that is the highest of arts. - Henry David Thoreau, _Where_I_Live_ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ping: sendto: No buffer space available
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. 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 command showed a connection to 37303 on a remote host. I was the only person logged in and I did not initiate that connection. Obviously, I'll be taking steps to find the crack and remote it. :) If anyone wants to suggest something to check, I'd appreciate it. 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. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ping: sendto: No buffer space available
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 found the same page. I agree with your assessment. The IP address that it is attempting to connect to is not found via traceroute and is registered to what appears to be a Russian ISP. How odd I'll be grabbing new source code and recompiling everything tomorrow. The box was running 4.7-Stable anyway. :) The troubling part is that the process claims to be /usr/sbin/nscd, but that file doesn't exist. I'll have to see how they did that with lsof, mergemaster, etc. Jaime ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
