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' the problem goes
away.
The pings are:
FreeBSD 8.3 em1 --> FreeBSD 9.0 em2
and I am seeing the issue on the FreeBSD 8.3 machine. The box has 6GB of free
ram and is a quagga router.
What do I need to tune?
Thanks!
Rudy
# netstat -m
10236/8454/18690 mbufs in use (current/cache/total)
10234/5388/15622/262144 mbuf clusters in use (current/cache/total/max)
10234/5382 mbuf+clusters out of packet secondary zone in use (current/cache)
0/327/327/12800 4k (page size) jumbo clusters in use (current/cache/total/max)
0/3070/3070/6400 9k jumbo clusters in use (current/cache/total/max)
0/0/0/3200 16k jumbo clusters in use (current/cache/total/max)
23027K/41827K/64854K bytes allocated to network (current/cache/total)
0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters)
0/0/0 requests for jumbo clusters denied (4k/9k/16k)
0/0/0 sfbufs in use (current/peak/max)
0 requests for sfbufs denied
0 requests for sfbufs delayed
0 requests for I/O initiated by sendfile
0 calls to protocol drain routines
# ifconfig em1
em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
ether 00:25:90:56:60:7f
inet 10.1.1.1 netmask 0xfffffffc broadcast 10.1.1.3
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
FreeBSD 8.3
### loader.conf:
net.link.ifqmaxlen=1024
hw.em.rxd=1024
hw.em.txd=1024
### sysctl.conf:
kern.timecounter.hardware=HPET
net.route.netisr_maxqlen=2048
net.inet.ip.intr_queue_maxlen=1024
kern.ipc.somaxconn=256
kern.random.sys.harvest.interrupt=0
kern.random.sys.harvest.ethernet=0
net.inet.raw.maxdgram=16384
net.inet.raw.recvspace=16384
net.inet.icmp.icmplim=1000
net.inet.ip.fastforwarding=1
kern.ipc.nmbclusters=262144
net.inet.icmp.drop_redirect=1
dev.em.0.rx_processing_limit=200
dev.em.1.rx_processing_limit=200
dev.em.2.rx_processing_limit=200
dev.em.3.rx_processing_limit=200
net.link.ether.inet.max_age=300
hw.intr_storm_threshold=9000
# Security
net.inet.ip.redirect=0
net.inet.ip.sourceroute=0
net.inet.ip.accept_sourceroute=0
net.inet.icmp.maskrepl=0
Not sure if it matters, but here are the tunings on the other box:
FreeBSD 9.0
### loader.conf:
net.link.ifqmaxlen="512"
### sysctl.conf:
net.inet.ip.fastforwarding=1
kern.ipc.nmbclusters=262144
kern.timecounter.hardware=HPET
net.inet.ip.rtminexpire=2
net.inet.ip.rtmaxcache=1024
dev.igb.0.rx_processing_limit=480
dev.igb.1.rx_processing_limit=480
net.inet.icmp.icmplim=1000
kern.random.sys.harvest.interrupt=0
kern.random.sys.harvest.ethernet=0
net.link.ether.inet.max_age=300
##Sat Apr 21 00:06:48 PDT 2012
net.inet.ip.redirect=0
net.route.netisr_maxqlen=2048
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[email protected]"
The most likely cause is that the interface send queue has become full and
stayed
in that condition. What type of NIC is at the other end of link? can you post
the output of:
# sysctl dev.em.1
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[email protected]"
