tom17
June 23rd, 2011, 03:58 PM
Hi,
I have 11.04 installed on a spare machine at work. All of a sudden, a couple of days ago, installing packages or updates started failing.
$ sudo aptitude update
Err http://ca.archive.ubuntu.com natty InRelease
Err http://ca.archive.ubuntu.com natty-updates InRelease
Err http://security.ubuntu.com natty-security InRelease
Err http://extras.ubuntu.com natty InRelease
Err http://ca.archive.ubuntu.com natty Release.gpg
Unable to connect to 172.22.4.200:8080:
Err http://security.ubuntu.com natty-security Release.gpg
Unable to connect to 172.22.4.200:8080:
Err http://ca.archive.ubuntu.com natty-updates Release.gpg
Unable to connect to 172.22.4.200:8080:
Err http://extras.ubuntu.com natty Release.gpg
Unable to connect to 172.22.4.200:8080:
Err http://dl.google.com stable InRelease
Err http://dl.google.com stable Release.gpg
Unable to connect to 172.22.4.200:8080:
Now I checked with a browser and wget and I am able to get to all of the domains mentioned even though aptitude appears not to be able to. I am also able to use wget to fetch the files such as http://ca.archive.ubuntu.com/ubuntu/dists/natty/Release.gpg.
Now, we did recently change our internet access at work. It used to be proxies (which did not work too well with Ubuntu and updates) but we are now using some DPI firewall, I believe. From what I can tell, the URL that I go to with wget is the same URL that aptitude/apt-get is using, yet they fail and wget does not. Could the DPI be looking at the host header sent in the HTTP requests from aptitude? Is it possible to check/change what it sends as its host header? Do they use port 80? (i'm not sure where that 172.11.4.200:8080 is coming from).
Or could it just be another problem with aptitude? I saw some people with similar errors on here but nothing helpful to me.
Thanks,
Tom...
I have 11.04 installed on a spare machine at work. All of a sudden, a couple of days ago, installing packages or updates started failing.
$ sudo aptitude update
Err http://ca.archive.ubuntu.com natty InRelease
Err http://ca.archive.ubuntu.com natty-updates InRelease
Err http://security.ubuntu.com natty-security InRelease
Err http://extras.ubuntu.com natty InRelease
Err http://ca.archive.ubuntu.com natty Release.gpg
Unable to connect to 172.22.4.200:8080:
Err http://security.ubuntu.com natty-security Release.gpg
Unable to connect to 172.22.4.200:8080:
Err http://ca.archive.ubuntu.com natty-updates Release.gpg
Unable to connect to 172.22.4.200:8080:
Err http://extras.ubuntu.com natty Release.gpg
Unable to connect to 172.22.4.200:8080:
Err http://dl.google.com stable InRelease
Err http://dl.google.com stable Release.gpg
Unable to connect to 172.22.4.200:8080:
Now I checked with a browser and wget and I am able to get to all of the domains mentioned even though aptitude appears not to be able to. I am also able to use wget to fetch the files such as http://ca.archive.ubuntu.com/ubuntu/dists/natty/Release.gpg.
Now, we did recently change our internet access at work. It used to be proxies (which did not work too well with Ubuntu and updates) but we are now using some DPI firewall, I believe. From what I can tell, the URL that I go to with wget is the same URL that aptitude/apt-get is using, yet they fail and wget does not. Could the DPI be looking at the host header sent in the HTTP requests from aptitude? Is it possible to check/change what it sends as its host header? Do they use port 80? (i'm not sure where that 172.11.4.200:8080 is coming from).
Or could it just be another problem with aptitude? I saw some people with similar errors on here but nothing helpful to me.
Thanks,
Tom...