Re: fedoraproject.org down (ipv6 only)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 08/28/2009 08:27 PM, Michael Cronenworth wrote:
I see fedoraproject.org has a AAAA record now (how new is that?) but the IP is not responding today. Access to fedoraproject was working up until today so I'm not sure if the AAAA record is brand new today or if it's just down.

$ ping6 fedoraproject.org
PING fedoraproject.org(2610:28:200:1::fed0:1) 56 data bytes
^C
--- fedoraproject.org ping statistics ---
11 packets transmitted, 0 received, 100% packet loss, time 10721ms

I cannot use yum in this situation. I can access http://ipv6.google.com just fine.

try this.
1.  Q: Networking (or DNS) seems really slow and fails often (Updated 2 January 2009)
A: If Fedora 10's networking seems slow or you get frequent network connection failures (when other Fedoras or other OSes were working just fine on your machine), then you're probably hitting this bug.

Here's how you can work around it:

   1. Open a Terminal.
   2. Become root:

      su -
   3. Make sure that the "dnsmasq" program is installed (it usually is, by default, in Fedora 10):

      rpm -q dnsmasq

      If that says "package dnsmasq is not installed", then you need to install dnsmasq, by running the following command:

      yum install dnsmasq
   4. Now, you have to find out which network interface your machine is using:

      route -n

      You'll see some output that looks like this:

      Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0

      The eth0 there (the furthest bottom-right text in the output) is the name of the network interface I'm using. Yours might be eth1 or something totally different. Just remember it for the next step.
   5. Now create a file called /etc/dhclient-<your network interface>.conf. For example, if your network interface is eth0, the file would be called /etc/dhclient-eth0.conf.

      You can create the file with this command (assuming your network interface is eth0):

      nano /etc/dhclient-eth0.conf

      Then make this the only line in the file:

      prepend domain-name-servers 127.0.0.1;

      And then save the file and close it (Ctrl-X then Y).

      If you have both a wireless and a wired network connection, you will have to do this step once for each of them.
   6. Now start dnsmasq:

      service dnsmasq start

      And make sure that it will start every time your computer starts:

      chkconfig dnsmasq on
   7. Now restart your network connection:

      service NetworkManager restart

And now things should be as fast as normal again. You might have to restart the programs that you're running for them to pick up the changes that NetworkManager made when it restarted.



2.  * IPv6
You might notice that your browsing through Firefox is a little slow on Fedora 10. This is because Firefox 3 has enabled by default IPv6 which causes Firefox to first resolve an IPv6 address and after the connection fails it switches to IPv4. To change this setting type:

about:config


and in Filter box type:

network.dns.disableIPv6


Right click on it, select Toggle and change its value to true. Restart Firefox and you are ready! 




Selinux Relabeling files.

setenforce 0; fixfiles -F restore; setenforce 1; reboot 
-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux