Re: Performance/lockup issues with FreeBSD as a router

From: T.D.Wipnet (H.M.) (tec_at_mega.net.br)
Date: 05/26/05

  • Next message: Peter Kieser: "Re: Performance/lockup issues with FreeBSD as a router (followup)" 
    To: freebsd-performance@freebsd.org
Date: Thu, 26 May 2005 18:14:59 -0300

    On Thursday 26 May 2005 14:47, Peter Kieser wrote:
    > however I'm currently running into issues where one, or both of the
    > NICs will stop transmitting traffic. When I go onto the machine,
    > and try to ping something I get "No buffer space available"
    >

    stopping transmitting anything or only your ping tries?

    > net.inet.ip.rtexpire=1800
    > net.inet.ip.rtminexpire=1800
    > kern.maxfiles=32768
    > kern.maxfilesperproc=32768
    > kern.ipc.somaxconn=32767
    > net.inet.tcp.sendspace=256000
    > net.inet.tcp.recvspace=256000
    > kern.ipc.maxsockbuf=2097152
    > net.inet.ip.fastforwarding=1
    > net.inet.tcp.rfc1323=1
    > net.link.ether.inet.max_age=600
    > net.inet.tcp.msl=7500
    > net.inet.ip.fw.dyn_udp_lifetime=10
    > net.inet.ip.fw.dyn_buckets=1024
    >
    > And here's my /boot/loader.conf:
    >
    > kern.ipc.maxsockets="163840"
    > kern.maxusers="2048"
    >

    if your pc is really only a router you probably have a lot of
    unessessary stuff in here, your extremly high settings for maxuser,
    maxfiles and somaxcons is somewhat useless here and could slow your
    machine down, anyway, this is not a p-III 600 with 128MB of ram isn't
    it?

    "no buffer space available" appears often when the buffer is used so
    that means that if your connections are bad the buffer gets filled
    because if your connections are good why the buffer should be used? -
    then it goes straight out ... I guess that probably your Nics,
    cables, hubs or even the "where it goes" may have a problem

    Hans 

    -- 
WIPNET Telecom Ltda. http://wip.mega.net.br
http://wip.mega.net.br/tec.asc
_______________________________________________
freebsd-performance@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-performance
To unsubscribe, send any mail to "freebsd-performance-unsubscribe@freebsd.org"
  • Next message: Peter Kieser: "Re: Performance/lockup issues with FreeBSD as a router (followup)"

    Relevant Pages

    • Re: send-receive using CSocket
      ... > desktop image & sending it from server to client " i convert it to DIB ... > strong and reliable send-receive code?? ... Is your image a constant size buffer? ... What kind of package are you transmitting across the buffer? ...
      (microsoft.public.vc.mfc)
    • Re: A stupid question...
      ... I know about the buffer issues - I've had that on all my servers, ... nowadays it's routine to up that to atleast 4x the default. ... > buffer space, etc. ... RealTek nics are ...
      (freebsd-stable)
    • Re: send-receive using CSocket
      ... Be aware that if you send a buffer, that the receive does not receive the same information ... >> strong and reliable send-receive code?? ... Or are you also transmitting height, width, color ... MVP Tips: http://www.flounder.com/mvp_tips.htm ...
      (microsoft.public.vc.mfc)
    • Re: write() only sends 16 chars to serial port?
      ... serial driver fills the tx FIFO with 16 bytes and starts it ... transmitting. ... but I'll probably add the tcdrain for safety. ... the buffer when I do it, but I don't know if that's guaranteed ...
      (comp.os.linux.development.apps)
    • Re: kern/95665: [if_tun] "ping: sendto: No buffer space available" with TUN interface (easily reprod
      ... Subject: kern/95665: "ping: sendto: No buffer space available" with TUN interface ... This is fairly common on slow or dodgy NICs, ... You should see a larger number of packets make it through. ...
      (freebsd-net)