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
On 08/05/2017 11:23 PM, Patricio Gibbs wrote:
> On 08/04/2017 07:47 PM, Ilario Gelmetti wrote:
>> On 08/05/2017 01:41 AM, Patrick Patricio Gibbs wrote:
>>> Two scenarios in which we want to control access based on set
>>> schedules. Ideally this would be configured in the luci GUI.
>>>
>>> A) Router WiFi Schedule
>>> Faby has a router with LibreMesh in her house, and she wants the WiFi
>>> to turn on every day at 2pm and turn off at 6pm. This could be
>>> achieved a number if ways:
>>> - the WiFi radios are enabled only during the desired hours.
>>
>> To switch on and off the radio sounds the easiest way to me.
>> Just adding to cron a line to switch it off using "wifi off radio0"
>> (also a line for radio1 also if the router is also 5 GHz) at 6pm and
>> another line to switch it on again with "wifi radio0" at 2pm should be
>> enough. And if you unexpectedly need the AP to be on out of allowed
>> hours you just reboot the router (unplug and plug) and the AP will be
>> active again.
>
> Any chance of getting a GUI version of this that persists between reboots?
Err, this would be something to implement on LEDE/OpenWrt side, in my
opinion.
You can find many related links on this page:
https://forum.lede-project.org/t/scheduling-on-off-wifi/3385
For example there's a luci-app-wifischedule package you can install on
LibreMesh and try :)
Let us know!
Ilario
Hi,
I have 4 Community Chaos LiMe nodes in a layer 2 LiMe network:
A.- Connected to an ISP router and to B.
B.- Connected to A, C and D.
C.- Connected to B and D.
D.- Connected to B and C.
A-B link is wired.
C-D link is wired.
Rest of links are wireless.
A and B work fine and they reach the Internet.
C and D work fine, they can reach any host of any node in the LAN, but
they cannot reach the Internet (ping 8.8.8.8).
Any basic troubleshooting tool/advice is welcome.
Thank you
Hi,
I am contacting the lime community to organize a visit to some of us
members.
In order to promote this open source mesh technology. I would like to
interview admin & users of working LiMe networks. Filming and recording
to share all experiences and show howtos.
Final documentary goal is to show mesh as a popular alternative to 5G
coming on.
I am located in France, Toulouse or Morvan in Bourgogne.
I am planning to organise road in an equiped van in october 2017.
Please contact me if you are interested to receive my visit ;)
1MESH
1LOVE
Fred
Thinking about how we might use the voucher system for access control in
Caimito and other communities in the area...
1) I imagine the process might be that someone connects to the wifi,
opens a browser (or on Android, sees a notification to register on the
network, like in airports), gets caught by the captive portal, and has
an option to use the network without registering, or enter a voucher
code. Correct? Other options?
2) In order to make the voucher code as easy as possible to use, three
options occur to me:
-- 1) the code is 2 or 3 letters (maybe up to 6), case insensitive,
automatically generated by the system. (My favorite)
-- 2) the code is a word or pair of words, automatically generated by
the system. (My least favorite)
-- 3) the code is defined by administrator, and checked by the system to
avoid duplicate codes. (Maybe useful in some cases)
Letters instead of numbers because we get more options for each digit,
thus making a shorter code.
number of letters - unique codes:
1 - 26
2 - 676
3 - 17,576
4 - 456,976
5 - 11,881,376
6 - 308,915,776
Airlines tend to use 6 letters, and I can usually remember those codes.
With 2 letters, we could give unique codes to everyone who comes through
Caimito in a year, and with 4 letters we could cover 87% the province,
and with 6 we could give 19 codes to each person in Ecuador. I imagine
most community networks would be fine with 3 or 4 letters. Maybe the
length of the code can be defined by admin, or it can grow sequentially
as needed (first code is A, 27th code is AA, 677th code is AAA, so on).
3) Codes expire and get recycled, yes?
4) The vouchers are part of Pitbull, or separate-but-connected?
5) Probably "it'll be ready when it's ready, no later than October",
but... Any idea when a functional build might be ready? There are a
number of things that seem not feasible until this system works (e.g.
community library / internet cafe).
6) Can we define roles or profiles in Pitbull / the voucher admin
system? This way I can look at a list of currently active vouchers, and
see who's connected, how much time they have left, and whether they're a
library/network member, library visitor, tourist, or other. When I
create a tourist voucher, they get access to 50% of the available
bandwidth, and by default the voucher lasts 1 day. A library visitor by
default gets 90% access and lasts 1 hour. A member by default gets 100%
of bandwidth and 1 month.
7) When a voucher expires, keep the code reserved in the system for 10%
of the time it was valid, in case the person wants to renew the voucher.
Examples:
-- A 1 hour voucher of a library/ciber visitor expires, and they have a
6-minute grace period to request another hour on their voucher. The
admin interface makes extending the voucher easy.
-- A 1 month voucher has a 3-day grace period. The device doesn't have
access once the voucher expires, but renewing is easy: the admin doesn't
have to create a new voucher, and the person doesn't have to enter a new
code.
If there's a better place to share these ideas, please tell me.
~ Pato
Hi Everyone,
The last LibreMesh release (I don't remember if it was announced or
not, but it is here :) ) brings support for 11s and many other things.
I was wondering... now that the wdr3500/3600/4300 devices are no longer
accessible... which ones can we use?
Now there are a lot of devices with the MTK7601, and others with
QCA6174.
I've tried some Xiaomi device that comes with the MTK7601
processor+radios and it works... but don't have knowledge about
performance and robustness... and if there are any dual radio with
weather enclosure around.
Thanks!
Two scenarios in which we want to control access based on set schedules. Ideally this would be configured in the luci GUI.
A) Router WiFi Schedule
Faby has a router with LibreMesh in her house, and she wants the WiFi to turn on every day at 2pm and turn off at 6pm. This could be achieved a number if ways:
- the password changes to something known by local users or is turned off during those hours.
- the network/SSID that's used by neighbors is enabled only during those hours.
- the WiFi radios are enabled only during the desired hours.
- something involving traffic queues?
- something else?
B) Device access schedule
This would be a feature of the voucher system that controls access to the Internet.
Scenario: Lili was spending three hours on Facebook messenger every afternoon and it was distracting her from homework, chores,and participating in social life with family and friends. Her mom Maria wants to take her phone away, but instead they reach an agreement enabled by LibreMesh voucher configuration. LibreMesh will only give Lili's phone access to the Internet from 3-4pm every weekday. This way her friends and family know that after 4pm, they can expect her at home or otherwise available.
Do these seem viable to implement? Soon? Any suggested workarounds until then?
~ Pato
Hi there,
I am having some problems related to DNS. Clients of some nodes can
reach the Internet but cannot resolve names.
I do not know how DNS work in LibreMesh.
If I check the DNS settings of a client I see the anygw address as the
DNS server.
How does name resolution of Internet hosts work in LibreMesh? I mean
when the LiMe network has access to the Internet.
If there is a router sharing their Internet connection with a LiMe
network and it changes the configuration of its DNS servers,
will the LibreMesh network be affected by that change?
How?
Will the problem be automatically solved after some time?
Do I need to manually restart any service?
Thank you.
