From owner-freebsd-security Wed Nov 14 6:57:52 2001 Delivered-To: freebsd-security@freebsd.org Received: from ns2.esnx.net (200-161-145-69.dsl.telesp.net.br [200.161.145.69]) by hub.freebsd.org (Postfix) with SMTP id 4A2C637B405 for ; Wed, 14 Nov 2001 06:57:45 -0800 (PST) Received: (qmail 58560 invoked from network); 14 Nov 2001 14:57:49 -0000 Received: from unknown (HELO host) (10.6.49.8) by ns2.esnx.net with SMTP; 14 Nov 2001 14:57:49 -0000 From: "Marcos Martinelli" To: Subject: RE: listrl0: no memory for tx Date: Wed, 14 Nov 2001 12:57:45 -0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-reply-to: <3BF27C9E.8700B070@centtech.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Importance: Normal Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This means that your network memory buffer is not enough to your network traffic. if you are using FreeBSD, put in your /boot/loader.conf : kern.ipc.nmbclusters="8192" kern.ipc.nmbufs="32768" you can see if the problem is it with the command: netstat -m > [root@pituba root]# netstat -m > 1650/2000/4096 mbufs in use (current/peak/max): > 1469 mbufs allocated to data > 124 mbufs allocated to packet headers > 57 mbufs allocated to socket names and addresses > 1024/1024/1024 mbuf clusters in use (current/peak/max) > 2548 Kbytes allocated to network (82% of mb_map in use) > 8436 requests for memory denied > 71 requests for memory delayed > 0 calls to protocol drain routines Its nothing related to hardware problem -----Original Message----- From: owner-freebsd-security@FreeBSD.ORG [mailto:owner-freebsd-security@FreeBSD.ORG]On Behalf Of Eric Anderson Sent: Wednesday, November 14, 2001 11:16 AM To: Sven Giersig Cc: freebsd-security Subject: Re: listrl0: no memory for tx I have seen similar messages on an NFS server that was extremely overloaded. I did a few sysctl tweaks to the tcp window sizes and such, and a few other things, so the machine could keep up with the hundreds of P4's beating the crud out of it. If it's your firewall, I'd be looking at it with a fine toothed comb right now. Eric Sven Giersig wrote: > > Hello List, > since the last night I have entries in my syslog like > listrl0: no memory for tx ... (repeated) > rl0 is the internal interface on a fw-machine - and should have had less traffic at night! > > does it mean > - I have to add more memory? > - my NIC is broken? > - cable? > > thanks for any hints, > Sven > > -- > Sven Giersig | > mailto: smg@weird.dnsalias.org | Unix Inter-Networking > mobile: +49-172-8049514 | Directory Services > https://weird.dnsalias.org/~smg | > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message -- ------------------------------------------------------------- Eric Anderson anderson@centtech.com Centaur Technology No single raindrop believes it is to blame for the flood. ------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message