From owner-freebsd-questions Fri Nov 2 10:39:52 2001 Delivered-To: freebsd-questions@freebsd.org Received: from kirk.sector14.net (66-61-170-163.mtc2.cox.rr.com [66.61.170.163]) by hub.freebsd.org (Postfix) with ESMTP id 3DBBF37B403 for ; Fri, 2 Nov 2001 10:39:47 -0800 (PST) Received: (from dgl@localhost) by kirk.sector14.net (8.11.3/8.11.3) id fA2Idfb26967 for freebsd-questions@freebsd.org; Fri, 2 Nov 2001 13:39:41 -0500 (EST) (envelope-from dgl) Date: Fri, 2 Nov 2001 13:39:40 -0500 From: Doug Lee To: freebsd-questions@freebsd.org Subject: Can I route TCP/UDP traffic by destination port? Message-ID: <20011102133940.K9714@kirk.sector14.net> Mail-Followup-To: Doug Lee , freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Bartimaeus Group 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 I live behind a cable modem, and Cox Communications appears to firewall ports 137-139, among others, both ways. It's fine with me that my ports 137-139 are protected from outside snooping (though I run my own firewall anyway), but I'd like the ability to send out requests on them and get answers back. I run a VPN to a machine which has no such out-of-my-hands firewall in its way... Can I possibly tell my FreeBSD box to send TCP/UDP traffic bound for ports 137-139 via a different route than all other traffic, and can I route responses back similarly (the other end of the VPN is also a FreeBSD box)? It would be really nice if I could do this without using the VPN as a pathway, but I think I could handle it either way. -- Doug Lee dgl@visi.com http://www.visi.com/~dgl Bartimaeus Group doug@bartsite.com http://www.bartsite.com "Determine that the thing can and shall be done, and then...find the way." - Abraham Lincoln To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message