An answer "yes" to "A or B, if B, why?" is hard to understand
. The thing is that the first byte of a MAC address must normally not be odd (as an opposite of even, not as a synonym of strange) because that's a multicast address indicator. So I suppose you had to set a MAC address of your previous equipment to get your public IP from your ISP, but the MAC address is a normal one, with the LSB of the first byte equal to 0.
OK, so what do the devices that report no internet have in common? If you don't specify a DNS server on the
/ip dhcp-server network row, Mikrotik tells its DHCP clients to use the DNS servers it uses itself, and yours gets the server addresses via DHCP from the ISP. So you may try to add
dns-server=192.168.0.1 to that row and let the client devices re-request their IP configuration, but it's kind of cargo cult advice - I've got no real arguments why this should have an impact, it's just that many devices detect internet availability by sending DNS requests. And my speculation is that if they get (a) public IP of the DNS server(s), they may behave different in some regard.