DNS Issue with Static IP

[kram66]

I've got a Sonos Five speaker which seems to have a static IP address. Sonos support assure me this should not be static. I have not reserved this and can't seem to force a new IP for this device.
I have tried to manually assign a new IP to this, but it will not work.

There is an issue with this device as it seems to have an issue communicating with DNS as pinging the Sonos servers fails with "Bad Address". Is there a way to force a new DHCP address without a factory reset for this Sonos Speaker?

I'm using Merlin firmware 3004.388.8_4 on a ASUS RT-AX86U Pro with AiMesh Node RT-AC68U
DNS Servers 8.8.8.8 and 8.8.8.4

DHCP settings are default

 

[dave14305]

Is there an active lease for this on the System Log / DHCP Leases tab? With a long lease duration, it would be a while before it checks for a new address and assignment.

 

[bbunge]

With your DHCP Lease time set to one week (604800 seconds) it will be three and a half days before any of your clients try to renew the IP address. Maybe you should set the lease time back to one day (86400 is the default).

 

[RMerlin]

Turn off the client, adjust DHCP settings as desired, reboot the router to flush its lease cache, then turn the client back on. Only way to easily get rid of an undesirable lease.

Note that the client is highly likely to reuse the same IP address (if left dynamic) as dnsmasq tries to do that based on the client`s MAC.

 

[kram66]

Thanks for the advice, I did try that, but it states it's static. I have not reserved this IP. It seems this is the only client on my network that does not want to resolve the update server at Sonos. "Bad Address", so a DNS issue for this client only. Connecting to a VPN in the USA resolves this, but not a viable option for me. Sonos support are blaming my router.

 

[Tech9]

As per Sonos none of their products have static IP option. At Sonos Community forums there is a person with the same issue and Asus XT9 router. He was given advice to set the same static IP to different device, set desired DHCP IP reservation for Sonos, power up the other device first and power up Sonos after hoping this will force it to get the DHCP reserved IP. Test and see if this resolves the issue.

 

[dave14305]

Here are some commands to determine whether the router has any hidden configuration for this device.

nvram show 2>/dev/null | grep "78:80"
grep -R "78:80" /jffs/syslog.log* /etc/dnsmasq* /var/lib/misc/dnsmasq* /jffs/configs/ /jffs/scripts/
iptables-save | grep "78:80"

 

[kram66]

I powered off the Sonos device and assigned another device 192.168.1.247. Powered the Sonos on and the sonos still has the 192.168.1.247.

Here is the output of the code from the previous code.
nvram show 2>/dev/null | grep "78:80"

<SonosZP>34:7E:5C4:78:80>0>82>>>>>

grep -r "78:80" /jffs/syslog.log* /etc/dnsmasq* /var/lib/misc/dnsmasq* /jffs/configs/ /jffs/scripts/

/jffs/syslog.log-1:May 5 05:05:35 dnsmasq-dhcp[2265]: DHCPDISCOVER(br0) 192.168.1.247 34:7e:5c:d4:78:80
/jffs/syslog.log-1:May 5 05:05:35 dnsmasq-dhcp[2265]: DHCPOFFER(br0) 192.168.50.8 34:7e:5c:d4:78:80
/jffs/syslog.log-1:May 5 05:05:35 dnsmasq-dhcp[2265]: DHCPREQUEST(br0) 192.168.1.247 34:7e:5c:d4:78:80
/jffs/syslog.log-1:May 5 05:05:35 dnsmasq-dhcp[2265]: DHCPNAK(br0) 192.168.1.247 34:7e:5c:d4:78:80 wrong server-ID
/jffs/syslog.log-1:Apr 15 09:50:08 dnsmasq-dhcp[6632]: DHCPDISCOVER(br0) 192.168.1.247 34:7e:5c:d4:78:80
/jffs/syslog.log-1:Apr 15 09:50:08 dnsmasq-dhcp[6632]: DHCPOFFER(br0) 192.168.1.10 34:7e:5c:d4:78:80
/jffs/syslog.log-1:Apr 15 09:50:08 dnsmasq-dhcp[6632]: DHCPREQUEST(br0) 192.168.1.247 34:7e:5c:d4:78:80
/jffs/syslog.log-1:Apr 15 09:50:08 dnsmasq-dhcp[6632]: DHCPNAK(br0) 192.168.1.247 34:7e:5c:d4:78:80 wrong server-ID
/jffs/syslog.log-1:May 5 16:05:46 dnsmasq-dhcp[2314]: DHCPDISCOVER(br0) 192.168.1.247 34:7e:5c:d4:78:80
/jffs/syslog.log-1:May 5 16:05:46 dnsmasq-dhcp[2314]: DHCPOFFER(br0) 192.168.1.247 34:7e:5c:d4:78:80
/jffs/syslog.log-1:May 5 16:05:46 dnsmasq-dhcp[2314]: DHCPREQUEST(br0) 192.168.1.247 34:7e:5c:d4:78:80
/jffs/syslog.log-1:May 5 16:05:46 dnsmasq-dhcp[2314]: DHCPNAK(br0) 192.168.1.247 34:7e:5c:d4:78:80 wrong server-ID

iptables-save | grep "78:80"
doesn't return anything

 

[kram66]

I assigned my macbook the 247 address rebooted and confirmed it has the 247. Startup the Sonos and now my Mac complains about another device with the duplicate IP. Not sure where this is assigned.

 

[dave14305]

What is your router’s LAN IP? It seems there is another device on the LAN giving out IPs.

udhcpc -n -q -s /bin/true -t 1 -i br0
nvram get lan_ipaddr

 

[dave14305]

I'm using Merlin firmware 3004.388.8_4 on a ASUS RT-AX86U Pro with AiMesh Node RT-AC68U

Is the AC68U really a node or has it reverted to being a router? Worth checking based on the rogue DHCP server that seems to be present somewhere.

 

[kram66]

Is the AC68U really a node or has it reverted to being a router? Worth checking based on the rogue DHCP server that seems to be present somewhere.

It's a definitely a node.

/tmp/home/root# udhcpc -n -q -s /bin/true -t 1 -i br
0
udhcpc: started, v1.25.1
udhcpc: sending discover
udhcpc: no lease, failing


nvram get lan_ipaddr
192.168.1.1

I do have a managed switch, but let me check if that is using DHCP as well.

 

[dave14305]

Thanks. I was confused for a bit by the DHCP messages also giving out 192.168.50.xxx addresses at first, but then I realized your original screenshot showed the actual DHCP range.

Something is making the Sonos think the DHCP offer is coming from a different server-id than the router (or a DHCP server IP that doesn’t match the one assigned to the router’s LAN interface).

May 5 16:05:46 dnsmasq-dhcp[2314]: DHCPDISCOVER(br0) 192.168.1.247 34:7e:5c:d4:78:80
May 5 16:05:46 dnsmasq-dhcp[2314]: DHCPOFFER(br0) 192.168.1.247 34:7e:5c:d4:78:80
May 5 16:05:46 dnsmasq-dhcp[2314]: DHCPREQUEST(br0) 192.168.1.247 34:7e:5c:d4:78:80
May 5 16:05:46 dnsmasq-dhcp[2314]: DHCPNAK(br0) 192.168.1.247 34:7e:5c:d4:78:80 wrong server-ID

 

[bennor]

How is the Sonos Five connected to the network? By WiFi or by Ethernet?
A suggestion or two. Maybe take a step back and start from scratch. Disconnect all other network devices, including any AiMesh nodes or AP nodes so it is just the main router, one wired PC, and the Sonos Five speaker. That might help rule out another device causing a problem with the Sonos.
If the Sonos is connected via WiFi instruct it to forget the WiFi connection and if possible have it forget any prior saved WiFi connection, then reconnect the Sonos to the WiFi.
If Sonos Five is using WiFi, try the Ethernet port instead.
Try doing a factory reset (if possible) on the Sonos and reconnect it to the network.
If you have a long list of manual IP reservations, double check that list for any other Sonos entries.
Maybe take a stab at the router's NVRAM to see if the IP address the Sonos is using is listed there and if so which NVRAM value it is.
As a last resort, hard factory reset the router and configure it manually from scratch. Including setting a different local IP subnet range from the previous one. Then connect only the Sonos (no AiMesh nodes) and see if the issue continues.

 

[dave14305]

@kram66 If you have Entware installed, it would be worthwhile to install tcpdump from Entware and capture the DHCP conversation between the router and the Sonos.

opkg update
opkg install tcpdump
tcpdump -pnvvei br0 udp and port 67 and ether host 34:7e:5c:d4:78:80

Then power-cycle the Sonos and watch the messages in tcpdump. I'd be interested in the output to see what Server-ID the Sonos is sending back.