I have found similar threads but none arrived at solution.

http://www.linuxquestions.org/questi...s-fine-452413/
http://www.linuxquestions.org/questi...ternet-570428/
http://www.linuxquestions.org/questi...ternet-476570/

So here is my problem, i finially got my windows box to share its wireless connection with my fedora 7 box(fresh install) by bridging the connections. Konqueror works fine, so does kopete. Unfortunately yum and firefox that I have realsied so far dont work.

here is the error from yum:
[root@localhost ~]# yum search kde
Loading "installonlyn" plugin
Could not retrieve mirrorlist http://mirrors.fedoraproject.org/mir...ra-7&arch=i386 error was
[Errno 4] IOError: <urlopen error (113, 'No route to host')>
Error: Cannot open/read repomd.xml file for repository: fedora



if i type http://www.google.com into firefox it gives a standard error message about not being able to connect, but if i do this:
http://64.233.167.99/
which is one of google's ip addresses it displays the google page fine.

any other info you want just ask. thanks heaps.
regards

you need to configure your repository . the the default one does not work. if you are using 7 then you may be in trouble the repository has been down for a long time. f8 is what they are using. yum looks for the repository you configured in setting. but if F7 is no longer being kept up then it is not usable. so If you do find a f7 repository then use there key and carry on.

Looks like a DNS issue. Check that /etc/resolv.conf has your nameservers listed.

Dave

[root@localhost ~]# cat /etc/resolv.conf

nameserver 10.1.1.1
nameserver 10.1.1.1

afaik this is my dns. at least that is what ipconfig /all lists next to dns on my windows box.

many thanks.

Can you ping 10.1.1.1 ?

thanks for the response. I do have an installation of fedora 8. Was very problematic when it came to installing compiz so decided to install fc7 on old h/d. i will try set up internet connection sharing on my f8 box and see if that solves the yum issue. hmm, but it still does not explain firefox behaviour does it?

here are my ping statistics

[root@localhost ~]# ping 10.1.1.1
PING 10.1.1.1 (10.1.1.1) 56(84) bytes of data.
64 bytes from 10.1.1.1: icmp_seq=1 ttl=255 time=6.16 ms
64 bytes from 10.1.1.1: icmp_seq=2 ttl=255 time=3.45 ms
64 bytes from 10.1.1.1: icmp_seq=3 ttl=255 time=3.26 ms
64 bytes from 10.1.1.1: icmp_seq=4 ttl=255 time=4.70 ms
64 bytes from 10.1.1.1: icmp_seq=5 ttl=255 time=2.68 ms

--- 10.1.1.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 2.683/4.055/6.167/1.246 ms

guess so

thanks heaps for prompt reply

Weird.

So QT apps work (Konqueror and Kopete), but YUM and Firefox don't.

Is there anything in kcontrol -> Internet & Network set up to go through a proxy, or any service discovery?
Does 'ping google.com' work?

Dave

Just before I check, here are my findings from my f8 box.

initially firefox actually worked, it could find www.google.com hmm but then it stopped, it would however find it though http://64.blahblah

kopete worked as did konqueror in the expected way. again yum didnt though.

John.

Under Proxies it is set up as "direct connection to the internet" and nothing else seems to be the problem, at least that I can see.

thanks.

Assuming 'ping google.com' works, I can't think of any reason yum shouldn't work.
Does 'env | grep -i http' return anything?

I'm stabbing in the dark now...

Dave

opps, sorry forgot to tell you that ping google.com works fine.

um nar it didnt return anything.
thanks heaps
John.

I'm completely stumped. I can't think of anything common to Firefox and YUM that would affect name service lookups that wouldn't affect QT apps.

I think you may have to sacrifice an animal to get this working. A goat is traditional for network issues.

Dave

hahahah
thanks for all your help.

yep, goat it is.

OK, last ditch attempt. Put the goat away for a minute.

Try using a different DNS service...
Put:

nameserver 208.67.222.222

as the *only* entry in /etc/resolv.conf and see if yum/Firefox works. It's an OpenDNS server.

Dave