From owner-freebsd-current@FreeBSD.ORG Mon Jan 3 19:12:46 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2000116A4CE for ; Mon, 3 Jan 2005 19:12:46 +0000 (GMT) Received: from smtps-vbr2.xs4all.nl (smtps-vbr2.xs4all.nl [194.109.24.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EA5743D2F for ; Mon, 3 Jan 2005 19:12:45 +0000 (GMT) (envelope-from mhellwig@xs4all.nl) Received: from [10.0.0.182] (xinagnet.xs4all.nl [80.126.243.229]) (authenticated bits=0)j03JChtN099826 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 3 Jan 2005 20:12:44 +0100 (CET) (envelope-from mhellwig@xs4all.nl) Message-ID: <41D9992C.4080401@xs4all.nl> Date: Mon, 03 Jan 2005 20:12:44 +0100 From: "Martin P. Hellwig" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041111 X-Accept-Language: en-us, en MIME-Version: 1.0 Cc: freebsd-current@freebsd.org References: <002401c4f1c4$fc7ab240$6500000a@asdf> In-Reply-To: <002401c4f1c4$fc7ab240$6500000a@asdf> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by XS4ALL Virus Scanner Subject: Re: Can't get rid of IPv6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jan 2005 19:12:46 -0000 Richard Cadwalader wrote: > > I've tried 4 other browsers. Even ping takes about 90 seconds to > return anything. > > I can't show you my kernel config or anything else, because I can't > even send/recieve email. That is name based, of course, so forget it. > I can't browse the net unless I know the host's IP and all the links > are relative and the host allows http req's by IP....otherwise I would > have set up Samba and wrote those files to the windows HDD so I can > share that with everyone, but I can't. > > The one thing I didn't try, and didn't think of it till just now is I > never actually tried IPv6 support on the card using sysinstall. Maybe > the all the apps are sending ip6 to the card, and the card isn't > telling the app to use ip4 because the card doesn't know what it's > getting in the first place...could that be it? > > Wild guess but could you post your netstat -r output, perhaps there is something interesting in there. -- mph