Date: Thu, 10 Apr 2003 22:44:48 +0900 From: Hiroharu Tamaru <tamaru@myn.rcast.u-tokyo.ac.jp> To: "Christoph P. Kukulies" <kuku@physik.rwth-aachen.de> Cc: freebsd-gnome@freebsd.org Subject: Re: mozilla 1.3,2 cannot access IPv6 addressed host via IPv4 Message-ID: <sa6y92iv54f.wl@gin.myn.rcast.u-tokyo.ac.jp> In-Reply-To: <20030409154421.GA6527@gilberto.physik.rwth-aachen.de> References: <sa63ckrwwu6.wl@gin.myn.rcast.u-tokyo.ac.jp> <E18m13u-00068y-00@roam.psg.com> <20030409154421.GA6527@gilberto.physik.rwth-aachen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, gnome@ CC:'ed 'causs it's the maintainer of the port. At Wed, 9 Apr 2003 17:44:21 +0200, Christoph P. Kukulies wrote: > > On Wed, Apr 09, 2003 at 11:48:33PM +0900, Hiroharu Tamaru wrote: > > I updated mozilla port from 1.2.1_1,2 to 1.3,2 and realized that > > it fails to reach some sites. It just says "Done" in the status bar > > and nothing happens. > > > > It seems to be those servers that have both IPv4 and IPv6 address that > > are the victims, eg: www.jp.freebsd.org, www.kame.net. > > > > I am running FreeBSD 4.8-RC. I have IPv6 lladdr assigned to my > > network interfaces but do not have IPv6 link to the Internet. > > > > Am I the only one seeing this problem? > > The problem has brought up by me in this list already before, > only not under this aspect. > > The workaround was, so far, to turn off IPV6 in the kernel. > > I admit, not a beautiful solution. I posted an excerpt (sample program > that had been posted to bugzilla on mozilla.org under some bug report) > > Look into this list under posts this and last week. Indeed you did. I saw 1.4 in the subject and didn't read it carefully then. I also found the same issue reported on gnome@ http://www.freebsd.org/cgi/getmsg.cgi?fetch=1019068+0+/usr/local/www/db/text/2003/freebsd-gnome/20030223.freebsd-gnome OK. I brought it up to users-jp@jp.freebsd.org ML and someone pointed out that it was assigned a bugzilla-JP id of 2967 http://bugzilla.mozilla.gr.jp/show_bug.cgi?id=2967 and forwarded to bugzilla http://bugzilla.mozilla.org/show_bug.cgi?id=192696 http://bugzilla.mozilla.org/show_bug.cgi?id=186745 He told me a fix is already committed to the trunk of Mozilla repo. also, reading through bugzilla 186745, the patch, http://bugzilla.mozilla.org/attachment.cgi?id=112566&action=view is said to work around the problem, with some impact on IPv6-only users. I tried the patch, and it seems to work for me. Could someone commit the above mentioned one line patch to the mozilla port? -- Hiroharu Tamaru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?sa6y92iv54f.wl>