Just a quick idea. It would probably be useful to include a global 'disable/enable IPv6' option in the installer. Having IPv6 enabled causes Mozilla DNS lookups to take ages in some areas - depends on DNS servers involved (basically it has to wait for IPv6 resolution to timeout). This can be achieved by 'alias net-pf-10 off' in /etc/modprobe.conf or by physically removing the IPv6 addresses from the interfaces (ip addr del ::1/128 dev lo; ip addr del <something> dev eth0;)
Comments?
Cheers, MaZe.
Also in FC3? I thougth this problem went away when FC3 came (comes).
lør, 30.10.2004 kl. 14.24 skrev Maciej Żenczykowski:
Just a quick idea. It would probably be useful to include a global 'disable/enable IPv6' option in the installer. Having IPv6 enabled causes Mozilla DNS lookups to take ages in some areas
- depends on DNS servers involved (basically it has to wait for IPv6
resolution to timeout). This can be achieved by 'alias net-pf-10 off' in /etc/modprobe.conf or by physically removing the IPv6 addresses from the interfaces (ip addr del ::1/128 dev lo; ip addr del <something> dev eth0;)
Comments?
Cheers, MaZe.
Don't know about FC3, was just performing some maintenance routine work on an FC2 box and ran across this again. Don't currently have the HDD space nor the bandwidth to give FC3 a test drive, especially seeing how rapidly the ISOs are changing lately (nb. why no jigdo releases?).
Anyway seeing how this is trivial to fix, and not being sure whether it was fixed or not, decided to bring this up to the attention of the list.
Cheers, MaZe.
On Sat, 30 Oct 2004, Kyrre Ness Sjobak wrote:
Also in FC3? I thougth this problem went away when FC3 came (comes).
l?r, 30.10.2004 kl. 14.24 skrev Maciej Żenczykowski:
Just a quick idea. It would probably be useful to include a global 'disable/enable IPv6' option in the installer. Having IPv6 enabled causes Mozilla DNS lookups to take ages in some areas
- depends on DNS servers involved (basically it has to wait for IPv6
resolution to timeout). This can be achieved by 'alias net-pf-10 off' in /etc/modprobe.conf or by physically removing the IPv6 addresses from the interfaces (ip addr del ::1/128 dev lo; ip addr del <something> dev eth0;)
Comments?
Cheers, MaZe.
I did not experience this while using epiphany in t2 - or epiphany (or put-any-other-browser-here) in fc2. but mozilla has always had this issue...
lør, 30.10.2004 kl. 15.32 skrev Maciej Żenczykowski:
Don't know about FC3, was just performing some maintenance routine work on an FC2 box and ran across this again. Don't currently have the HDD space nor the bandwidth to give FC3 a test drive, especially seeing how rapidly the ISOs are changing lately (nb. why no jigdo releases?).
Anyway seeing how this is trivial to fix, and not being sure whether it was fixed or not, decided to bring this up to the attention of the list.
Cheers, MaZe.
On Sat, 30 Oct 2004, Kyrre Ness Sjobak wrote:
Also in FC3? I thougth this problem went away when FC3 came (comes).
l?r, 30.10.2004 kl. 14.24 skrev Maciej Żenczykowski:
Just a quick idea. It would probably be useful to include a global 'disable/enable IPv6' option in the installer. Having IPv6 enabled causes Mozilla DNS lookups to take ages in some areas
- depends on DNS servers involved (basically it has to wait for IPv6
resolution to timeout). This can be achieved by 'alias net-pf-10 off' in /etc/modprobe.conf or by physically removing the IPv6 addresses from the interfaces (ip addr del ::1/128 dev lo; ip addr del <something> dev eth0;)
Comments?
Cheers, MaZe.
On Sat, 2004-10-30 at 14:46 +0200, Kyrre Ness Sjobak wrote:
Also in FC3? I thougth this problem went away when FC3 came (comes).
It was still present in FC3-RC1, and I am trying to install RC5 now to see whether it has been corrected. I hugely doubt it, though.
Cheers,
On Sat, 2004-10-30 at 14:24 +0200, Maciej Żenczykowski wrote:
It would probably be useful to include a global 'disable/enable IPv6' option in the installer.
In theory, placing "NETWORKING_IPV6=no" in /etc/sysconfig/network should disable IPv6 and is documented by the initscripts docs as being the "correct" way to do it. However, it does not work, since apparently there is some code somewhere that does not check for this variable and loads the IPv6 module anyway.
However, I did file Bug #125587 on this issue (originally against FC2, on June 8th), and I have not seen any action taken on it. At the very least, I think that adding that line to the file would have been an easy change to make; then debugging why it does not have the desired effect could have been performed later.
Cheers,
-
Kyrre Ness Sjobak -
Maciej Żenczykowski -
Rodolfo J. Paiz