Bug 463015

Summary: Able to ping unable to connect
Product: [openSUSE] openSUSE 11.1 Reporter: Teruel de Campo MD <chusty>
Component: NetworkAssignee: E-mail List <gnome-bugs>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P5 - None CC: medwin
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 11.1   
Whiteboard:
Found By: Community User Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: After installing networkmanager the added DNS server address is gone

Description Teruel de Campo MD 2008-12-30 22:17:57 UTC
Problem: ISP dns server is not read.

This is what I did:

1. I can ping

2. I can resolve domain names using <host>

3. I can not use firefox, neither update. 

4. If I disable within yast ipb6 suddenly I can use firefox and get updates. However I can not get or send mail with evolution. I can however with kmail.

5. /etc/resolv.conf has only one line:

nameserver 192.168.0.1

which is the ip of the router.

6. If I add the another line with the ISP DNS server now everything is ok even after enabling ipv6. S

nameserver 205.171.3.25
nameserver 192.168.0.1


This is a major problem that did not happens in any of the previous versions since I use suse (9.0)
I have always use the 64 b version. I am running kde 4.1.3.

-=terry=-
Comment 1 Teruel de Campo MD 2008-12-30 22:20:21 UTC
On Saturday 27 December 2008 10:55:32 am Teruel de Campo MD wrote:
...
> Routers are not DNS serves and sometimes are not good and providing the
> isp dns server. 

Is is probably missing or flaky IPv6 suport. 

> Under opensuse 11 the only address under /etc/resolv.conf was the router
> address. From here the OS was able to read the isp dns address and use
> the ips dns server and I did not have any problems.
> Under opensuse 11.1 that approach is partially or randomly insufficient.
> Sometimes it works sometimes it does not. This makes the search for the
> problem hard.
> Adding the isp dns addess to the resolv.conf fixed the problem.
>
> In summary in my case these are the steps I went through:
>
> 1. Unable to connect to the net and unable to get to the repositories
> however:
>
> 1.1 I was able to ping
>
> 1. 2 I was able to resolve domain names:
>
> $ host www.google.com
> www.google.com is an alias for www.l.google.com.
> www.l.google.com has address 74.125.95.103
> www.l.google.com has address 74.125.95.99
> www.l.google.com has address 74.125.95.104
> www.l.google.com has address 74.125.95.147

'ping' and 'host' should be one of few programs that are not using Avahi [1]

> 1.3 I could not access a web site using Firefox. I could not access the
> repositories

Which is using Avahi [1]

> 2. The initial solution I found was to disable ipv6 within firefox. That
> did it. Firefox suddenly worked!.

It seems something wrong with IPv6 in Avahi, as I was able to see DNS queries 
without answer. Maybe it doesn't remember that "DNS server" has no clue about 
IPv6, or it is not designed to do so.  

Hmm ... it can't remember, mdns nor mdns4 are not present in 
current /etc/nsswitch.conf
 hosts:          files mdns4_minimal [NOTFOUND=return] dns 

mdns4_minimal is for local host
mdns4  is for the rest of the world and it comes at the end of the line, 
       after dns, but I don't know why it is dropped out.    

> 3. I still could not see any of the community repositories under yast or
> update anything. So I enable ipv6 inside Firefox and disable ipv6 under
> yast (network services). Now I could use firefox and see all the
> repositories and update the system.
> 3.1 But I still could not fetch or send mail using evolution. I was able
> to fetch mail using kmail but kmail could not send mail.  How can figure
> out this behavior?

My KMail has no problems in any direction. My problem was with browsing. 

> 4. I start to think more and more of a DNS problem so I look into the
> web router utility and from there I got the ISP DNS address and I added
> to the resolv.conf
> nameserver:xxx.xxx.xxx.xxx.
> Then enable ipv6 as it was as default and reboot. Suddenly everything
> works perfect.
> 
> 5. I remove the DNS from the resolv.conf and I added it using yast
> networking so now is added automatically to the resolv.conf. I have not
> had any problems since.
>
> What has change since opensuse 11.0 I donot know but I have both
> installed and what I described is the difference.

The /etc/nsswitch.conf is not. They are identical.  

I can put DNS servers in /etc/resolv.conf just as a patch that may speed 
up resolution, as it skips router, but it is not permanent solution. 


[1] http://avahi.org/wiki/AboutAvahi

-- 
Regards, Rajko
-- 
Comment 2 Teruel de Campo MD 2008-12-30 22:22:29 UTC
The message above I pasted it from the opensuse. Hope it ave some time :-)

-=terry=-
Comment 3 Teruel de Campo MD 2008-12-31 03:18:23 UTC
The system I was using for the above messages is a workstation wired, so the network manager was not used.
Today I installed 11.1 in a Thinkpad x61. 
The installation went perfect but I had the same problem as above. I add the DNS server using yast and the config file was change. The /etc/resolv.conf got the changes and I was able to access the repositories etc.

Then I enable the networkmanager and the wireless connection got established with no problems. But I could no access the web. Then I realized that if the networkmanger is running the DNS addresses are not written into the resolv.conf. 
The conf file seems to be OK. 

In summary I can not use the networkmanager. I will try to find a way around if not I will have to install 11.0 . This is for work.

I think you have a real problem with the DNS resolution. The fact that not everybody has this problem may be related to use a different router. The router I am using is the Motorola 3347. 
This problem is new to opensuse 11.1

-=terry=-
Comment 4 M. Edwin Zakaria 2009-01-02 04:09:30 UTC
My problem is like #1, networkmanager sometimes doesn't write the DNS server correctly in /etc/resolv.conf.
 
I use networkmanager on KDE 3.5.10 openSUSE 11.1 and ipv6 is disabled.
I'm connecting to my AP with wireless, I can browse with the name address. /etc/resolv.conf contain the name server correctly.

I cange the connection with the UTP cable, but different subnet and different DNS server. I check the /etc/resolv.conf and it contains the DNS server correctly.

Then I change the connection using bluetooth and 3G using wvdial. I can connect and get ip address from the 3G provider. I can ping ip address, but cannot browse the name address. I check /etc/resolv.conf and it contains nothing.

The workaround for my case is changing the network setup method using traditional method with ifup in Yast. And now the /etc/resolv.conf contain the DNS server correctly. So I can ping and browse using the name address. 
Comment 5 Alexander Orlovskyy 2009-01-07 09:25:53 UTC
Please provide following info:

/var/log/NetworkManager
Comment 6 Teruel de Campo MD 2009-01-07 13:22:00 UTC
Created attachment 263583 [details]
After installing networkmanager the added DNS server address is gone

The ThinkPad referred in the report does not have opensuse 11.1 any more :-( so I do not have that file any more.
The test machine I am using has only one NIC wired. This is the one of the first report where it works after I added the IP DNS server (205.171.3.25) to yast/networks settings/host-DNS. This writes the IP DNS server to the resolv.con in addition to the router address. The system is running ifup/ifdown. Connection is OK.

After reading your request what I did was to activate the networkmanager and reboot. Well the same thing that happened with the thinkpad occurred here. I could not connect. Then I looked into the resolv.conf and 205.171.3.25 is not there any more, only the router address. To send you this message I used the initial trick that it was to disable ipb6 in firefox. 

Well the good thing is that the same problem I had in the thinkpad is reproduced here. 

Thxs for your help

-=terry=-
Comment 7 Alexander Orlovskyy 2009-01-07 13:29:24 UTC
Reassign to gnome-maintainers.
Comment 8 Teruel de Campo MD 2009-01-07 13:35:39 UTC
The behavior of the NetworkManger seems to be OK. I do not think the problem is
with NetworkManager. The NM writes to the router ip to the resolve.con and that
should be enough to get the ISP DNS address but it does not. So basically
solving the first problem described above should make the NetworkManager to
work as it should.

It seems Rajko in the message above is in the correct track.

Thxs

-=terry=-
Comment 9 Teruel de Campo MD 2009-01-10 15:39:00 UTC
I've just got the Novell box of opensuse 11.1. Just in case something was different this is what I did and the results:

1. installed the 32 b and the 64 b and the results are the same.

2. After a default:

2.1 I can not connect neither to the update server or to firefox
2.2 Evolution can not get or send e-mail
2.3 I can ping and I can host.
2.4 Resolv.conf has as a nameserver the router IP 
2.3 If I disable ipv6 the update server works, firefox works but evolution does not (seems evolution needs ipv6)
The resolv.conf has the router ip
2.3 If I enable ipb6 and I add the DNS server to the resolv.conf everything works OK including evolution.
2.4 I I enable the newtork manager, the whole problem shows up again, the reason that when the networkmanger is enable it does nor write the DNS servers to resolv.conf.

In summary if ipv6 is disable, then the system can get the DNS from the routers IP. If ipv6 is enable the only way that works is to add DNS server to resolv.conf and therefore the networkmanager can not be used.

My ISP is Qwest, the Modem/router is the Motorola 3747 (Netopia) Software Version QM01-7.7.4r10

I saw few threads with this problem but I assume most of the users do not have it. Why am I different? I tried this installation in an amd fx55 desktop a Thinkpad x61 and a Thinkpad x40 with the same results. So the problem is no the computer. The modem is a standard moderm modem provided by Qwest. I do not have problems with opensuse 11 same setup. Rajko's comments make sense but what I wonder is why most of the users do not have the problem?

-=terry=-
Comment 10 JP Rosevear 2009-01-14 14:56:58 UTC
Describes pretty closely the behaviour others are seeing.

*** This bug has been marked as a duplicate of bug 441947 ***