ks10596
February 7th, 2018, 02:33 PM
I have a ssh socks 5 connection running on port 4430 (ssh -D 4430 user@host) and want to route traffic for apt-get over the proxy. I have installed tsock with the following in the tsocks.conf: server = 127.0.0.1, server_type = 5 and server_port = 4430. Everything else is commented out. I am implementing it by running 'tsocks apt-get -y upgrade' but it always seems to get stuck at the same place:
279 upgraded, 0 newly installed, 0 to remove and 16 not upgraded.Need to get 11.3 MB/256 MB of archives.
After this operation, 122 MB of additional disk space will be used.
96% [Working]
I am not sure why it gets stuck here or how to find out what the problem is. Any suggestions would be helpful.
Update
I have quit using tsock and decided to try to make the entries in /etc/apt/apt.conf:
Acquire::http::proxy "http://localhost:4430";
Acquire::https::proxy "https://localhost:4430";
Acquire::ftp::proxy "ftp://localhost:4430";
Now I see alot of entries like:
Ign:1 https://deb.nodesource.com/node_7.x xenial InRelease
Ign:2 https://deb.nodesource.com/node_7.x xenial Release
Ign:3 https://deb.nodesource.com/node_7.x xenial/main Sources.diff/Index
Ign:4 https://deb.nodesource.com/node_7.x xenial/main amd64 Packages.diff/Index
Ign:5 https://deb.nodesource.com/node_7.x xenial/main i386 Packages.diff/Index
Ign:6 https://deb.nodesource.com/node_7.x xenial/main all Packages
I see some entries like :
Err:8 https://deb.nodesource.com/node_7.x xenial/main Sources
Proxy CONNECT aborted
or
Err:107 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
Connection failed
Ultimately it ends with :
Reading package lists... Done
W: The repository 'https://deb.nodesource.com/node_7.x xenial Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'http://us.archive.ubuntu.com/ubuntu xenial Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'http://us.archive.ubuntu.com/ubuntu xenial-updates Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'http://us.archive.ubuntu.com/ubuntu xenial-backports Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'http://security.ubuntu.com/ubuntu xenial-security Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch https://deb.nodesource.com/node_7.x/dists/xenial/main/source/Sources Proxy CONNECT aborted
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial-backports/restricted/binary-amd64/Packages Connection failed
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial/main/binary-amd64/Packages Connection failed
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-amd64/Packages Connection failed
E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/main/binary-amd64/Packages Connection failed
E: Some index files failed to download. They have been ignored, or old ones used instead.
So, it seems like communication is happening but I do not understand why some individual connections fail or information about data cannot be authenticated.
279 upgraded, 0 newly installed, 0 to remove and 16 not upgraded.Need to get 11.3 MB/256 MB of archives.
After this operation, 122 MB of additional disk space will be used.
96% [Working]
I am not sure why it gets stuck here or how to find out what the problem is. Any suggestions would be helpful.
Update
I have quit using tsock and decided to try to make the entries in /etc/apt/apt.conf:
Acquire::http::proxy "http://localhost:4430";
Acquire::https::proxy "https://localhost:4430";
Acquire::ftp::proxy "ftp://localhost:4430";
Now I see alot of entries like:
Ign:1 https://deb.nodesource.com/node_7.x xenial InRelease
Ign:2 https://deb.nodesource.com/node_7.x xenial Release
Ign:3 https://deb.nodesource.com/node_7.x xenial/main Sources.diff/Index
Ign:4 https://deb.nodesource.com/node_7.x xenial/main amd64 Packages.diff/Index
Ign:5 https://deb.nodesource.com/node_7.x xenial/main i386 Packages.diff/Index
Ign:6 https://deb.nodesource.com/node_7.x xenial/main all Packages
I see some entries like :
Err:8 https://deb.nodesource.com/node_7.x xenial/main Sources
Proxy CONNECT aborted
or
Err:107 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
Connection failed
Ultimately it ends with :
Reading package lists... Done
W: The repository 'https://deb.nodesource.com/node_7.x xenial Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'http://us.archive.ubuntu.com/ubuntu xenial Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'http://us.archive.ubuntu.com/ubuntu xenial-updates Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'http://us.archive.ubuntu.com/ubuntu xenial-backports Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'http://security.ubuntu.com/ubuntu xenial-security Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch https://deb.nodesource.com/node_7.x/dists/xenial/main/source/Sources Proxy CONNECT aborted
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial-backports/restricted/binary-amd64/Packages Connection failed
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial/main/binary-amd64/Packages Connection failed
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-amd64/Packages Connection failed
E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/main/binary-amd64/Packages Connection failed
E: Some index files failed to download. They have been ignored, or old ones used instead.
So, it seems like communication is happening but I do not understand why some individual connections fail or information about data cannot be authenticated.