The desktop has a network proxy configuration tool to set these things.

I've reopened that bug because there is discussion about getting anaconda
proxy-enabled (and thus asking for the proxy servers/passwords/etc.) in bug
#125917. Once that is resolved, anaconda should set the GConf system defaults
(keys beneath /system/proxy) from the proxy information it already got from the
user. Bonus points for {http,https,ftp}_proxy environment variables being set
for "legacy" aka command line applications.

Having to provide this information twice or (even worse) more (if every user has
to configure this) is just nonsense.

*** Bug 324801 has been marked as a duplicate of this bug. ***

Any progress or more consideration of this?  Currently additional repos can not
be  accessed behind network proxies, ruling out the especially nice ability to
catch the huge number of updates at install time.  I submitted an anaconda
updates patch (some related bug report, cant find it) a release or two ago -
only required a few lines of python to to at least take a proxy string from a
command line key.  The patch of course is broken now w/ current anaconda releases.

Ping?

Have not tested so far, don't run Fedora at the moment

This is something I am looking at adding support for as part of the rework of
install method code for F9.  Currently it looks like we will be able to support
proxies for downloading packages, but probably not for grabbing the stage2
image.  If you are booting off a CD and installing from a website, this will
work just fine for you.

That makes sense and yes it would work for me.  My particular case is a PXE grab
of stage 1 & 2 inside the firewall and then of course the want to pull the
updates through the proxy at install time.  I vainly imagine that many of the
enterprise folks would have similar setups.

I note though that this bug, or at least its ancestors, is circa F6. Must it
wait for F9? 

Anyone care to comment on their favorite work around du jour for proxy support,
in lieu of the fix?

Also, recommend
https://bugzilla.redhat.com/show_bug.cgi?id=125917 assigned to David Cantrell
and
https://bugzilla.redhat.com/show_bug.cgi?id=213109  assigned to Peter Jones
which are all filed against Anaconda be combined with this report. Who is the
real honcho on Anaconda these days?

Also, recommend
https://bugzilla.redhat.com/show_bug.cgi?id=125917 assigned to David Cantrell
and
https://bugzilla.redhat.com/show_bug.cgi?id=213109  assigned to Peter Jones
which are all filed against Anaconda be combined with this report. Who is the
real honcho on Anaconda these days?

We don't issue anaconda updates for released versions of Fedora, so it will have
to wait to make its official appearance in F9.  That doesn't mean work will
start post-F9, but that it will be in rawhide in the lead up to F9.  I've been
thinking about how to do this from a UI perspective, since it appears to be
pretty simple to enable in the backend.  Hopefully I will have something working
fairly soon.

There's now code to do this in F9 Alpha, at least in the graphical installer. 
You won't be able to get the stage2 image via proxy, but once you get into
selecting your packages you can modify the base repo and set up a proxy.  Can
someone please give this a test and see how well it works for them?  Thanks.

What's the reason that the stage2 image can't be downloaded via the proxy?  Is
it just a matter of 'round tuits' or is there something else getting in the way?

There's no code in the loader for handling HTTP proxies.  It could certainly be
added by someone with sufficient motivation, knowledge of HTTP, and free time
though.  I don't think it should be too terribly difficult.

Adding to F10Target for stage2 retrieval via proxy.

Reporter - note, however. that the new boot.iso/netinst.iso contains stage2 on
them, so the need for this is lessened - the only boot method by which you don't
get stage2 for free is via PXE now (admittedly probably the environment in which
this would be most valuable).

The likelihood of adding support for grabbing the stage2 image through a proxy
is pretty small unless we can find a nice lightweight library for fetching files
from a URL that also supports proxies.  I don't think anyone in anaconda land
has time for F10 to come up with proxy code on their own.

Of course, patches to anaconda-devel-list are always welcome too.

My hope for adding this proxy capability was to get access to updates and other
repos out on the net _in_ stage 2 package installs.  That capability is still
not available in Fedora 9 which I have just loaded. The proxy seems to only give
access to stage images.

In F9, you can select the base repo and enable a proxy on it.  The way this
works is as follows:

- On the task selection screen (the screen that lets you pick
Office/Server/Etc.) you should see a list of repos at the bottom.  One is
checked by default, and this one can't be unchecked.  It's the one you set up
when you answered the installation method question in the loader.  Highlight
that one and click "edit".
- The bottom half of the edit dialog has a proxy checkbox and then some entry
fields.  Check the box, fill it in, and click OK.

This should then mean that we'll use a proxy for fetching all files (including
the packages, which is the biggest part) from that repository.  Does this not work?

The screen in the loader really just needs to die, and probably will this time
around.

Hello

Fedora-11-i386-netinst.iso
anaconda 11.5.0.59

It would be better to ask for the proxy settings after the network settings.
Now we only get the Proxy settings mask/window if we disable DHCP and enter only a IP address and leave the Gateway and DNS empty.

I only come to select the packeges to be installed, but after that I get "Versuche Download erneut ..." and nothing happens.

A cancel button is missing too.

Please reopen this, it is not working.

On Fedora 16, after being asked about the network connection, the NetworkManager dialog hangs for minutes, after a while, I get a notification that the repotree wasn't being found (of course, the proxy hasn't been configured).

The proxy has to be configured *before* any network checks, otherwise it's useless.

Please open a new bug describing your new problem.

(In reply to comment #22)
> Please open a new bug describing your new problem.

Ok. Bug #752940.