Package: auto-apt-proxy
Version: 13.1
Severity: normal
Dear Maintainer,
First of all, thanks for auto-apt-proxy!
I just got started with it. My setup is simple, I have apt-cacher-ng
running on my machine, and that's it. So everything should "just work"
:)
After installing, I tried to run 'auto-apt-proxy'. It takes about 15
seconds to complete, quite disappointing.
$ time auto-apt-proxy
http://127.0.0.1:3142
real 0m15.183s
user 0m0.136s
sys 0m0.071s
So I tried again with 'bash -x' option to see what was going on. It
turns out that the line that checks for an explicit proxy returns an IP,
but that's definitely not what we want:
++ getent hosts apt-proxy
++ awk '/[:blank:]/ { print($1) }'
+ explicit_proxy=125.235.4.59
This IP seems to be something more or less generic for any unknown host,
from what I can tell. For example, if I run:
$ nslookup asfdsafesgraefdsge
Server: 192.168.1.1
Address: 192.168.1.1#53
Non-authoritative answer:
Name: asfdsafesgraefdsge
Address: 125.235.4.59
Seems to be some ISP specific stuff though, in this case I'm accessing
Internet via ISP Viettel. I also tried with another connection (going
through my phone, hence 3G network), and it looks more "normal":
$ nslookup asfdsafesgraefdsge
Server: 192.168.43.161
Address: 192.168.43.161#53
** server can't find asfdsafesgraefdsge: NXDOMAIN
$ getent hosts asfdsafesgraefdsge
... return nothing ...
$ echo $?
2
Don't have a patch to submit yet, I'm really no expert in network things
like that. But I'll dig a bit and be back soon, I hope.
Cheers!
Arnaud
----
Versions of packages auto-apt-proxy depends on:
ii apt 2.2.2
Versions of packages auto-apt-proxy recommends:
ii busybox 1:1.30.1-6+b1
ii iproute2 5.10.0-4
