I could, but that seems to be overkill for the real problem - since all other web apps I use are fine, it's gotta be something in a way zypper works. My DNS servers are configured dynamically via DHCP, and since I move around a lot, I just as well not mess with my network configuration. Especially given that it's a single application that is failing. On Thu, Jan 1, 2009 at 2:08 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Thursday, 2009-01-01 at 12:08 -0000, Myrosia Dzikovska wrote:

...

I run opensuse updater applet in 11.0. More 2/3 of the time it comes up with the same message "curl error: cannot resolve http://download.opensuse.org" or "curl error: cannot resolve http://www.mirrorservice.org". If I type either of those addresses into Firefox, they come up just fine, though there is a delay (my provider's ISP isn't the fastest). And if I re-try the update immediately after, it comes through. But it doesn't seem to be able to go forward on its own. Is there a way for me to reconfigure something to make it work? I don't really think it's my network configuration per se - my web browsing never has any problems. I am wondering if there is some extra config setting for libcurl and/or zypper that I could set, and where, to make it more tolerant to long delays in domain name resolution.

You could install a local dns server as cache.

Maybe you have two dns servers configured and one fails.

- -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAklczm8ACgkQtTMYHG2NR9WHqACfdxP0F6eHGQkk3OadF/LG1roB E9wAnj3d3OCvPYWaNcNu+FnX73/uH9F/ =mcTC -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thursday 01 January 2009 08:50:11 am Carlos E. R. wrote:

On Thursday, 2009-01-01 at 14:39 -0000, Myrosia Dzikovska wrote:

...

I could, but that seems to be overkill for the real problem - since all other web apps I use are fine, it's gotta be something in a way zypper works. My DNS servers are configured dynamically via DHCP, and since I move around a lot, I just as well not mess with my network configuration. Especially given that it's a single application that is failing.

But you can not tune that application, as far as I know.

By the way, you can configure any dns server you like, regardless of where you are connected. It doesn't have to be the one your provider says.

In short disable IPv6 using YaST, and remove one obstacle from the stack. The IPv6 is enabled and it is used first. I used wireshark to see what is going on, and you have first unresolved DNS resolution request (IPv6), then resolved (IPv4). That happens with every URL. IMHO, it is not very smart plan in the world where IPv4 is still dominant. In my case the home router will not respond, as it has no clue what is IPv6, so my Internet provider will not see those double requests on his servers, but some software may fail. I don't see consistent failure by curl, ie. first failure and on repeat success, so it doesn't fail on IPv6 request failure, but failed request takes time from the total time allowed for name resolution. Situation is better since I configured openSUSE to use ISP's nameservers directly, not the router as intermediate. For libcurl advice we need someone who knows internals, ie. file bug report with request to have that configurable. I guess that dialup users will see more problems than broadband. The wireshark gives time from request to answer, and usually it is in range of tens of milliseconds, but sometimes server has more requests and it can be a second. Some websites with ads are real DNS server killer. They request resolution of 90 names for each page. Some like Yahoo ask once and that's it. Mentioned this, does openSUSE use DNS resolver cache? -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hi Myrosia, This landed in my mailbox only, but more people would like to know that disabling IPv6 helps, so I'll post the answer on the mail list too. On Thursday 01 January 2009 12:18:52 pm Myrosia Dzikovska wrote:

...

In short disable IPv6 using YaST, and remove one obstacle from the stack.

Thanks! I figured out how to run wireshark and saw the same thing you did - IPv6 requests going to the router, and coming back as failures, and then re-tries as IPv4. So I disabled IPv6, and things seem to be going better - I run a couple of update checks and repository refesh calls, and they all worked, where something was regularly failing previously.

I need to watch it for a couple of days, but looks to me that this solves the problem. Looked up stats on Wikipedia, and something like 0.6% of all hosts are using IPv6, so I figure disabling it is unlikely to be a problem. And I agree with you, it is not the best strategy to have it enabled by default if in fact almost no one uses it.

Myrosia

Even those 0.6% have to use IPv4 too, otherwise they would be isolated. You would not miss anything. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thu, 2009-01-01 at 10:13 -0600, Rajko M. wrote:

On Thursday 01 January 2009 08:50:11 am Carlos E. R. wrote:

...

On Thursday, 2009-01-01 at 14:39 -0000, Myrosia Dzikovska wrote:

...

I could, but that seems to be overkill for the real problem - since all other web apps I use are fine, it's gotta be something in a way zypper works. My DNS servers are configured dynamically via DHCP, and since I move around a lot, I just as well not mess with my network configuration. Especially given that it's a single application that is failing.

But you can not tune that application, as far as I know.

By the way, you can configure any dns server you like, regardless of where you are connected. It doesn't have to be the one your provider says.

In short disable IPv6 using YaST, and remove one obstacle from the stack.

The IPv6 is enabled and it is used first. I used wireshark to see what is going on, and you have first unresolved DNS resolution request (IPv6), then resolved (IPv4). That happens with every URL.

IMHO, it is not very smart plan in the world where IPv4 is still dominant. In my case the home router will not respond, as it has no clue what is IPv6, so my Internet provider will not see those double requests on his servers, but some software may fail.

I don't see consistent failure by curl, ie. first failure and on repeat success, so it doesn't fail on IPv6 request failure, but failed request takes time from the total time allowed for name resolution. Situation is better since I configured openSUSE to use ISP's nameservers directly, not the router as intermediate.

For libcurl advice we need someone who knows internals, ie. file bug report with request to have that configurable. I guess that dialup users will see more problems than broadband.

The wireshark gives time from request to answer, and usually it is in range of tens of milliseconds, but sometimes server has more requests and it can be a second.

Some websites with ads are real DNS server killer. They request resolution of 90 names for each page. Some like Yahoo ask once and that's it. Mentioned this, does openSUSE use DNS resolver cache?

-- Regards, Rajko

Rajko, Seems to be the same problem I got (Bug 463015 - Able to ping unable to connect) A couple of points: 1. disabling ipv6 did not allow me to use evolution, the rest was OK. I just got Wireshark after you mention it. Now I have to figure it out before I can use it and figure out what's happening with evolution. 2. Adding the DNS servers works while you do not use the network manager. If I enable the networkmanager the DNS server is not written to the resolv.conf. I quess I can use ifup but it was better to go back to 11 in my TP x61. 3. This is not a problem unique to opensuse 11.1. When fedora 10 came out I tested it and I had a very similar problem. At the time I solved there disabling ipv6. 4. "It seems something wrong with IPv6 in Avahi" it looks like you are in the correct track. I have been reading about Avahi but until you mentioned it I have no clue ;-) -=terry=- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thursday 01 January 2009 20:49:49 Carlos E. R. wrote:

"Apple's Zeroconf". If I don't have any "apple" in my network, can I dissable this service?

You also don't have anything built by DARPA, can you disable tcp/ip? Just because Apple designed the protocol doesn't mean it's tied to MacOS However, if you're configuring everything manually and explicitly, you can disable it. It is a protocol intended to make a LAN usable without any configuration at all Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-01-01 at 15:14 -0700, Teruel de Campo MD wrote:

Anders,

I do not think Carlos or most of us are against using avahi what we are trying to figure out is how to around of something that is not working.

Exactly. I don't really know what is avahi for, I don't know what it does. Just suppose it does some type of network configuration automatically, perhaps changes the dns, who knows. I know what the man page describes, and I don't understand it. The man page talks about some configuration files which I haven't touched. Perhaps the configuration is bad. Or good. I have no idea. I only know that I don't know what it does, what it changes or provides and for what programs, the effect it has... So I ask. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkldUwYACgkQtTMYHG2NR9Wi1QCfTw3FYDR47qezHJJfLiInpW+M rBIAn3F8TVqUCH9AA45TBhMj77Kyk203 =iM1o -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2009-01-02 at 00:47 +0100, Anders Johansson wrote:

On Friday 02 January 2009 00:34:27 Carlos E. R. wrote:

...

I only know that I don't know what it does, what it changes or provides and for what programs, the effect it has...

So I ask.

As I said, it helps you set up a network without configuration. If you configure things yourself, or if you already have dhcp and dns from some other source, you don't need it. The same goes if you have special non-trivial needs for your lan.

http://en.wikipedia.org/wiki/MDNS

has a reasonably good explanation

Ok, lets have a look. ] Zero Configuration Networking (Zeroconfig), is a set of techniques that ] automatically creates a usable IP network without configuration or ] special servers. ] ] This allows inexpert users to connect computers, networked printers, and ] other network devices and expect a functioning network to be established ] automatically. Without Zeroconfig, a user must either set up special ] services, like DHCP and DNS, or set up each computer's network settings I have both DHCP and DNS. ] manually, which may be challenging for non-technical or novice users. ] ] Zeroconfig currently provides these services: ] ] * Choose numeric network addresses for networked devices, (link-local ] address autoconfiguration) I don't need that, I set up my own Numbers. ] * Automatically resolve and distribute computer host names I set up my names, so I don't need it either. ] * Automatically locate network services, like printing (service ] discovery) Nay, when I configured my printer YaST couldn't find it. I had to tell it where it was. Anyway, the firewall has most ports closed... So, I think I do not need them; I'll try disabling both daemons (avahi-dnsconfd and avahi-daemon) for the moment. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkldXNsACgkQtTMYHG2NR9WMFACfZbswbEcW3/CECYBoBThJmaDa JrwAnjXB1Pqe2i9ki72DZO1X/RGR9/Lv =ePMU -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-01-01 at 17:59 -0600, Rajko M. wrote:

In other words we are trying to find how to improve things that currently work for majority, but under some circumstances can be source of frustration.

Disabling Avahi without knowing to what extent it is used, ie. what functions will need manual tweaking is not a solution. Shoot the unknown device and hope that the rest of the system will just work is in domain of fiction.

I have just dissabled avahi (suse 11.0), I think I do not need it. The worst that can happen is that I have to reenable it. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkldXYAACgkQtTMYHG2NR9Wt2wCcC6UgNi+RxZPozW0llpUlKW+j VtsAn01tny8hGGmC8SHnMDqbIhE/bEkP =8pC4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thu, 2009-01-01 at 19:01 -0600, Rajko M. wrote:

On Thursday 01 January 2009 01:27:55 pm Teruel de Campo MD wrote: ...

...

Rajko,

Seems to be the same problem I got (Bug 463015 - Able to ping unable to connect)

A couple of points:

1. disabling ipv6 did not allow me to use evolution, the rest was OK. I just got Wireshark after you mention it. Now I have to figure it out before I can use it and figure out what's happening with evolution.

Whatever is going on look in Evolution. Some enterprize networks are internally IPv6, so it should be OK that Evolution defaults to IPv6, but as it is not used exclusively there, it should not fail if there is no IPv6. That should be a bug.

The minimal solution would be to have manual switch hidden somewhere in configuration. Better solution would be to have automatic switch, though it can be located in first configuration after installation, which would help Evolution to start faster by skipping check for environment changes.

...

2. Adding the DNS servers works while you do not use the network manager. If I enable the networkmanager the DNS server is not written to the resolv.conf. I quess I can use ifup but it was better to go back to 11 in my TP x61.

I can imagine how complex piece of software is that and I'm not surprised to see problems. You can't cover every possible network configuration.

Though, I would file bug report. If it is closed as invalid, then you know that you case is not covered, at least not yet.

...

3. This is not a problem unique to opensuse 11.1. When fedora 10 came out I tested it and I had a very similar problem. At the time I solved there disabling ipv6.

Avahi too?

...

4. "It seems something wrong with IPv6 in Avahi" it looks like you are in the correct track. I have been reading about Avahi but until you mentioned it I have no clue ;-)

So far, only programs that use Avahi, and users of those programs have a problem ;-)

My problem is that I don't want to become Avahi insider, but the other choice is to wait for Godot ( http://en.wikipedia.org/wiki/Waiting_for_Godot ).

When SUSE crew comes from holidays your report https://bugzilla.novell.com/show_bug.cgi?id=463015 will be one in the pile. Taking that most of the users don't complain it can be some time before it get attention.

...

-=terry=-

-- Regards, Rajko

Thxs Rajko terry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-01-01 at 10:13 -0600, Rajko M. wrote:

In short disable IPv6 using YaST, and remove one obstacle from the stack.

The IPv6 is enabled and it is used first. I used wireshark to see what is going on, and you have first unresolved DNS resolution request (IPv6), then resolved (IPv4). That happens with every URL.

I forgot that one. There is some sort of provision for this in openSUSE 11.1, because I see this in the log: ] Dec 28 14:29:28 minas-morgul kernel: eth0: no IPv6 routers present I think I saw somewhere (in the computer) something about disabling ipv6 because the router doesn't support it. I'm not running 11.1 now, so i can't check. Perhaps ipv6 can be used intranet and ipv4 outside.

I don't see consistent failure by curl, ie. first failure and on repeat success, so it doesn't fail on IPv6 request failure, but failed request takes time from the total time allowed for name resolution. Situation is better since I configured openSUSE to use ISP's nameservers directly, not the router as intermediate.

I do it the other way round: I use the router dns server because this way I don't have to cater for dynamic dns server allocation. At least mine works reasonably well. On the setup I'm running now, I have defined my own dns server instead.

Some websites with ads are real DNS server killer. They request resolution of 90 names for each page. Some like Yahoo ask once and that's it. Mentioned this, does openSUSE use DNS resolver cache?

Er... no, you have to configure one. The service "nscd", which runs by default, is misleading. The acronym stands for "name service cache daemon", but it caches passwd, group, hosts, and services; not "dns". But, simply by installing "bind" you have one, because the default configuration is that of a cache server. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkldHUsACgkQtTMYHG2NR9XFCQCgj0yQksGc4UCuyyNqrU9ZxyvU HCAAn1Y6yZmZ0HaExpMmI6dokDE9HLz9 =nJM/ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-01-01 at 19:11 -0600, Rajko M. wrote:

On Thursday 01 January 2009 01:45:08 pm Carlos E. R. wrote:

...

...

Some websites with ads are real DNS server killer. They request resolution of 90 names for each page. Some like Yahoo ask once and that's it. Mentioned this, does openSUSE use DNS resolver cache?

Er... no, you have to configure one. The service "nscd", which runs by default, is misleading. The acronym stands for "name service cache daemon", but it caches passwd, group, hosts, and services; not "dns".

But, simply by installing "bind" you have one, because the default configuration is that of a cache server.

It sounds like, use baseball bat to kill a fly. I never used bind, but it seems there is first time for everything.

True enough. But I have used it since... since I started using linux with a modem about 10 years ago, it made a bit of difference. If you have a router, it is probable that the router has bind running, too. Mine has, as cache (less load on the ISP). I don't know haw effective it can be with so little memory, I haven't measured it. But it works. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkldeHQACgkQtTMYHG2NR9XsLgCbBD7fLYKJphAQzUza2JiK8GPd tmsAoJYXfcrF1+J3UrYQ4xPKRXTVEBJA =/E8l -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-01-01 at 20:12 -0600, Rajko M. wrote:

...

...

resolution of 90 names for each page. Some like Yahoo ask once and that's it. Mentioned this, does openSUSE use DNS resolver cache?

Er... no, you have to configure one. The service "nscd", which runs by default, is misleading. The acronym stands for "name service cache daemon", but it caches passwd, group, hosts, and services; not "dns".

But, simply by installing "bind" you have one, because the default configuration is that of a cache server.

Any sample configuration at hand?

You don't need any :-) I mean, just install it, from de suse rpm, and it already runs as a cache daemon, if they haven't changed things. However, there is a change you can do in the configuration: In /etc/named.conf search for a line starting as "forwarders { something }". Put inside the DNS provided by your ISP: forwarders { 192.168.1.1; }; # router adsl forward first; This simply means that your server will ask first your ISP dns server, and if it fails, it will go to the internet root servers. You can define up to three servers: forwarders { one.ip; another.ip; one.more.ip }; - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkldeq4ACgkQtTMYHG2NR9WKaACfXsIFAiqrExgMgUB7YHQLpeRP Q6EAnA+FjAyc6PiiBUIKPAACqcyX+O2O =Pof9 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-01-01 at 23:25 -0300, Cristian Rodríguez wrote:

Rajko M. escribió:

...

Any sample configuration at hand?

See, Im going to spoonfeed you folks on how to do this as quick and clean as possible

you need

a) opensuse ***11.1*** b) 5 minutes

- install package dnsmasq "zypper in dnsmasq", and enable it as a service "ckconfig dnsmasq on"

It is installed by default, but not enabled. Interesting. This package was also included in 9.3 at least. ...

as you can see, it is trivial to do :-P

I'll save this, thanks. Advantages to use bind as cache server? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkldjFYACgkQtTMYHG2NR9V3qwCeJDx0K/56i7zbHfAG8Dkl2dLK LjoAn3AockQFlaTUugw2U5Ipsr0XMySi =fVzi -----END PGP SIGNATURE-----

Rajko M. escribió:

It doesn't work, after all.

did you started the dnsmasq service ? -- "We have art in order not to die of the truth" - Friedrich Nietzsche Cristian Rodríguez R. Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/