"No buffer space available" problem. FreeBSD 4.7, mpd 3.17

From: Максим Чеусов (chmax_at_kras.ru)
Date: 05/06/04

  • Next message: Lukasz Stelmach: "Re: if_stf bug/feature" 
    Date: Thu, 6 May 2004 15:43:19 +0800
To: freebsd-net@freebsd.org

    Hello all!
    A couple days ago i've got next problem with my ISP (before everything
    were ok). When connection to the VPN server is established then I can't
    ping anything through the tunel even VPN server (192.168.10.1):

    64 bytes from 192.168.10.1: icmp_seq=503 ttl=64 time=0.634 ms
    64 bytes from 192.168.10.1: icmp_seq=504 ttl=64 time=0.689 ms
    64 bytes from 192.168.10.1: icmp_seq=505 ttl=64 time=0.645 ms
    64 bytes from 192.168.10.1: icmp_seq=506 ttl=64 time=0.664 ms
    ping: sendto: Resource deadlock avoided
    ping: sendto: Resource deadlock avoided
    ping: sendto: No buffer space available
    ping: sendto: No buffer space available
    ping: sendto: No buffer space available
    ping: sendto: No buffer space available
    ping: sendto: No buffer space available
    ping: sendto: No buffer space available
    ping: sendto: No buffer space available

    In moment when mdp connetction established ping response is over.
    There is tcpdump -i ng0:
    tcpdump: listening on ng0
    12:23:40.489990 192.168.100.102 > 192.168.10.1: icmp: echo request
    12:23:41.499975 192.168.100.102 > 192.168.10.1: icmp: echo request
    12:23:42.509985 192.168.100.102 > 192.168.10.1: icmp: echo request
    12:23:43.519997 192.168.100.102 > 192.168.10.1: icmp: echo request
    12:23:44.530011 192.168.100.102 > 192.168.10.1: icmp: echo request
    12:23:45.540022 192.168.100.102 > 192.168.10.1: icmp: echo request
    12:23:46.550046 192.168.100.102 > 192.168.10.1: icmp: echo request
    12:23:47.560053 192.168.100.102 > 192.168.10.1: icmp: echo request
    12:23:48.570068 192.168.100.102 > 192.168.10.1: icmp: echo request
    12:23:49.580084 192.168.100.102 > 192.168.10.1: icmp: echo request
    12:23:50.590127 192.168.100.102 > 192.168.10.1: icmp: echo request
    12:23:51.600118 192.168.100.102 > 192.168.10.1: icmp: echo request
    12:23:52.610151 192.168.100.102 > 192.168.10.1: icmp: echo request
    12:23:53.620149 192.168.100.102 > 192.168.10.1: icmp: echo request

    Seems like nothing can get through the tunnel.
    netstat -m:
    196/1328/3328 mbufs in use (current/peak/max):
            193 mbufs allocated to data
            3 mbufs allocated to packet headers
    192/236/832 mbuf clusters in use (current/peak/max)
    1304 Kbytes allocated to network (52% of mb_map in use)
    652 requests for memory denied
    15 requests for memory delayed
    29 calls to protocol drain routines

    Looks like no any problem here.
    I'v red someting similar about Cisco VPN servers, but solution that
    were given did'n help me.

    ifconfig:
    xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
            options=3<rxcsum,txcsum>
            inet 192.168.10.12 netmask 0xffffff00 broadcast 192.168.10.255
            ether 00:01:02:ca:0c:24
            media: Ethernet autoselect (100baseTX <full-duplex>)
            status: active
    fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
            inet 192.168.0.10 netmask 0xffffffc0 broadcast 192.168.0.63
            ether 00:a0:c9:69:91:8a
            media: Ethernet autoselect (100baseTX <full-duplex>)
            status: active
    lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
    faith0: flags=8002<BROADCAST,MULTICAST> mtu 1500
    lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
            inet 127.0.0.1 netmask 0xff000000
    ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
    sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552
    ng0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> mtu 1500
            inet 192.168.100.102 --> 192.168.10.1 netmask 0xffffffff

    >mpd.comf:
    default:
            load vpn
    vpn:
            new -i ng0 ciscovpn pptp192
            set bundle authname "*******"
            set ipcp ranges 192.168.100.102 192.168.10.1
            set iface up-script /usr/local/etc/mpd/iface-up.sh
            load vpnpptp
            open
    vpnpptp:
            set bundle disable compression
    # set bundle no crypt-reqd

            set bundle enable compression
            set ccp yes mppc
            set ccp yes mpp-e40
            set ccp yes mpp-e128
            set bundle enable crypt-reqd
            set ccp yes mpp-stateless

            set iface idle 0
            set ipcp disable vjcomp
            set ipcp enable req-pri-dns req-sec-dns
            set link max-redial 1
            set link keep-alive 0 0
            set link disable pap chap
            set link disable acfcomp protocomp
    > end

    >mpd.links
    pptp192:
            set link type pptp
            set pptp peer 192.168.10.1
            set pptp enable originate outcall
    > end

    >iface-up.sh
    #!/bin/sh

    iface=$1
    proto=$2
    localip=$3
    remoteip=$4
    vpn_private_ip=192.168.10.1

    ifconfig $iface $proto $localip $vpn_private_ip netmask 0xffffffff
    ifconfig $iface mtu 1500
    route flush
    route add default -interface $iface
    > end

    And there is nothing strange in mpd.log also
    As far as I know on the ISP side is mdp-3.17 and FreeBSD too.
    And there is no any problems whith XP box.

    _______________________________________________
    freebsd-net@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-net
    To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"

  • Next message: Lukasz Stelmach: "Re: if_stf bug/feature"

    Relevant Pages