1. Forum
  2. Usenet
  3. LINUX.DEBIAN.USER

  • auto-apt-proxy on trixie?

    From Charles Curley@21:1/5 to All on Sat Dec 21 04:20:01 2024
    auto-apt-proxy does not appear to be working fully on trixie. I have
    two trixie machines, one virtual, the other non-virtual (literal?). On
    the virtual machine auto-apt-proxy works just fine. It is NATted. The non-virtual machine has problems: it does not find my apt proxy, an
    instance of apt-cacher-ng. A bunch of bookworm machines, virtual and non-virtual, all work well.

    Because of the NATting for the VMs I have defined an alias for the
    cache in bind per the auto-apt-proxy man page. This works as expected,
    even on the non-virtual trixie machine. however, this shouldn't be
    necessary for the trixie non-virtual machine.

    The version on trixie is 15; 14.1 on bookworm. Just for the halibut I
    copied the bookworm version to the trixie machine, and that works
    correctly, suggesting a regression. Diffing the two gave me no ideas.
    The latest version gave no improvement.

    --
    Does anybody read signatures any more?

    https://charlescurley.com
    https://charlescurley.com/blog/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Frank Guthausen@21:1/5 to jeremy ardley on Sat Dec 21 11:50:01 2024
    On Sat, 21 Dec 2024 11:30:00 +0800
    jeremy ardley <jeremy.ardley@gmail.com> wrote:
    On 21/12/24 11:12, Charles Curley wrote:
    I have
    two trixie machines, one virtual, the other non-virtual (literal?).

    physical ?

    I guess ``bare metal'' describes it precicely. HTH
    --
    kind regards
    Frank

    -----BEGIN PGP SIGNATURE-----

    iQGzBAEBCgAdFiEE86z15c6qwvuAkhy+zDIN/uu9BloFAmdmnKQACgkQzDIN/uu9 BlrxNQv/di4H0GkHUTm92WmdEkdNkS9vlf8OuUUcAVltuU5zKt6MB8smq/brRHTE 7gmoIBR/+WtFz27Iq5okQixfeKyMXj2tzgxyNIpNsYumkxozwRJ35SBBDlj2tRNR tRRV+Ha1pGSxF539CDPfbxlXH3VooC6vRN8ckzLtbmaVTEB5f5b7kwFZQluQdD6h OPzKHPnUQA5fboPFyBF7X2idXOFlv0vX/Is2X5V8L7wlZ/2hx2FhB2cTEeRlmbjC wbWddDE21d9OsjPJz05QtqU0uFE+x1hW7fQ+me/LJYCsvvBbWHijQOsx32FuP90X ZKmuxk5TYdmmCp8U5wrzbGlxePUbbn8Fl0v94h7qL1G7aTk+luyCyHA7DUQzsgom EumansiXH2gIsYhlH8nDu0uT7un69KL7WDtVSe8smkSJ2/Nh8zw/bmNaN+smNB3U BRVcwlUc9vF+uzzoaASprwB950XXrW0IwLM89M0PkrcTtcftN4pvQlhuH7Lh/q8u
    /9us6A06
    =L4Gu
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Charles Curley@21:1/5 to Max Nikulin on Sun Dec 22 22:40:01 2024
    On Sun, 22 Dec 2024 09:42:40 +0700
    Max Nikulin <manikulin@gmail.com> wrote:

    On 21/12/2024 10:12, Charles Curley wrote:
    Because of the NATting for the VMs I have defined an alias for the
    cache in bind per the auto-apt-proxy man page. This works as
    expected, even on the non-virtual trixie machine.

    Disclaimer: I have never tried this tool.

    Have you compared results on machines where it works and where it
    does not (with your actual domain)?

    getent hosts _apt_proxy._tcp.YOUR.DOMAIN

    None of my hosts return anything from this except an error code of two.
    The man page says:

    2 One or more supplied key could not be found in the database.

    However, I tried setting up a SRV record, but could never get it to
    work. I did, however, successfully alias apt-proxy:

    root@cdtest:~# host apt-proxy
    apt-proxy.localdomain is an alias for issola.localdomain.
    issola.localdomain has address 192.168.100.12
    root@cdtest:~#

    This works on all machines, including the machine where auto-apt-proxy
    fails.


    Does this tool use multicast DNS? Is it configured on your trixie
    machine and on bookworm ones?

    The man page for auto-apt-proxy indicates that it will try MDNS, but I
    have not tried to set it up.


    grep hosts: /etc/nsswitch.conf



    On the trixie machine where auto-apt-proxy works:

    root@cdtest:~# grep hosts: /etc/nsswitch.conf
    hosts: files dns
    root@cdtest:~#

    On the trixie machine where it doesn't work:

    root@tiassa:~# grep hosts: /etc/nsswitch.conf
    hosts: files mdns4_minimal [NOTFOUND=return] dns
    root@tiassa:~#

    As a point of comparison, from one of the bookworm machines (on all of
    which auto-apt-proxy works):

    root@hawk:/usr/local/sbin# grep hosts: /etc/nsswitch.conf
    hosts: files mdns4_minimal [NOTFOUND=return] dns mymachines root@hawk:/usr/local/sbin#

    Just for the halibut, I took the mdns entry out of tiassa's
    nsswitch.conf:

    root@tiassa:~# grep hosts: /etc/nsswitch.conf
    hosts: files dns
    root@tiassa:~#

    and auto-apt-proxy still fails.

    --
    Does anybody read signatures any more?

    https://charlescurley.com
    https://charlescurley.com/blog/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)