From owner-freebsd-stable Sun Jan 30 19: 6: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89]) by hub.freebsd.org (Postfix) with ESMTP id 12FA914F8A for ; Sun, 30 Jan 2000 19:05:59 -0800 (PST) (envelope-from forrestc@workhorse.iMach.com) Received: from localhost (forrestc@localhost) by workhorse.iMach.com (8.9.3/8.9.3) with ESMTP id UAA18854; Sun, 30 Jan 2000 20:00:19 -0700 (MST) Date: Sun, 30 Jan 2000 20:00:15 -0700 (MST) From: "Forrest W. Christian" To: Coleman Kane Cc: Doug White , William Woods , freebsd-stable@FreeBSD.ORG Subject: Re: FW: DSL natd rules.... In-Reply-To: <20000130012354.A86581@evil.2y.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In my experiences and knowledge, the phone company's network does a lot of the > NAT and everything. Somewhere along the line your final output IP is bridged > with the ISP's IP to give to you. The NAT and routing is typically internal in > the phone company. Just to put my $0.02 in here. From experience with USWest DSL from both the customer and ISP end, I can guarantee that the phone company does very little to the ATM cells which go between the 675 and our equipment (ATM interface on a Cisco router). If we set the connection up PPP the client has to set it up PPP, if we set it up bridging, so does the client. We can (and do) at times push out a whole subnet bridged to the client end. I have yet to see anything which indicates that the telco does anything to the packets except take them in on the DSLAM and push them out our ATM port. - Forrest W. Christian (forrestc@imach.com) KD7EHZ ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message