2 Jul
2017
2 Jul
'17
5:02 p.m.
On Sun, 2017-07-02 at 18:30 +0200, Nikksno via lime-users wrote:
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.
Yes!
That is because DHCP requests are coming from your devices to your UBNT
AP, from there they move the DHCP request to the switch, and as the
request goes to the broadcast address, the switch sends the packet to
all the devices at the same time... so the one that replies faster is
the response that the devices accepts.
I still don't understand how a network with not
one, but several DHCP
servers can work correctly.
LibreMesh DHCPs can live together because they know of their
presence... the external DHCP should be connected to one single Mesh
node.
Mesh nodes that belong to the same network (the AC Lites, the Archer C7
and 1034ND) can connect between each other through the LAN ports.
Your ISP router should be connected to the WAN port of any of those
devices.