惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

V
Visual Studio Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
G
Google Developers Blog
J
Java Code Geeks
爱范儿
爱范儿
Microsoft Azure Blog
Microsoft Azure Blog
美团技术团队
人人都是产品经理
人人都是产品经理
Martin Fowler
Martin Fowler
IT之家
IT之家
博客园_首页
B
Blog RSS Feed
Google DeepMind News
Google DeepMind News
B
Blog
U
Unit 42
Apple Machine Learning Research
Apple Machine Learning Research
L
LangChain Blog
Stack Overflow Blog
Stack Overflow Blog
罗磊的独立博客
N
Netflix TechBlog - Medium
T
Tailwind CSS Blog
博客园 - 聂微东
腾讯CDC
A
About on SuperTechFans

dnsmasq-discuss

[Dnsmasq-discuss] Announce: dnsmasq-2.92rc2 Re: [Dnsmasq-discuss] [PATCH] Fix arguments order for chaos subdomain check Re: [Dnsmasq-discuss] patch: block-file/allow-file - for review/feedback Re: [Dnsmasq-discuss] patch: block-file/allow-file - for review/feedback Re: [Dnsmasq-discuss] patch: block-file/allow-file - for review/feedback Re: [Dnsmasq-discuss] patch: block-file/allow-file - for review/feedback [Dnsmasq-discuss] patch: block-file/allow-file - for review/feedback Re: [Dnsmasq-discuss] server= with interface parameter changes behavior over time [Dnsmasq-discuss] NFTsets and hosts-files [Dnsmasq-discuss] [PATCH] Allow expired RRSIGs when stale caching is enabled [Dnsmasq-discuss] [PATCH] Fix local host records being overridden by upstream NXDOMAIN [Dnsmasq-discuss] [PATCH] Fix arguments order for chaos subdomain check Re: [Dnsmasq-discuss] Malformed RRSIG Can Crash dnsmasq [Dnsmasq-discuss] Malformed NSEC/NSEC3 Can Hang dnsmasq [Dnsmasq-discuss] Malformed RRSIG Can Crash dnsmasq [Dnsmasq-discuss] Security - IMPORTANT Re: [Dnsmasq-discuss] Issue with circuit-id matching on dhcp requests Re: [Dnsmasq-discuss] Issue with circuit-id matching on dhcp requests Re: [Dnsmasq-discuss] Issue with circuit-id matching on dhcp requests [Dnsmasq-discuss] Issue with circuit-id matching on dhcp requests Re: [Dnsmasq-discuss] [PATCH] bpf.c: fix memory leak in arp_enumerate() on BSD Re: [Dnsmasq-discuss] [PATCH] bpf.c: fix memory leak in arp_enumerate() on BSD Re: [Dnsmasq-discuss] dnssec problem here and now Re: [Dnsmasq-discuss] dnssec problem here and now [Dnsmasq-discuss] dnssec problem here and now Re: [Dnsmasq-discuss] server= with interface parameter changes behavior over time Re: [Dnsmasq-discuss] [PATCH] bpf.c: fix memory leak in arp_enumerate() on BSD Re: [Dnsmasq-discuss] [PATCH] bpf.c: fix memory leak in arp_enumerate() on BSD Re: [Dnsmasq-discuss] [PATCH] Preserve existing log file permissions when adding group-write bit. [Dnsmasq-discuss] server= with interface parameter changes behavior over time
[Dnsmasq-discuss] Shut down caused by device request addr...
Colin Finnis · 2026-02-22 · via dnsmasq-discuss
I have been running dnsmasq for some time on a Raspberry PI. I had no
problems until about 18 months ago when the DNS would suddenly stop working.
I found these types of entries in the syslog.

 

Feb 21 16:14:07 pilot dnsmasq-dhcp[2061]: DHCPACK(eth0) 192.168.0.242
02:ef:dd:91:3a:f3 Wild-s-S21

Feb 21 16:14:09 pilot dnsmasq-dhcp[2061]: DHCPREQUEST(eth0) 192.168.0.242
02:ef:dd:91:3a:f3 

Feb 21 16:14:09 pilot dnsmasq-dhcp[2061]: DHCPACK(eth0) 192.168.0.242
02:ef:dd:91:3a:f3 Wild-s-S21

Feb 21 16:14:09 pilot dhcpcd[377]: eth0: hardware address 02:ef:dd:91:3a:f3
claims 192.168.0.8

Feb 21 16:14:10 pilot dhcpcd[377]: eth0: hardware address 02:ef:dd:91:3a:f3
claims 192.168.0.8

Feb 21 16:14:10 pilot dhcpcd[377]: eth0: 10 second defence failed for
192.168.0.8

Feb 21 16:14:10 pilot dhcpcd[377]: eth0: deleting route to 192.168.0.0/24

Feb 21 16:14:10 pilot dhcpcd[377]: eth0: deleting default route via
192.168.0.1

Feb 21 16:14:10 pilot avahi-daemon[279]: Withdrawing address record for
192.168.0.8 on eth0.

 

The problem always seems to be associated with Samsung phones and appears to
have started after an update to the phone around 18 months ago. I have found
what purports to be a solution which requires a setting change on the phone.
This is fine for my phone but visitors to my house can cause the same
problem and its difficult to get them all to change before the damage is
done. It dosnt always happens when the phone is brought into the house, I
think it occur when the phone is close to the property and the signal is
poor.

 

As you can see the request is made for an address and the DNS responds. The
request is made a second time and immediately the device seems to take over
the IP address of the DNS box. DHCPD then goes into some sort of defence
mode and avahi withdraws the statically assigned address. I have tried
changing the address of the DNS server in case it was just the phone using a
random address but that made no difference. I cant run a network monitor on
the traffic so I cant see what is happen during this event. It just sems
strange behaviour for the phone to suddenly decide its going to usurp the
DNS's IP address.

 

Im technically savvy having worked in the IT industry for 40 years but cant
work out away to either prevent this or stop it happening. The only way at
the moment is to reboot the PI. Any help would be appreciated.

 

Colin Finnis

 

_______________________________________________
Dnsmasq-discuss mailing list
[email protected]
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss