DHCP user oversight: DHCP config'd for 192.168.. but device has 192.68..

Problem appeared as inability to ping between subnets on a hAPaclite with RoS 6.49. Eth3 was set as 192.168.88.1, offering DHCP service. The bridge serves 192.168.1.x on all other interfaces. After much time wasted, I noticed that the IP address of a computer connected by cable to Eth3 showed its IP as 192.68.88.x and not 192.168… Used the route list section (in Winbox) to remove the route to Eth3 (which showed it was active and connected as 192.168.88..) and configured it again, using 192.168.88.. for the address range. Still getting 192.68… on two computers (openSuse 15.4 and Fedora 36, one at a time). I’m not sure what information to provide for anyone to see how this happens. Any hints where a typo like 192.68.. might be buried? Thanks.

In your config, obviously.

Could be your DHCP server :wink:, think you want to check your pool.

Thankyou elinden; found the typo for the address range in the pool config. Strange that the dhcp pool is not accessible from the DHCP server window. Still no connection on ..88.x subnet; computer not getting IP address via dhcp. Will look at firewall rules for the input chain.