From owner-freebsd-questions Sun Oct 29 12:42:40 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail.gelrevision.nl (mail.gelrevision.nl [195.86.58.10]) by hub.freebsd.org (Postfix) with ESMTP id 022E337B479 for ; Sun, 29 Oct 2000 12:42:38 -0800 (PST) Received: from localhost [195.86.231.176] by mail.gelrevision.nl with ESMTP (SMTPD32-6.00) id AB6C934D0072; Sun, 29 Oct 2000 21:41:16 +0100 Date: Sun, 29 Oct 2000 21:42:16 +0100 (CET) From: Maarten van Schie To: cjclark@alum.mit.edu Cc: questions@FreeBSD.ORG Subject: Re: funproxy In-Reply-To: <20001029121312.R75251@149.211.6.64.reflexcom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I just saw I made a search for 'funproxy' instead of 'funkproxy'... So.. sockstat tells me it's scr-bx which is using the port for internal purposes, I guess. scr-bx is the command to retach BitchX to a ttyv after detachment. USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS AnEra scr-bx 1325 3 tcp4 127.0.0.1:1506 127.0.0.1:1505 AnEra BitchX-1 1322 0 tcp4 127.0.0.1:1505 127.0.0.1:1506 AnEra BitchX-1 1322 1 tcp4 127.0.0.1:1505 127.0.0.1:1506 AnEra BitchX-1 1322 2 tcp4 127.0.0.1:1505 127.0.0.1:1506 AnEra BitchX-1 1322 3 udp4 *:* *:* AnEra BitchX-1 1322 4 tcp4 192.168.1.5:1502 194.119.238.162:66 AnEra BitchX-1 1322 7 tcp4 127.0.0.1:1505 127.0.0.1:1506 I've never seen it behave like this, don't use it much but still, though I netstat a couple of times a day. Thanx, Maarten. On Sun, 29 Oct 2000, Crist J . Clark wrote: > On Sun, Oct 29, 2000 at 08:37:31PM +0100, Maarten van Schie wrote: > > I'm running 4.1.1-STABLE as of last night and everything works just fine. > > Except for one thing: > > > > Proto Recv-Q Send-Q Local Address Foreign Address (state) > > tcp4 0 0 localhost.funkproxy localhost.1506 ESTABLISHED > > tcp4 0 0 localhost.1506 localhost.funkproxy ESTABLISHED > > > > I found that this port is used by some piece of windoze software which can > > remotely administer winboxes.... > > > > > > I certainly do not use it since I do not windoze and I can't figure out > > why my system could or would be using this established connection. > > > > Any help will be appreciated, > > Do a 'sockstat' to see what process is using that connection. It > almost surely has nothing to do with 'funkproxy.' If you check the > numbers, funkproxy is port 1505 so that connection is between ports > 1505 and 1506. It is likely those numbers just happened to be next in > line whenever the process using them needed to make connection. > -- > Crist J. Clark cjclark@alum.mit.edu > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message