[lime-users] DHCP conflicts

Hi all I've finally had the chance to test out what some of you were saying about LiMe doing mesh over ethernet using Lan - to - Lan connections. I have a POE switch with one cable going to a UBNT AC lite, one going to a Bullet M2, one going to a 1043ND [on its wan port] and one to an Archer C7 [on its wan port]. All 4 devices have the latest images downloaded from repo.libremesh.org, just to be on the safe side. The fifth cable is going to my ISP router [IP 192.168.111.1]. Since the lite and the bullet only have one ethernet port, stock lime configures it as a Lan port, with 10.13.0.x DHCP being handed out over it, and so on. So from the switch I have two cables going to wan ports [1043 and C7] and two going to "Lan" ports [lite and bullet] since that's what their default behavior is. They all mesh correctly, and even the two UBNTs serve internet connectivity perfectly. The problem is that when I connect to these two devices wirelessly with clients, I often get a DHCP assignment from my ISP router [as it's on the 192.168.111.x subnet] and not a 10.13.0.x assignment. I still don't understand how a network with not one, but several DHCP servers can work correctly. I seem to understand that LiMe can ignore such advertisements on its Lan ports, but what happens to a client that is on such wired network, say, with another cable from the switch I mentioned? Won't he receive advertisements from all servers at once? Does LiMe terminate advertisements upstream-bound when it detects others? And in the case of the 1043 and C7 that are using their wan ports, how does LiMe understand when it should mesh with other devices over it and when it should become a DHCP client to an upstream non-mesh router in a traditional way? And how do I solve this DHCP leaking from ISP router to LiMe routers' clients in the case of the lite and bullet? Thank you in advance Nk