From owner-freebsd-security Thu Jan 21 00:41:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA04640 for freebsd-security-outgoing; Thu, 21 Jan 1999 00:41:33 -0800 (PST) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from elmls02.ce.mediaone.net (elmls02.ce.mediaone.net [24.131.128.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA04633 for ; Thu, 21 Jan 1999 00:41:30 -0800 (PST) (envelope-from anthony@enteract.com) Received: from enteract.com (d152-173.ce.mediaone.net [24.131.152.173]) by elmls02.ce.mediaone.net (8.8.7/8.8.7) with ESMTP id CAA10575 for ; Thu, 21 Jan 1999 02:41:21 -0600 (CST) Message-ID: <36A6E700.CEC5418C@enteract.com> Date: Thu, 21 Jan 1999 02:36:16 -0600 From: Anthony Kim Organization: deus ex machina X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: zh-TW,en MIME-Version: 1.0 To: "security@FreeBSD.ORG" Subject: TCP port question IPFW Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm sort of annoyed...there is some IP who is constantly filling up my ipfw logs with TCP port 1719 attempts daily. The hours are late in the evening until around 2am, then it begins again shortly after 6pm (he or she must have come home from work and felt like bugging me). More recently I see requests for TCP port 1106 in my logs as well from them. A quick search on the web showed 1719 was h323gatestat. Can someone tell me what that is? I didn't find anything on TCP port 1106 either. Any info is greatly appreciated. Also, anyway I can track this person down? traceroute works but no hostname returns. Sorry if this isn't the correct forum. -- SYSADMIN(1) sysadmin takes care of everything, is generally harangued, must be supplied with coffee, chocolate, and alcohol in order to function properly, cannot be exposed to direct sunlight, and must not be allowed to have a life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message