From owner-freebsd-questions Tue Aug 6 14:45:30 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 95FDB37B410 for ; Tue, 6 Aug 2002 14:45:21 -0700 (PDT) Received: from nemesis.systems.pipex.net (nemesis.systems.pipex.net [62.241.160.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id A293643E65 for ; Tue, 6 Aug 2002 14:45:20 -0700 (PDT) (envelope-from stacey@Demon.vickiandstacey.com) Received: from Demon (81-86-129-77.dsl.pipex.com [81.86.129.77]) by nemesis.systems.pipex.net (Postfix) with ESMTP id 36539160003FD; Tue, 6 Aug 2002 22:42:21 +0100 (BST) Subject: Re: /kernel: drop session, too many entries From: Stacey Roberts Reply-To: sroberts@dsl.pipex.com To: root@unixhideout.com Cc: FreeBSD Questions In-Reply-To: <2599.192.168.1.10.1028669060.squirrel@email.unixhideout.com> References: <1028666145.38776.66.camel@Demon.vickiandstacey.com> <2599.192.168.1.10.1028669060.squirrel@email.unixhideout.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-NUUU/KeQ9pOn+QqWB3mt" X-Mailer: Ximian Evolution 1.0.8 Date: 06 Aug 2002 22:43:00 +0100 Message-Id: <1028670181.38776.89.camel@Demon.vickiandstacey.com> Mime-Version: 1.0 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --=-NUUU/KeQ9pOn+QqWB3mt Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi Mike, Hmmm.., your mentioning ipfw *does* kinda make sense here. If anything, I figure it might be the fact that the firewall has processed (denied, for instance) a certain number of packets at a certain rule number, and has actually decided not to process anymore as the connection has already been assessed and (in the above case) a decision (deny) has be made. The end of this is, that there is no sense in continued logging of this event, hence the message. The snag in this theory is the lack of a firewall rule number associated with the message, though. Logical, but by no means authoritative! I'd like to get to the bottom of this myself, and do hope that a more learned ipfw person might comment. Stacey On Tue, 2002-08-06 at 22:24, Mike wrote: > It's due to IPFW rules. I know that cause i just configged it and im > getting those errors, but I am not sure whats it means either. when you > find out please send me the email. >=20 > > Hi, > > I've been noticing the following in /var/log/messages recently. I > > don't know what they refer to, nor if I should be concerned about them. > > > > Aug 6 13:01:11 /kernel: drop session, too many entries > > Aug 6 13:01:19 /kernel: drop session, too many entries > > > > Here's my uname: > > # uname -rp > > 4.6-STABLE i386 > > # > > > > I'd appreciate someone in the know to shed some light on these messages= , > > please. > > > > Stacey > > > > -- > > Stacey Roberts > > B.Sc (HONS) Computer Science >=20 >=20 >=20 > ----------------------------------------- > Free email that kicks ass from UnixHideout > "The UnixHideout network" > http://www.unixhideout.com/ >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message --=20 Stacey Roberts B.Sc (HONS) Computer Science --=-NUUU/KeQ9pOn+QqWB3mt Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.8 iQEVAwUAPVBC4pvQeubckvvXAQGjrQf/QbLdoBGAH2VP74Yixk/eAbkX2c0Y6dh3 3EkzH1BgZMyyaqQi0hyXW5VTQFyD2izuZyAfvUR8JOV9zb9C06ZFpstBBPGzQheA 1c7jcY8mW2zy3omC/17oRU43yTMcyN2OL1R2CggEkqmvaWT/YH4ZRB/aBFVPGbfT 2m7TnYOIl1r7CXVO9LteuPseqX3G9o4sw2tpKCuPA7URYZSxEhBRFLF6rpQvWO6f BojO/tR2s6FaaP6TcUCE4UNu/zHtHFQGdz6ypfzRwYnnQ7wV4cZPDgF/qhGweQPG PZ13W9Iy/c1j7u6NuJw3FyOKdxNXsSjLhTXJSh2ieLxKaD8/SBgp5Q== =ilHo -----END PGP SIGNATURE----- --=-NUUU/KeQ9pOn+QqWB3mt-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message