On Sat, Jan 18, 2003 at 07:47:52PM -0500, Matt Zimmerman wrote: > On Thu, Jan 16, 2003 at 10:53:27PM -0500, Peter J. Farley III wrote: > > > 0% [Connecting to 192.168.0.1 (198.168.0.1)] > > Err http://security.debian.org stable/updates/main Packages > > Could not connect to 192.168.0.1:3128 (192.168.0.1), connection timed out > > ... > > Failed to fetch > > http://security.debian.org/dists/stable/updates/main/binary-s390/Packag > > es Could not connect to 192.168.0.1:3128 (192.168.0.1), connection > > timed out > > 192.168.0.1:3128 happens to be where my Squid proxy is. Did that bit of > configuration leak into the image that I built somewhere? I'm away from > home right now and can't check it, but it should be simple to fix when I get > back if this is the case.
I have returned home and had a chance to look into this, and upon inspection it appears that the image is fine. When initial configuration runs (when you telnet into it), http://192.168.0.1:3128 will be given as the _default_ proxy address, but you are prompted to change it and it is not used for anything until after this point. "Enter http proxy information, or leave blank for none:" -- - mdz
