From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 122F51381F3 for ; Thu, 5 Sep 2013 13:00:31 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5F208E0E78; Thu, 5 Sep 2013 13:00:21 +0000 (UTC) Received: from mail-we0-f169.google.com (mail-we0-f169.google.com [74.125.82.169]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 357ADE0E47 for ; Thu, 5 Sep 2013 13:00:19 +0000 (UTC) Received: by mail-we0-f169.google.com with SMTP id t60so1735203wes.14 for ; Thu, 05 Sep 2013 06:00:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=PDBqfKPWtBj625oDmG8qR4OzD6j+y0gzTCnVveSy4MU=; b=TOYhDvnn3BuouJtuI6OkqyIDk+qNJLR2g0u9vBTUuYVjrT0WnZm70V4M2VT0jJekkE eKrPjod3qobaM6zlwtLIPR/456mP2oSgEQAl0EG44grhWPmkEgrJNwcpvFcQRSEKlM3R fGukZ/e74jWn9z3hG1avvj4zrEAdzGr6U8Eh+101MLgHWE/4k3jIV/pUjAcsU6fXjhg6 aKs2LJJCmg+fr5y2IGEbjkl1qDIXPqHAcAghux0QhP/gMFE8AfbSzhG/0Zx0zZPRP+o6 7ozClWPcfKfDsRQl1bm/tfrXs+ikhN0WJMjEcdOXhbEJoxyjL0YVFmnnDXx01LGF4xF/ vYTQ== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.195.13.45 with SMTP id ev13mr6798249wjd.20.1378386018878; Thu, 05 Sep 2013 06:00:18 -0700 (PDT) Received: by 10.194.93.199 with HTTP; Thu, 5 Sep 2013 06:00:18 -0700 (PDT) In-Reply-To: References: <52238823.9060008@gmail.com> <201309012010.22227.michaelkintzios@gmail.com> Date: Thu, 5 Sep 2013 06:00:18 -0700 Message-ID: Subject: Re: [gentoo-user] Re: Can't ping remote system From: Grant To: Gentoo mailing list Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: f3e80420-5788-4261-b3f4-ad3382713ecb X-Archives-Hash: eab4c90247f25909de82a7f60d32994b >> I called AT&T and they say the Westell 6100 modem/router I have will >> not respond to pings. They said I could put it into bridged mode and >> set up PPPoE on the computer connected to it which would cause ICMP >> packets to pass through to the computer. Would you guys recommend >> that? For sure I won't attempt this until I'm in the same room as the >> device. > > You'll lose the router functionality doing that. If you need to connect > other machines to it, then it will only be able to act as a switch, meaning > that everything you connect to it will either need to be on the same subnet, > or you need to configure another machine to act as a router if you need to > connect different subnets. And the machine will also need to be always on > in order to provide internet connectivity to other machines, since it will > be the one that talks to the ADSL modem. > > You'll also be losing NAT, which is quite nice for redirecting traffic on > specific ports to whatever machine you want. As with the router > functionality, you will need to configure a Linux machine to do NAT if you > want to keep having that feature. > > There's also the issue of not being able to set up a firewall on the router > itself anymore. You can still do that on the target machine itself, of > course, but there's the issue of creating a firewall on the machine you want > to protect, which is not optimal (the analogy here being that if you want to > protect something, you put it behind a wall rather than hardening it; even > if it's hardened, it still gets hit.) > > Or, you might not care about any of the above, in which case using the > device as a simple ASDL modem (which is what bridging means) will work just > fine. That's actually exactly what I want. The Gentoo system connected to the single-port Westell modem/router is already set up as a router/firewall and it is the one doing NAT. Thank you for the run-down. Now I feel like I know exactly what this change will mean. - Grant