Comment 0 for bug 236884

It's possible to have a client machine in a situation where landscape itself is using a proxy, but not smart. In networks where the only way out is via a proxy, this means that that machine would never be able to perform package operations, nor report the packages it has installed and available.

Even if smart checks the http_proxy env var, it's entirely possible the admin didn't set it. A contributing factor is that the landscape-config wizard explicitly asks for a proxy, so it's not unreasonable for the admin to assume smart would be setup too.

I suggest to have landscape-config also set the proxy for smart if one is set for landscape.