From owner-freebsd-questions Sat Jun 10 14:40:19 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail.lagparty.org (lagparty.org [140.186.18.204]) by hub.freebsd.org (Postfix) with ESMTP id 4BA7537B630 for ; Sat, 10 Jun 2000 14:40:16 -0700 (PDT) (envelope-from greek@lagparty.org) Received: by mail.lagparty.org (Postfix, from userid 1022) id 8A5AB2FF8F; Sat, 10 Jun 2000 17:40:15 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.lagparty.org (Postfix) with ESMTP id 833ED2F463 for ; Sat, 10 Jun 2000 17:40:15 -0400 (EDT) Date: Sat, 10 Jun 2000 17:40:15 -0400 (EDT) From: "Kyle R. Green" To: freebsd-questions@freebsd.org Subject: UserPPP, natd, and Battle.net, oh my! 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 I recently changed my dialup router box from Debian Linux Frozen to FreeBSD. I've had a pleasant experience so far. cvsupping to the latest sources was incredibly easy, as was the process of making a new world and kernel. Additionally, the boot time's quite a bit better, too. I'm currently using UserPPP with its included NAT. I encountered problems, however, when I tried to play a game of Starcraft over battlenet. It said that it couldn't connect on UDP 6112, which is understandable, although it threw me for a loop momentarily, as Linux's IPMasq did this just fine. I'd heard (from FreeBSD users) that userppp's included NAT is somewhat less than capable, so I tried setting up natd with userppp, following the instructions for natd in _The_Complete_FreeBSD_. I had no luck at all--boxes on the internal network couldn't see outside. So I tried setting up kernel PPP, but that was even worse; I couldn't dial outside at all. I've googled, searched the FreeBSD documentation, and the mailing list archives to no avail. Is there something that I've missed? Regards, -- Kyle R. Green greek@lagparty.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message