Welcome Jason!!
My answer in line:
On 5/16/21 1:12 PM, Jason Gauthier wrote:
>> With
LibreMesh is it possible to continue using my own router?
I have a
>> Cisco ASA that I am somewhat partial to
and I don't want to stop
using
> it.
>> I couldn't find anything (obvious) in the docs on how if this
scenario
>> was
>>> possible.
Sorry for that, the documentation is a fragmented in various places...
Every contribution is most welcomed!
Thanks for
your repsonse. I don't want my ASA to be part of the mesh
network, just act as my edge router. If I can do that, I'll give
libremesh
a try, for sure.
My ASA is already my DHCP
server, so if I can disable it with libremesh
it should work. My desired setup is as simple as you made it sound,
except I want 2-3 libremesh devices. I'll try it out and see. Off to
research good, but affordable, compatible routers. Thanks!
This can be achieved compiling LibreMesh *without* selecting the
"lime-proto-anygw" package (but I never tested this scenario).
Then, you should connect a LAN port of your router with a LAN port of a
LibreMesh node (very bad idea unless lime-proto-anygw is deselected!!).
I can see only two small problems with this:
* The nodes will have an IPv4 which is likely not in the subnet your
router is advertising (this can be configured in the LibreMesh nodes in
/etc/config/lime-node following the documentation on
/docs/lime-example.txt
https://github.com/libremesh/lime-packages/blob/master/packages/lime-docs/f…
and the configuration is applied running lime-apply). The clients will
have no problem to reach the internet and to reach the other nodes but
it will be inconvenient to connect to the mesh nodes for maintenance.
* In the lime-proto-anygw there's a parameter that I suppose should be
useful also in your scenario: the LibreMesh DHCP suggests to the clients
to use a small MTU (I suppose that the reason is to decrease
fragmentation inside the mesh). This should be possible to achieve also
decreasing the MTU for the AP interface. If you ignore this, everything
should work anyway, but maaaaybe with a bit worse performances, I
suppose. That MTU setting appeared in LibreMesh in 2014, set by G10h4ck
and I'm not sure that 1350 is still an optimal choice with the current
set of routing protocols:
https://github.com/libremesh/lime-packages/commit/c028a28b1defdab5163af822e…
Ciao!
Ilario
--
Ilario
iochesonome(a)gmail.com
ilario(a)sindominio.net