Quantcast
Channel: Debian User Forums
Viewing all articles
Browse latest Browse all 2681

Installation • Re: Debian 11 install does not have default gateway route?

$
0
0
A bit of context, I am a 30 year IT career support person, with over 15 years experience with VMware, not to mention Hyper-V, KVM, etc. And I just built a Debian 11 based VM using VMware Player 16 on Windows 10, and it has no default gateway configured, even though I am using a valid DHCP server that is sending the gateway information request back to the VM. The physical NIC is in bridged mode, not using NAT, I have built 100s if not 1000s of VMs over the years, with various OSes, and this issue is driving me nuts... It is not common but not exactly in frequent, that Linux OS based VMs have some odd quirks at times. But this issue is being really stubborn to resolve.

[...]

The question is, has anyone else seem this odd behavior, in VMware Player on Windows 10 and attempting to install Debian 11?
@Jibun no Kage, I wonder if you found an explanation.

I see the same symptoms, but also have some differences in my circumstances:

- I have lots of linux experience (redhat/ubuntu), but this is my first Debian install
- my hypervisor is Proxmox 8.1 (nested under Vmware Workstation 16, running on Win 10 LTSC)
- VM is Debian 12, installed also from the debian-12.5.0-amd64-netinst.iso image, with all options at default, except no desktop environment
- Proxmox VM uses the q35 chipset, all other VM options default.
- my DHCP server is dnsmasq running on another reliable linux box, and the debian install was served the following lease (uses option 121/classless routing):

Code:

lease {  interface "enp6s18";  fixed-address 192.168.7.197;  option subnet-mask 255.255.255.0;  option routers 192.168.7.11;  option dhcp-lease-time 180;  option dhcp-message-type 5;  option domain-name-servers 192.168.7.11;  option dhcp-server-identifier 192.168.7.11;  option dhcp-renewal-time 79;  option rfc3442-classless-static-routes 24,192,168,20,192,168,20,11,0,192,168,20,10;  option broadcast-address 192.168.7.255;  option dhcp-rebinding-time 143;  option host-name "dock";  option domain-name "br8.sun.[redacted]";  renew 4 2024/04/25 06:32:39;  rebind 4 2024/04/25 06:33:57;  expire 4 2024/04/25 06:34:34;}
The dmesg ends with the following suspicious messages:

Code:

[    3.286916] audit: type=1400 audit(1714023676.988:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=464 comm="apparmor_parser"[    3.286921] audit: type=1400 audit(1714023676.988:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=464 comm="apparmor_parser"[    3.286923] audit: type=1400 audit(1714023676.988:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=464 comm="apparmor_parser"

They are suspicious because the paths '/usr/lib/NetworkManager/nm-dhcp-helper' and '/usr/lib/connman/scripts/dhclient-script' do not exist, although '/usr/sbin/dhclient-script' does exist.
However, '/usr/sbin/dhclient-script' is not installed by any package ('dpkg -S /usr/sbin/dhclient' reports 'dpkg-query: no path found matching pattern /usr/sbin/dhclient-script').
The files named 'nm-dhcp-client.action' and 'nm-dhcp-helper' do not exist anywhere (i.e., 'find / -name nm-dhcp-helper' finds nothing; dpkg -S finds no owner package)

On my network, as seen in the lease above from option 121/rfc3442-classless-static-routes, the default prefix /0 is routed via 192.168.20.10 which is not in the same subnet as the lease address 192.168.7.197/24; this is arguably a misconfiguration for leases in the 192.168.7.0/24 subnet, but other DHCP clients correctly use the the 192.168.7.11 default router, and I would expect the debian dhcp client hooks to also see 192.168.20.10 as a "non-applicable" configuration, and not a reason to leave the machine in an unusable state.

The absence of '/usr/lib/connman/scripts/dhclient-script' seems like a smoking gun to me.

If I reinstall from the same ISO, but with the default Desktop environment (gnome):
- the dmesg suspicious messages do not appear.
- the 'network-manager: /usr/lib/NetworkManager/nm-dhcp-helper' ownership exists in dpkg
- the '/usr/lib/connman/scripts/dhclient-script' file still does not exist
- the dhclient process is not running
- the routing table reflects option 121 supplied by the DHCP server, while the 192.168.7.11 is still not used as default, as shown below
- there are no (lease) files in '/var/lib/dhcp/'

Code:

root@dock:~# ip route listdefault via 192.168.20.10 dev ens18 proto dhcp src 192.168.7.127 metric 100192.168.7.0/24 dev ens18 proto kernel scope link src 192.168.7.127 metric 100192.168.20.0/24 via 192.168.20.11 dev ens18 proto dhcp src 192.168.7.127 metric 100192.168.20.10 dev ens18 proto dhcp scope link src 192.168.7.127 metric 100192.168.20.11 dev ens18 proto dhcp scope link src 192.168.7.127 metric 100
In this case (with a desktop environment), the network system is more functional, but dhclient is not running.

Statistics: Posted by rh009 — 2024-04-25 07:02



Viewing all articles
Browse latest Browse all 2681