Turris Omnia distributing wrong IP addresses via DHCP

Software SW help
1

Hey I’m using the Omnia with the latest update 3.8.5 and I have noticed problems with the IP address distribution.
For some reason the router assigns addresses in the wrong subnet for two of my devices (different hardware, one is a Linux and one is a Windows device), this leads to the clients having no internet connection.

The turris is 192.168.1.1 and those devices receive an address in 192.168.0.xxx. They also don’t appear on the active DHCP leases page in luci.

That’s what appears in the system log:

2017-11-18T17:54:08+01:00 info hostapd[]: wlan1: STA 50:1a:c5:a3:15:b1 IEEE 802.11: authenticated
2017-11-18T17:54:08+01:00 info hostapd[]: wlan1: STA 50:1a:c5:a3:15:b1 IEEE 802.11: associated (aid 1)
2017-11-18T17:54:14+01:00 info hostapd[]: wlan1: STA 50:1a:c5:a3:15:b1 IEEE 802.11: authenticated
2017-11-18T17:54:14+01:00 info hostapd[]: wlan1: STA 50:1a:c5:a3:15:b1 IEEE 802.11: associated (aid 1)
2017-11-18T17:54:23+01:00 info hostapd[]: wlan1: STA 50:1a:c5:a3:15:b1 IEEE 802.11: deauthenticated due to local deauth request
2017-11-18T17:55:01+01:00 info /usr/sbin/cron[29751]: (root) CMD (   /usr/bin/notifier)
2017-11-18T17:55:01+01:00 info /usr/sbin/cron[29753]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2017-11-18T17:55:01+01:00 info /usr/sbin/cron[29756]: (root) CMD (/usr/bin/watchdog.sh)
2017-11-18T17:55:01+01:00 info /usr/sbin/cron[29755]: (root) CMD (majordomo_db.sh downsize)
2017-11-18T17:56:01+01:00 info /usr/sbin/cron[30333]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2017-11-18T17:56:01+01:00 info /usr/sbin/cron[30334]: (root) CMD (nethist_stats.lua)
2017-11-18T17:56:13+01:00 info hostapd[]: wlan1: STA 50:1a:c5:a3:15:b1 IEEE 802.11: authenticated
2017-11-18T17:56:13+01:00 info hostapd[]: wlan1: STA 50:1a:c5:a3:15:b1 IEEE 802.11: associated (aid 1)
2017-11-18T17:56:13+01:00 info hostapd[]: wlan1: STA 50:1a:c5:a3:15:b1 RADIUS: starting accounting session 2DXXXXXXXXX708
2017-11-18T17:56:13+01:00 info hostapd[]: wlan1: STA 50:1a:c5:a3:15:b1 WPA: pairwise key handshake completed (RSN)
2017-11-18T18:56:16+01:00 info dnsmasq-dhcp[3326]: DHCPDISCOVER(br-lan) 50:1a:c5:a3:15:b1 
2017-11-18T18:56:16+01:00 info dnsmasq-dhcp[3326]: DHCPOFFER(br-lan) 192.168.1.191 50:1a:c5:a3:15:b1 
2017-11-18T18:56:16+01:00 info dnsmasq-dhcp[3326]: DHCPREQUEST(br-lan) 192.168.0.11 50:1a:c5:a3:15:b1 
2017-11-18T18:56:16+01:00 info dnsmasq-dhcp[3326]: DHCPNAK(br-lan) 192.168.0.11 50:1a:c5:a3:15:b1 wrong server-ID
2017-11-18T18:56:16+01:00 info dnsmasq-dhcp[3326]: DHCPINFORM(br-lan) 192.168.0.11 50:1a:c5:a3:15:b1 
2017-11-18T18:56:16+01:00 info dnsmasq-dhcp[3326]: DHCPACK(br-lan) 192.168.0.11 50:1a:c5:a3:15:b1 LAPTOP-531337
2017-11-18T18:56:20+01:00 info dnsmasq-dhcp[3326]: DHCPINFORM(br-lan) 192.168.0.11 50:1a:c5:a3:15:b1 
2017-11-18T18:56:20+01:00 info dnsmasq-dhcp[3326]: DHCPACK(br-lan) 192.168.0.11 50:1a:c5:a3:15:b1 LAPTOP-531337
2017-11-18T18:56:23+01:00 info dnsmasq-dhcp[3326]: DHCPINFORM(br-lan) 192.168.0.11 50:1a:c5:a3:15:b1 
2017-11-18T18:56:23+01:00 info dnsmasq-dhcp[3326]: DHCPACK(br-lan) 192.168.0.11 50:1a:c5:a3:15:b1 LAPTOP-531337

Any Ideas whats the problem or how to further trubleshoot?
Thx in advance!

2

You described your problem but there is no mention of how you set it exactly! How to distinguish members of individual groups.Youre DHCP rules.

3

check that you dont have multiple DHCP server in your network, and also check your exact dhcp settings. Please note that if they are VMs, virtualization softwares like Virutalbox can act as a dhcp servers as well and they can create bridged network interfaces on a different subnet

4

So I cannot reproduce the problem since 1,5 weeks.
Strange thing, that it happened during 3 days across different devices and operating systems.