3 Jul
2017
3 Jul
'17
8:20 a.m.
On July 2, 2017 8:31:44 PM GMT+03:00, Nk via lime-users <lime-users@lis
ts.libremesh.org> wrote:
Thank you Nicolas, so what you're saying is that
instead of
connecting
the ISP router to the switch, and then having cables from the switch
going either to the wan port of LiMe routers [if they have one] or to
their Lan port [if it's the only one they have], I should connect the
ISP router directly to the wan port of a LiMe router that has both,
such as a 1043 or a C7, and then connecting all other nodes to that
device's Lan ports, or, should they not suffice, draw a cable from
that
router's LAN port to the switch, and then connect all other devices
to
the switch, is this correct?
So, from my point of view, best possible scenario is for all libremesh
routers to be connected via cable through the LAN sockets.
If they are too far to reach via a cable (+100m) i would use Wifi.
This way, you say, only the first LiMe router receives
the external
DHCP. But still there are multiple advertisements.
Not in the same network.
You have one DHCP in the outside network between the ISP Gateway and
the first LibreMesh router, and you have a cloud of LibreMesh DHCP
routers in the other network.
Is this not a
problem any more since they are all the same, is this your point?
Yes
But still, how can all LiMe routers on that wired network have
the 10.13.0.1 IP at that point though?
That is a 'trick' of the LibreMesh Routers... they announce the same
Gateway IP, that is a local IP of each router, to allow Roaming devices
between Access Points.