From owner-freebsd-questions Mon Jun 2 05:17:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA16066 for questions-outgoing; Mon, 2 Jun 1997 05:17:56 -0700 (PDT) Received: from emout14.mail.aol.com (emout14.mx.aol.com [198.81.11.40]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA16060 for ; Mon, 2 Jun 1997 05:17:49 -0700 (PDT) From: Almondale@aol.com Received: (from root@localhost) by emout14.mail.aol.com (8.7.6/8.7.3/AOL-2.0.0) id IAA07821 for freebsd-questions@freebsd.org; Mon, 2 Jun 1997 08:14:37 -0400 (EDT) Date: Mon, 2 Jun 1997 08:14:37 -0400 (EDT) Message-ID: <970602081435_-895257799@emout14.mail.aol.com> To: freebsd-questions@freebsd.org Subject: Re: IP Masquerading Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The whole main issue is that the "ping" command will probably *not* work under most forms of IP masquerading/aliasing (don't know about NAT). It's sort of interesting just what commands do and don't work when you are working with "virtual private networks" as microsoft calls them. I think in short it would be neat if this (NAT or ppp -alias) code could be put on the ROM chip of a NIC! In a message dated 97-06-01 19:19:33 EDT, you write: << I would have to see what your routing table looks like to help more, but you probably will have this aced by the time you get this and could send it along. Like I said, I am not familiar with fBSD's ways (why I read this list's mail), but have seen more than one PPP host handle forwarding for a LAN. The most common problem I recall is not setting the forwarding for the LAN (Ethernet card) to pass things on via the PPP device. If you can ping the PPP device from a LAN client, but not get past that, you may find the problem there. Also, if you can dial-in to the ISP from a client and ping the PPP host, but no further, the problem is in the other direction (not what you described here). >>