Dear Alexander, Here is Wojox's fix (which worked perfectly and is continuing to work): 1. Type about:config in the address bar, press Enter. 2. Find network.dns.disableIPv6 in the list. 3. Right-click -> Toggle. Set to true 4. Restart your Mozilla application and try again. I do not know how to add a workaround to the bug description. Can you tell me how to do it? For < ip -f inet6 link > I get: 1: lo: mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: mtu 1500 qdisc pfifo_fast state DOWN qlen 1000 link/ether 00:1d:72:2b:73:90 brd ff:ff:ff:ff:ff:ff 3: irda0: mtu 2048 qdisc noop state DOWN qlen 8 link/irda 00:00:00:00 brd ff:ff:ff:ff 4: wmaster0: mtu 0 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ieee802.11 00:1c:bf:ac:b7:60 brd 00:00:00:00:00:00 5: wlan0: mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:1c:bf:ac:b7:60 brd ff:ff:ff:ff:ff:ff For < ip -f inet6 addr > I get: 1: lo: mtu 16436 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 5: wlan0: mtu 1500 qlen 1000 inet6 fe80::21c:bfff:feac:b760/64 scope link valid_lft forever preferred_lft forever For < ip -f inet6 route > I get: fe80::/64 dev wlan0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0 For < ip -f inet link > I get: 1: lo: mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: mtu 1500 qdisc pfifo_fast state DOWN qlen 1000 link/ether 00:1d:72:2b:73:90 brd ff:ff:ff:ff:ff:ff 3: irda0: mtu 2048 qdisc noop state DOWN qlen 8 link/irda 00:00:00:00 brd ff:ff:ff:ff 4: wmaster0: mtu 0 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ieee802.11 00:1c:bf:ac:b7:60 brd 00:00:00:00:00:00 5: wlan0: mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:1c:bf:ac:b7:60 brd ff:ff:ff:ff:ff:ff For < ip -f inet addr > I get: 1: lo: mtu 16436 qdisc noqueue state UNKNOWN inet 127.0.0.1/8 scope host lo 5: wlan0: mtu 1500 qdisc pfifo_fast state UP qlen 1000 inet 192.168.1.70/24 brd 192.168.1.255 scope global wlan0 And for < ip -f inet route > I get: 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.70 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 default via 192.168.1.1 dev wlan0 proto static I hope the above is of some use to you and that it helps in clearing up this problem. What concerns me (in addition to causing ME to have a problem!) is that someone else, after their wireless router is turned off either deliberately, as in my case, or inadvertently, by a power failure for example, may be unable to load few or no pages within Firefox. (In my case it was extremely strange in that I could load SOME pages but not MOST of them! Now why would that happen?) Thank you for responding to me and thank you for any effort you can make in resolving this apparent bug. And if you will tell me how to add a workaround to the bug description (and tell me what to say), I'll be glad to do it. Very truly yours, Lawrence H. Bulk