Hi
I used fedora 6 connected to the internet where its gateway was a WIN xp machine with ICS enabled and all worked fine.
I changed my DSL modem to a router configuration and connected both computers to the router with a switch.
I had to disable ipv6 explained here:
(http://www.mjmwired.net/resources/mj...-fc6.html#ipv6)

and i can see the internet OK,but, Evolution mail can't connect anymore,yum and wget aren't working,terminal SSH also and who knows what else...
this is what i get from yum:

[root@fedora6 etc]# yum search java
Loading "installonlyn" plugin
Setting up repositories
Could not retrieve mirrorlist http://mirrors.fedoraproject.org/mir...re-6&arch=i386 error was
[Errno 4] IOError: <urlopen error (-2, 'Name or service not known')>
Error: Cannot find a valid baseurl for repo: core

I can open the site with firefox and if i change the siteś name to itś IP in yum confand uncommented the base urls in yum conf files then i get this:

Loading "installonlyn" plugin
Setting up repositories
Could not retrieve mirrorlist http://mirrors.fedoraproject.org/mir...re-6&arch=i386 error was
[Errno 4] IOError: <urlopen error (-2, 'Name or service not known')>
http://66.187.224.20/pub/fedora/linu...ta/repomd.xml: [Errno 4] IOError: <urlopen error (-2, 'Name or service not known')>
Trying other mirror.
Error: Cannot open/read repomd.xml file for repository: core



I feel like its a dns problem.

any ideas?

thanks.

ok, if you can reach the internet ok, can you go to "http://mirrors.fedoraproject.org" in firefox? are you using a proxy to do this? if you can successfully see that webpage but yum is failing to reach the same site, it'd have to be a proxy issue i'd be sure. what does the contents of /etc/resolv.conf say about your cojfigured name servers? can you ping the name servers? can you do a dig or host lookup against them explicitly, e.g. "dig google.com @12.34.56.78"?

I can go to http://mirrors.fedoraproject.org/ in firefox.
my resolv.conf looks like this:
search homenet.com
nameserver 10.0.0.138

"serach homenet.com" is just something i entered in the network configuration of fedora for dns search path, i don't realy know what this means.

10.0.0.138 is the routerś IP.

and "dig google.com@12.34.56.78" got this:

; <<>> DiG 9.3.3rc3 <<>> google.com@12.34.56.78
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 62214
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com\@12.34.56.78. IN A

;; Query time: 1995 msec
;; SERVER: 10.0.0.138#53(10.0.0.138)
;; WHEN: Mon Dec 11 16:03:17 2006
;; MSG SIZE rcvd: 40


I'd mention that the xp machine connected in the same way is working with no problems.

Thanks.

yeah, 12.34.56.78 was an example... thought that would have been apparent...

try "dig google.com @10.0.0.138"

OK

this is the result with 10.0.0.138:

; <<>> DiG 9.3.3rc3 <<>> google.com @10.0.0.138
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12977
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;google.com. IN A

;; ANSWER SECTION:
google.com. 281 IN A 64.233.187.99
google.com. 281 IN A 72.14.207.99
google.com. 281 IN A 64.233.167.99

;; AUTHORITY SECTION:
google.com. 6043 IN NS ns3.google.com.
google.com. 6043 IN NS ns4.google.com.
google.com. 6043 IN NS ns1.google.com.
google.com. 6043 IN NS ns2.google.com.

;; ADDITIONAL SECTION:
ns1.google.com. 173329 IN A 216.239.32.10
ns2.google.com. 173329 IN A 216.239.34.10
ns3.google.com. 173329 IN A 216.239.36.10
ns4.google.com. 173329 IN A 216.239.38.10

;; Query time: 18 msec
;; SERVER: 10.0.0.138#53(10.0.0.138)
;; WHEN: Mon Dec 11 16:23:38 2006
;; MSG SIZE rcvd: 212

right so dns is just fine, so next go a step further into the system... can you manually downlaod the mirror list that yum is choking on?


curl http://mirrors.fedoraproject.org/mir...re-6&arch=i386

yes, i can see this in firefox.

can you run the command i gave you?

this is what i get with this command and the hangs for a long time

[shlomi@fedora6 ~]$ curl http://mirrors.fedoraproject.org/mir...re-6&arch=i386
[1] 3026
[shlomi@fedora6 ~]$ # no arch specified
# Valid archs: i386, ppc, x86_64

Either you didn't follow the steps exactly to disable IPv6, or you manually edited a file and made modifications you're not revealing. It sounds like either you edited /etc/services and removed/commented some lines, or that the resolver libraries are expecting IPv6 support to be present and it's not. Have you checked your interfaces to see if they're getting IPv6 addresses? That might be causing a problem if your primary interface still has an IPv6 address but the support for it is turned off.

BTW, this is a good example of why "tuning the kernel for performance" is generally a bad idea. Unless you know exactly what you're doing, trying to remove default pieces (especially as big a piece as IPv6) is just going to cause problems, and for very little potential gain. My recommendation would be to just IPv6 on and have the opportunity to learn about it as it's rolled out to more sites over the coming years. The US goverment for example has a huge push for IPv6. I believe they're even mandated to have all software support IPv6 within 2 years.

I installed a fresh copy of fedora 6.
the only thing i did is disabl ipv6 as in here:
http://www.mjmwired.net/resources/mj...-fc6.html#ipv6

using the network configuration tool i configured my nic to have a static ip where the gateway is the router/adsl modem.

/etc/sysconfig/networking/devices/ifcfg-eth0
# Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+
DEVICE=eth0
BOOTPROTO=static
BROADCAST=10.255.255.255
HWADDR=00:E0:4C:39:36:FC
IPADDR=10.0.0.2
IPV6ADDR=
IPV6PREFIX=
NETMASK=255.0.0.0
NETWORK=10.0.0.0
ONBOOT=yes


/etc/sysconfig/network
NETWORKING=yes
NETWORKING_IPV6=no
HOSTNAME=fedora6.localhost.localdomain
GATEWAY=10.0.0.138

/etc/resolv.conf
search localhost.localdomain
nameserver 10.0.0.138



Thanks

I had to disable ipv6 or i can't connect at all,looks like my isp doesn't support ipv6 yet.