Date: Fri, 26 Oct 2007 10:31:40 +0300 From: Nikos Vassiliadis <nvass@teledomenet.gr> To: freebsd-net@freebsd.org Cc: Barney Wolff <barney@databus.com> Subject: Re: pppoa connection Message-ID: <200710261031.40592.nvass@teledomenet.gr> In-Reply-To: <DD2BA22E-523B-4751-9417-E2DA0DFF1157@tinker.com> References: <A5EB0F83-8C40-4014-84E0-5C5661885661@tinker.com> <20071026052932.GA72917@pit.databus.com> <DD2BA22E-523B-4751-9417-E2DA0DFF1157@tinker.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 26 October 2007 10:06:30 Kim Shrier wrote: > I do have a fixed IP address. I have tried using their modem > as a router and assigned my IP address to the modem. This forces > me to use the NAT facility in the modem and it keeps dropping > my ssh sessions. I have also seen the modem drop the pppoa > connection and not be able to reestablish it until I reboot the > modem. > > The only thing this fine piece of equipment has been able to do > reliably is maintain the virtual circuit to the ISP. Anything > at a higher level in the protocol stack is too flakey. Hence, > I just want it to act as the most stupid of pipes between me > and the ISP. Yes, this is a familiar situation:) Most of the time these NAT devices are configured for non-interactive protocols doing bulk transfers , so ssh having long periods of inactivity suffers... And even these is flakey, as you said. > > Other people successfully use this modem to connect to their ISP > when the ISP accepts pppoe connections and the modem is configured > as a bridge. Unfortunately, my ISP doesn't support pppoe, only > pppoa. The only way to do PPPoA is to have a device that does the DSL and ATM layers and handles the rest to FreeBSD.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200710261031.40592.nvass>