-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-05-06 15:00, Roger Oberholtzer wrote:

There is no proxy. The strange thing is that this happens with a wired connection. We also have a wireless Guest connection that has no restrictions on external access (only restrictions on internal access) and the Guest interface is fast. It is the wired one that is the problem. The IT guys here like to help by saying "We don't support Linux.". Actually, Linux works here better than they know. Except for zypper and only in this office...

It does look as a proxy. Like checking all downloads for viruses. It appears as if the download stalls, then you get it suddenly at the end, after the proxy has downloaded and scanned it. It is pretty typical on a corporate, windows based, network. That they say "we don't support Linux" is indicative. The guest interface is not protected by the corporate proxy. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlVKF/YACgkQja8UbcUWM1xwMgD/TTfJthUmgIaNg+/Sns2TbMCB 4e11nmGjNNpE+gSFhEcA/Axb9W4UHMAbXicziqDYHO68tndrbI5ve36qtc/CkOlv =DhLc -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 05/06/2015 06:32 AM, Carlos E. R. wrote:

On 2015-05-06 15:00, Roger Oberholtzer wrote:

...

There is no proxy. The strange thing is that this happens with a wired connection. We also have a wireless Guest connection that has no restrictions on external access (only restrictions on internal access) and the Guest interface is fast. It is the wired one that is the problem. The IT guys here like to help by saying "We don't support Linux.". Actually, Linux works here better than they know. Except for zypper and only in this office...

It does look as a proxy. Like checking all downloads for viruses. It appears as if the download stalls, then you get it suddenly at the end, after the proxy has downloaded and scanned it. It is pretty typical on a corporate, windows based, network.

But didn't the thread start off by saying that this did not occur when using YAST, or did I imagine that? -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

I seem to recall that they have some Cisco device (IronPort, I think). I suspected that it was the problem I had before related to that at some time in the past. So I tried the zypper environment variable that said to use curl instead of aria2c (or whatever it is called) to get the items. Getting a single file from multiple hosts did not work well with the Cisco device. But that seems not to have any effect. I do not know if it is even still implemented. I suspect not. We are trying to do system updates. Some files are rather small. So even waiting for the Cisco thing to get the whole thing should still go fast. But I think there are options in the http protocol that zypper uses that the Cisco device does not support. At least aria2c uses them. And if the flag to use curl as the mechanism is no longer recognized, the problem will remain. My memory on this is foggy. It was a couple years ago when I went through this in my office (not the same one). IIRC, the final solution was to let my system bypass the Cisco device. Since it has been working for me I had almost forgotten about it. I googled my previous issue with this and saw that I could run the aria2c program to get an rpm to see it that was the problem. I no longer seem to have aria2c installed. So perhaps zypper is now using something else? Checking the binary, I see libcurl referenced. Some libs I do not recognize, so I do not know if one of these might be the successor to aria2c. I would still like to know if zypper can still be told to use curl, it it is not already. BTW, the same thing happens in yast. On Wed, May 6, 2015 at 11:49 PM, Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

On 2015-05-06 20:22, John Andersen wrote:

...

But didn't the thread start off by saying that this did not occur when using YAST, or did I imagine that?

No: «Mysteriously, when running zypper (or yast), downloading packages screeches to a near standstill.»

- -- Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)

iF4EAREIAAYFAlVKjFcACgkQja8UbcUWM1yR8AD+Ojj0ul86L+QI4YPtO4ChxiLb ZKTbB877SeRnaZ5lYZYA+gI34EmueCR46RexGODn9nFHjNR8a8kAT9ZGPIJ98xzV =KMWg -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

This works fine. We get > 3MB per second sustained. It starts reporting immediately. It would be interesting if a similar command for the method zypper uses could be done. Previously, the command was aria2c. I don't see that one anymore. So I do not know if zypper is still using it. On Thu, May 7, 2015 at 8:02 AM, Per Jessen wrote:

Roger Oberholtzer wrote:

...

I seem to recall that they have some Cisco device (IronPort, I think).

Ironport is an anti-spam device, I don't really see it being involved in port 80 traffic.

...

BTW, the same thing happens in yast.

Take yast and zypper out of the equation, and try a simple wget download - it should be affected in exactly the same way:

wget -O /dev/null http://ftp.sunet.se/pub/Linux/distributions/opensuse/distribution/13.2/iso/o...

If you get the same slow download here, it's not about yast&zypper. If you get nornal speed, it's probably about yast/zypper.

-- Per Jessen, Zürich (12.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-05-07 09:46, Per Jessen wrote:

Roger Oberholtzer wrote:

...

It would be interesting if a similar command for the method zypper uses could be done. Previously, the command was aria2c. I don't see that one anymore. So I do not know if zypper is still using it.

I think(!) zypper uses curl, but it should not make a difference.

Yes, but internally, with a library, not as a command. AFAIK, there is no way to call aria2c. I have a feeling I read about something similar and strange, with zypper/yast. I don't remember now enough details to search for it. Maybe a grep for aria2c in the list :-? [...] nope, didn't see it. Idea: are you using IPv6? I read that there are issues, because geolocation doeesn't work right, and you may get directed to mirrors on the other end of the globe. Subject: Re: [opensuse] IPv6 to OpenSUSE sites? - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlVLXoUACgkQja8UbcUWM1yKBwD/XTk+ZaykJUUo89Sn52h+Tgvo 2wRbK7nMLINB16JIkXwA/jwS5nFb4ktHpupkkX8A6KBOwSTbc8K11FR+iiOWvx9I =34oR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Not using IPv6. But I am not sure it is explicitly disabled. I will suggest that. On Thu, May 7, 2015 at 2:45 PM, Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

On 2015-05-07 09:46, Per Jessen wrote:

...

Roger Oberholtzer wrote:

...

...

It would be interesting if a similar command for the method zypper uses could be done. Previously, the command was aria2c. I don't see that one anymore. So I do not know if zypper is still using it.

I think(!) zypper uses curl, but it should not make a difference.

Yes, but internally, with a library, not as a command. AFAIK, there is no way to call aria2c.

I have a feeling I read about something similar and strange, with zypper/yast. I don't remember now enough details to search for it. Maybe a grep for aria2c in the list :-? [...] nope, didn't see it.

Idea: are you using IPv6? I read that there are issues, because geolocation doeesn't work right, and you may get directed to mirrors on the other end of the globe.

Subject: Re: [opensuse] IPv6 to OpenSUSE sites?

- -- Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)

iF4EAREIAAYFAlVLXoUACgkQja8UbcUWM1yKBwD/XTk+ZaykJUUo89Sn52h+Tgvo 2wRbK7nMLINB16JIkXwA/jwS5nFb4ktHpupkkX8A6KBOwSTbc8K11FR+iiOWvx9I =34oR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 05/07/2015 08:05 AM, Per Jessen wrote:

Carlos E. R. wrote:

...

Idea: are you using IPv6? I read that there are issues, because geolocation doeesn't work right, and you may get directed to mirrors on the other end of the globe.

That was what I said in my first reply in this thread :-)

http://lists.opensuse.org/opensuse/2015-05/msg00152.html

Back in february, I suggested we simply remove IPv6 for download.opensuse.org:

https://progress.opensuse.org/issues/6176

Nothing much has happened since then.

Thread's so damn long, I missed that. I also have IPV6 turned off, so I never seem to get bit by this.... Other than in hotels. I have seen extremely slow downloads using Yast when in hotels. Even when the rest of the net is working fine. I just switched to my phone's wifi hot spot and its fast. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

I see that curl is the same as wget. Nice and fast. It is only zypper/yast that have a problem. So I suspect that zypper is either not using curl, or it is setting some option. I used no options with curl. And it seemed happy. On Thu, May 7, 2015 at 9:33 AM, Roger Oberholtzer wrote:

This works fine. We get > 3MB per second sustained. It starts reporting immediately.

It would be interesting if a similar command for the method zypper uses could be done. Previously, the command was aria2c. I don't see that one anymore. So I do not know if zypper is still using it.

On Thu, May 7, 2015 at 8:02 AM, Per Jessen wrote:

...

Roger Oberholtzer wrote:

...

I seem to recall that they have some Cisco device (IronPort, I think).

Ironport is an anti-spam device, I don't really see it being involved in port 80 traffic.

...

BTW, the same thing happens in yast.

Take yast and zypper out of the equation, and try a simple wget download - it should be affected in exactly the same way:

wget -O /dev/null http://ftp.sunet.se/pub/Linux/distributions/opensuse/distribution/13.2/iso/o...

If you get the same slow download here, it's not about yast&zypper. If you get nornal speed, it's probably about yast/zypper.

-- Per Jessen, Zürich (12.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-- Roger Oberholtzer

-- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-05-07 11:23, Per Jessen wrote:

I'm sure you can set a bandwidth limit on both wget and curl, but it doesn't seem to make much sense for zypper to do that.

On the contrary, it does. When you have slow internet, you may want to limit the bandwidth yast/zypper uses so that other things or other machines in the house can keep working. Yes, the update takes longer, so what? :-) One way I used was this: trickle -s -d 45 yast2 --qt online_update Another was edit /root/.curlrc, with the line "--limit-rate 25K" But the best, available since 13.1, is chnage in /etc/zypp/zypp.conf the setting download.max_download_speed. This works fine. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlVLY1MACgkQja8UbcUWM1yGzwD/YXobdVHhfSfRcV78OjeJao2h +zxl9PD6VpL+r5vMNcoA/RhTIUSBFQBMaFwc5a8QQks8ohLNsNG/ZuFmpWzI+0vM =6lDM -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2015-05-07 17:00, Per Jessen wrote:

Carlos E. R. wrote:

Sure, I understand that, but doesn't make sense for _zypper_ to do set any limits on its own.

An automatic limit? No, right, I don't see why it wold do that. I didn't notice you were talking about an automatic limit. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

I will try this. Does this apply to 13.1 as well? On Thu, May 7, 2015 at 12:33 PM, Michael Andres wrote:

On Thursday 07 May 2015 10:56:54 Roger Oberholtzer wrote:

...

I see that curl is the same as wget. Nice and fast. It is only zypper/yast that have a problem. So I suspect that zypper is either not using curl, or it is setting some option. I used no options with curl. And it seemed happy.

zypp is using libcurl (and no aria2c; finally removed in 13.2.0).

You can try ZYPP_MULTICURL=0 to turn off multicurl (metalink and zsync) and fall back to plain libcurl.

You can set ZYPP_MEDIA_CURL_DEBUG=2 to log the http headers and server responses to the log file. Maybe the timestamps in /var/log/zypper.log can help to figure out where the time is spent.

--

cu, Michael Andres

+------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres SUSE LINUX GmbH, Development, ma@suse.de Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 74 053-0 +------------------------------------------------------------------+ SUSE Linux GmbH GF: Felix Imendörffer, Jane Smithard, Jennifer Guild Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) +------------------------------------------------------------------+

-- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 05/07/2015 11:56 AM, Roger Oberholtzer wrote:

...

My solution was to choose individual fixed mirror repos instead of the main one. I tested the speed by measuring individual downloads and set my repos to point to the fastest one. For my locations the best one was in Germany, don't remember the name.

How do you set a fixed repo? I would imagine it could need to be done on a per-repo basis. The most likely mirror for us is sunet.se. But it may not mirror Packman, Google, or Nvidia...

And, how to set this for zypper and yast?

-- Roger Oberholtzer

I went to yast/software_repositories and there you have urls for each repo. By default, most of them are "http://download.opensuse.org/..." something. You can edit and change the url to another fixed mirror. Now, how to choose which one to put where. There is a list of all mirros somewhere on opensuse site. You have to check which site mirrors which repo and make your own choice. Try http://mirrors.opensuse.org/. Just avoid ftp sites and slow/distant servers. You're right regarding packman, it's not mirrored this way. I think most of the IronPort problems is caused by dynamic mirror/IP change of download.opensuse.org, and this doesn't happen with packman and others. ~rmš~

On 05/07/2015 08:10 AM, Per Jessen wrote:

Roger Oberholtzer wrote:

...

...

My solution was to choose individual fixed mirror repos instead of the main one. I tested the speed by measuring individual downloads and set my repos to point to the fastest one. For my locations the best one was in Germany, don't remember the name.

How do you set a fixed repo? I would imagine it could need to be done on a per-repo basis. The most likely mirror for us is sunet.se. But it may not mirror Packman, Google, or Nvidia...

And, how to set this for zypper and yast?

You change the repo URLs to point directly to your favourite mirror instead of download.opensuse.org.

Yast -> Software Repositories.

Wait... Per, are you saying that download.opensuse.org is actually some sort of round-robin load balancing address, where each access may go to some different mirror? -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2015-05-07 a las 20:09 +0200, Per Jessen escribió:

John Andersen wrote:

...

Wait... Per, are you saying that download.opensuse.org is actually some sort of round-robin load balancing address, where each access may go to some different mirror?

Yes, that's pretty much it, but in an intelligent fashion. It's running mirrorbrain which directs you to a geographically close mirror. There's probably some load balacing involved too.

Yes. I understand that it can also give the downloader information to download from several mirrors in parallel, metalink type. The geolocation using IPv6 doesn't work right, I heard, so that you can get redirected to a mirror on the other side of the globe, with slow results... - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlVMGNoACgkQja8UbcUWM1wZugEAkwuozIbMmwJJUDWWXC172BbH QK2W4nTE8iiYcC2bHvgA/3sPSjHhIYe/SmfmQ+zNSvmmPjrhddsTYoP8gDIM0K4b =3Sab -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-05-08 10:38, Per Jessen wrote:

Carlos E. R. wrote:

Yup - I believe(!) the issue is that there is no IPv6 geolocation database. Given the lack of people reporting this issue, I guess we can conclude that IPv6 deployment among openSUSE users is negligible.

Indeed. My current router, a new one supplied by my ISP, is prepared for IPv6, hands them to the local network, but no v6 connectivity to Internet. Maybe. My guess is that they are preparing for the future(©) - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlVMnQUACgkQja8UbcUWM1zULAD/VOHJa2joBjz5wC6ALe9jNnxe u+m3hdBaxfyrjLTw7SEBAJgsdo0vWYa0yZCA3sCE6OVCJGUSnHySX0A2V4xULG18 =DQ5+ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 05/08/2015 04:38 AM, Per Jessen wrote:

Yup - I believe(!) the issue is that there is no IPv6 geolocation database. Given the lack of people reporting this issue, I guess we can conclude that IPv6 deployment among openSUSE users is negligible.

Well, I've been running IPv6 for about 5 years and haven't seen that problem. Then again, I don't use zypper. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 05/08/2015 08:16 AM, Carlos E. R. wrote:

...

Well, I've been running IPv6 for about 5 years and haven't seen

...

that problem. Then again, I don't use zypper. YaST would have the same issues.

Well, I still haven't seen them. Yast software management and update work well. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 05/08/2015 08:16 AM, Carlos E. R. wrote:

On 2015-05-08 13:43, James Knott wrote:

...

On 05/08/2015 04:38 AM, Per Jessen wrote:

...

Yup - I believe(!) the issue is that there is no IPv6 geolocation database. Given the lack of people reporting this issue, I guess we can conclude that IPv6 deployment among openSUSE users is negligible.

...

Well, I've been running IPv6 for about 5 years and haven't seen that problem. Then again, I don't use zypper.

YaST would have the same issues.

Indeed, because they both use libzypp -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* John Andersen [05-07-15 21:25]: [...]

Wait... Per, are you saying that download.opensuse.org is actually some sort of round-robin load balancing address, where each access may go to some different mirror?

Most certainly, and has been for a looong time :^) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org