From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 14 09:23:05 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37CBC16A4CE for ; Thu, 14 Apr 2005 09:23:05 +0000 (GMT) Received: from Neo-Vortex.net (203-217-87-46.dyn.iinet.net.au [203.217.87.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DC1A43D5E for ; Thu, 14 Apr 2005 09:23:04 +0000 (GMT) (envelope-from root@Neo-Vortex.net) Received: from localhost.Neo-Vortex.got-root.cc (Neo-Vortex@localhost.Neo-Vortex.got-root.cc [127.0.0.1]) by Neo-Vortex.net (8.13.1/8.12.10) with ESMTP id j3E9MxL2062640; Thu, 14 Apr 2005 19:23:00 +1000 (EST) (envelope-from root@Neo-Vortex.net) Date: Thu, 14 Apr 2005 19:22:59 +1000 (EST) From: Neo-Vortex To: Stephan Uphoff In-Reply-To: <1113439764.7457.55947.camel@palm> Message-ID: <20050414192002.I61191@Neo-Vortex.net> References: <1113439764.7457.55947.camel@palm> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Thu, 14 Apr 2005 12:28:39 +0000 cc: freebsd-hackers@freebsd.org cc: "M. Parsons" Subject: Re: Route/arp help? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Apr 2005 09:23:05 -0000 On Wed, 2005-04-13 at 16:38, M. Parsons wrote: > I was under the impression (but would need to check to make sure) that > all incoming packets are diverted to ng_pppoe when it is hooked into the > Ethernet interface. > > This would explain your problems. > > Can you try this without the interface being used for PPPOE? I have a single interface for PPPoE using netgraph and it connects to the modem, and other computers fine > > For the record, http://www.broadbandreports.com/faq/9693 is the page > > on how you access the line stats, and the MAC part is required for my > > modem. The only reason i could think of as to why it is required, is if its ip address isn't 10.0.0.1 as you think it is and for some strange reason it accepts ip packets as its own if the ethernet header points to its MAC address... try setting it to DHCP and see if you get an ip... else look up the manufacturer for the default ip and try a factory reset