On 2023-04-05 12:30, Per Jessen wrote:
Carlos E. R. wrote:
lease { [snip] } Laicolasse:~ #
See? No search item.
Yes I see it - with that, we can deduce your weird searchlist setting is coming from your system itself.
Yes.
And an ntp item I knew nothing about.
Bit of an odd one, with no route to 10.x.x.x, it's pointless. Do you see it in your chrony/ntp config? (just being curious). You can probably access it if you add a route for that network.
Oh, I can alright: Laicolasse:~ # traceroute 10.22.64.1 traceroute to 10.22.64.1 (10.22.64.1), 30 hops max, 60 byte packets 1 router.valinor (192.168.1.1) 2.509 ms 2.587 ms 2.722 ms 2 * * * 3 * * * 4 * * * Maybe it responds to a time request. It is external, on the ISP network. The router has an VLAN for it, I think (not documented). Laicolasse:~ # grep 10.22.64.1 /etc/chrony* /etc/chrony.conf:pool 10.22.64.1 iburst grep: /etc/chrony.d: Is a directory Laicolasse:~ # grep 10.22.64.1 /etc/chrony*/* Laicolasse:~ # Wow, it is there indeed. :-o Does it work?
Laicolasse:~ # grep 10.22.64.1 /var/log/messages 2023-04-05T04:07:32.570230+02:00 Laicolasse chronyd[1844]: Source 10.22.64.1 offline 2023-04-05T11:00:51.733335+02:00 Laicolasse chronyd[1844]: Source 10.22.64.1 online 2023-04-05T12:26:23.161658+02:00 Laicolasse chronyd[1844]: Source 10.22.64.1 offline 2023-04-05T12:26:33.960313+02:00 Laicolasse chronyd[1844]: Source 10.22.64.1 online Laicolasse:~ #
It seems to work, yes. :-o Means I can not define a 10* network myself. I think virtualbox does. What port uses chrony? Ah, 123. TCP or UDP? Trying both. Laicolasse:~ # traceroute --port=123 --protocol=TCP 10.22.64.1 traceroute to 10.22.64.1 (10.22.64.1), 30 hops max, 60 byte packets 1 * router.valinor (192.168.1.1) 22.276 ms 1.400 ms 2 * * * 3 * * router.valinor (192.168.1.1) 2600.757 ms 4 router.valinor (192.168.1.1) 2.602 ms 1.347 ms * 5 * * * 6 * * * 7 * * * 8 * * * ... 30 * * * Laicolasse:~ # Laicolasse:/etc/NetworkManager/dispatcher.d # traceroute --port=123 --protocol=UDP 10.22.64.1 traceroute to 10.22.64.1 (10.22.64.1), 30 hops max, 60 byte packets 1 router.valinor (192.168.1.1) 3.854 ms 1.666 ms 1.385 ms 2 * * * 3 * * * 4 * * * ... 30 * * * Laicolasse:/etc/NetworkManager/dispatcher.d #
Ok, if I now change NETCONFIG_DNS_POLICY to auto, I get:
Laicolasse:~ # tail /etc/resolv.conf | egrep -v "^[[:space:]]*$|^#" search Laicolasse.valinor nameserver 127.0.0.1 nameserver 80.58.61.254 nameserver 80.58.61.250 Laicolasse:~ #
Ah, see, the search line is broken.
Yes, that is the real issue. I have no idea why the hostname is being prepended. Wild guess - anything odd in /etc/hosts ?
It is impossible to get the damn file completely right.
Well, it works for me, so we just have to figure out what's wrong with yours.
My laptop uses NM, I think your machine doesn't. I have just made an adjust to the /etc/hosts file, now it contains a proper entry for the hostname. So let's try again. No. still "search Laicolasse.valinor". In case you are curious, I have "/etc/NetworkManager/dispatcher.d/90mine" which updates /etc/hosts dynamically to the actual IP address I get each time. I just activated this minutes ago. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)