STRANGE! No buffer space available



  • Hi!

    There is something strange going on at my pfSense machine!

    I have read a lot of 'same' problems but noone was quite the same as mine.

    When I'm pinging a IP address outside of pfSense, I get SOMETIMES 'ping: sendto: No buffer space available' as seen below:

    [2.0.2-RELEASE][bbele@sheldon.ylog]/home/bbele(14): ping 192.168.1.1
    PING 192.168.1.1 (192.168.1.1): 56 data bytes
    64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=56.594 ms
    64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=7.197 ms
    64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=9.513 ms
    64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=103.933 ms
    ping: sendto: No buffer space available
    64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=12.534 ms
    64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=6.330 ms
    64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=7.791 ms

    I have my pfSense router behind another router because of testing porpouses and will take it as my router later whenn the network behind pfSense is stable. I have some Vlans on it and for now it is already acting as my DNS forwarder. If I'm pinging from the second NIC (LAN), I have not such msgs (both NICs are the same and onboard).

    We bought an entry-server some time ago and I'm using it now for pfSense. It has some GB Intel NICs (i would like to know what hw I have but I'm to new to freeBSD and don't know the commands).

    I hope I posted enough infos!

    Kind Regards, BB



  • @MuadDib:

    …i would like to know what hw I have but I'm to new to freeBSD and don't know the commands).

    The command that will show you the hardware on your machine is:

    dmesg
    

    Try this too:

    ping -c 3 192.168.1.1
    

    The -c flag is the count and designates how many packets you'll use with the ping command, in this instance 3.



  • Thank you mr_bobo!

    I was using the command "dmesg -a" and I haven't got any usable info! Just post-install msgs (I just upgraded pfSense to 2.0.3). I had just a look on the suppliers page and my NICs are Intel 82574L. I have a Supermicro board named X7SPA-H http://www.supermicro.com/products/motherboard/ATOM/ICH9/X7SPA.cfm?typ=H (I hope I'm allowed to share links else pleas a moderator to clean it out).

    If I putted the command 'ping -c 5 -s 1484 192.168.1.1' (MTU is 1492) I had no messages. It is just going to be about 2-25% packet loss and this is why I'm using ping without any count or count til 100 or even 1000.  I'm have such issues something later in the day (can a machine get tired??? :P) and we have a AC set to 16°C.

    I've just ordered another computer to see if this is an hw issue (as the msg is comming just sometimes).

    I've just recorded I become a HUGE packet loss if I'm going over MTU! IP framing is not well implemented somehow.

    [2.0.3-RELEASE][root@sheldon.ylog]/root(1): ping -c 5 -s 30000 192.168.1.1
    PING 192.168.1.1 (192.168.1.1): 30000 data bytes
    ping: sendto: No buffer space available
    30008 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=1086.535 ms
    ping: sendto: No buffer space available
    ping: sendto: No buffer space available
    ping: sendto: No buffer space available
    
    --- 192.168.1.1 ping statistics ---
    5 packets transmitted, 1 packets received, 80.0% packet loss
    round-trip min/avg/max/stddev = 1086.535/1086.535/1086.535/0.000 ms
    

    I have no clue what is happening!



  • You might have to increase mbufs.

    What's the output of netstat -m ?



  • I had the same problem months ago, and now in a virtual machine on my house with just one computer as client and no service running, just the pure pfsense, the problem showed while I was trying to ping my physical machine.
    nmbcluster can't be the source of the problem because I increased, I saw no request for mbuf denied, and yet no success, top showed something strange for me, the process 258 "check_reload" took 100% WCPU on my CPU2 and 11:21 TIME. I though killing it would solve, but, nothing happened.
    Then I had a power problem, my pc rebooted, when the VM started again, the problem just dissapeared, but this is not the solution too, months ago I tried this and no success.



Log in to reply