DNSMASQ 中的 DHCP 无法满足 IP 地址请求

DNSMASQ 中的 DHCP 无法满足 IP 地址请求

由于网络中的设备丢失,在另一台服务器上引入了新的 DNSMASQ 配置。该服务器恰好是 Raspberry Pi 4B。许多设备能够获取 IP 地址,但有些设备(特别是 Windows 10 设备)在 DHCP 请求上超时。这是新情况;之前 DHCP 没有已知问题,我没有任何理由认为此配置有偏差。配置如下:

# Use interface wlan0
#interface=eth0
#interface=lo
#interface=wlan0

listen-address=10.158.54.3
listen-address=127.0.0.1

bind-interfaces

# Don't forward unqualified names (hpmicro1)...
domain-needed

# Don't forward some non-routed addresses
bogus-priv

# don't forward requests for the intranet subdomain
local=/lovelady.com/

# Assign addresses between 10.158.54.65 and 10.158.54.200 with a 24 hour lease time
dhcp-range=10.158.54.101,10.158.54.200,12h

# Forward DNS requests to the local DNS and then Google DNS
server=10.158.54.3
server=8.8.8.8
server=8.8.4.4

dhcp-option=option:router,10.158.54.1    # Default gateway
dhcp-option=6,10.158.54.3               # DNS (that's me)

# append domain to all hosts
domain=lovelady.com

expand-hosts # Add domain also to any simple names in /etc/hosts    

dhcp-host=b4:2e:99:a2:58:77,Velmicro
dhcp-host=ac:1f:6b:17:f6:25,NAS-1,10.158.54.10
dhcp-host=ac:1f:6b:9a:cb:6c,PLEX-NAS1
dhcp-host=b8:27:eb:ba:a0:7b,pi-in-the-sky
dhcp-host=00:1c:d2:f1:94:3d,inet-radio
dhcp-host=38:f7:3d:b1:12:3f,Amazon-BSMT
dhcp-host=fc:a1:83:43:30:76,Amazon-LivRm
dhcp-host=20:df:b9:57:9d:46,Google-Home
dhcp-host=b8:27:eb:9b:e1:91,octopi-w,10.158.54.20
dhcp-host=50:87:b8:00:8e:46,luvtablo

非常感谢您提供的任何帮助...

答案1

事实证明,有关超时的消息具有误导性。显然,自 Windows 10 的最新版本以来,系统将有时尝试重置环回接口(又名 localhost 或 127.0.0.1),这就是错误所说的内容。当 windows 最终在环回接口上超时后,它获得了其他适用接口的 IP 地址。Windows 不应该尝试重置 localhost 接口,通常它不会这样做。但它显然有情绪。

相关内容