From owner-freebsd-questions@FreeBSD.ORG Mon Feb 22 19:18:52 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7193B1065679 for ; Mon, 22 Feb 2010 19:18:52 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 2BC958FC1B for ; Mon, 22 Feb 2010 19:18:51 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Njdnm-00056G-H0 for freebsd-questions@freebsd.org; Mon, 22 Feb 2010 20:18:42 +0100 Received: from pool-70-21-13-66.res.east.verizon.net ([70.21.13.66]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 22 Feb 2010 20:18:42 +0100 Received: from nightrecon by pool-70-21-13-66.res.east.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 22 Feb 2010 20:18:42 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Michael Powell Followup-To: gmane.os.freebsd.questions Date: Mon, 22 Feb 2010 14:17:57 -0500 Lines: 27 Message-ID: References: <478167.77662.qm@web113819.mail.gq1.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: pool-70-21-13-66.res.east.verizon.net Subject: Re: Limiting Port X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Feb 2010 19:18:52 -0000 Alex Terente wrote: > Hi, > > I have a problem with my FreeBSD system, i have installed a gameserver on > it and after a period of time, the port 11002 (login port) is closed. What > i can do to resolve this? > Two things spring to mind at first, possibly a way to get started. First, establish that it is not the game server relinquishing the port. This is unlikely but it ought to get eliminated from consideration. sockstat -4l will tell you what is listening to which ports. Next time it gets "closed" take a quick look at this and ensure the game server is actually still listening to this port. If it is not it is most likely a configuration detail relevant to the game server. Second, this sounds a lot like a NAT session timing out from inactivity. If such a situation should be the case it is possible to design a rule specific so the ports' traffic can bypass NAT and run "straight-through". If the first thingy from above gets eliminated this is where I'd look next. As to exactly how you would go about tailoring such a rule would depend upon the syntax of whichever firewall you are using. -Mike