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.
Hi,
I would like to know a bit about the routing protocol, specially when
there are several Internet gateways available. I was once told it makes
decisions mainly based on packet loss. That sounds good in order to find
the best way out to the Internet.
But, is there any kind of load-balance system so that every gateway is
used according to its capacity?
When having multiple Internet gateways, is it a normal scene to have
only one active in the whole network? Or it should normally use
different gateways at the same time?
Besides packet loss, what other criteria are taken into account to make
decisions?
Cheers!
Big antennas, small elements!
Em 1 de jul de 2017 9:10 PM, "Nicolás Echániz" <nicoechaniz(a)altermundi.net>
escreveu:
thanks foe the pics
if you can send an image of the antenna internals, we can see if it is a
known dual band model.
I'm thinking we can use ufl pigtails, like these :
https://www.data-alliance.net/u-fl-extension-cable-18-inch-
20-in-22-in-2ft-28-in-30-in-3ft-42-inch-u-fl-male-to-u-fl-female/
... to be able to use these antennas the way we use those provided with the
3500/3600 models.
On July 1, 2017 7:11:42 PM GMT-03:00, bruno vianna <bruno(a)pobox.com> wrote:
>
>
>
>>
>> Bruno, can you send pictures of this router without it's cover?
>> I'd like to see how the antennas are connected to the board.
>>
>> Also, do you know if the antennas are bi-band or the 2.4Ghz antenna is
>> inside the router like in other models?
>>
>>
>>
>
> Here they are. It looks like both antennas are connected to both chips
> (there is a track in the other side of the board connecting the antenna on
> the left to the MT7620 chip).
>
> Is there anyway I can test this?
>
>
>
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
Hi all,
my plan is to setup multiple LiMe routers in the house I live in to
connected me and my neighbors.
For testing I setup only two nodes and face the first problem: The
gateway router works just fine, resolving DNS requests. The "client"
router, connected via Ethernet to the gateway router routes all IP
traffic correctly but does not handle DNS requests at all.
I'm using a wdr4300 as gateway and a wr841 as client, using flavor
lime_default and lime_mini. The configuration is below.
config lime system
option hostname 'ZE-%M4%M5%M6'
option domain 'ze.lan'
option keep_on_upgrade 'libremesh base-files-essential
/etc/sysupgrade.conf'
config lime network
option primary_interface eth0
option main_ipv4_address '10.%N1.%N2.0/25'
option main_ipv6_address 'fc23:4237:3407:%N1%N2::/64'
option bmx6_mtu '1500'
list protocols lan
list protocols anygw
list protocols batadv:%N1
list protocols bmx6:13
list protocols olsr:14
list protocols olsr6:15
list protocols olsr2:16
list resolvers 8.8.8.8 # b.resolvers.Level3.net
list resolvers 141.1.1.1 # cns1.cw.net
option bmx6_over_batman false
option bmx6_pref_gw none
option bmx7_over_batman false
option anygw_mac "aa:aa:aa:%N1:%N2:aa"
config lime wifi
option channel_2ghz '11'
option channel_5ghz '48'
option htmode_5ghz 'HT40'
list modes 'ap'
option ap_ssid 'ze net'
option ap_key 'password'
option ap_encryption 'psk2'
Currently I'm not intending to use any Wifi Mesh functionality, only via
Ethernet, enabling roaming within the house.
Thanks for all comments!
Best,
Paul
Hi all
I’ve noticed LEDE supports 802.11r and 802.11w and has the respective settings section in LUCI under wireless security. I’m not familiar with these protocols other than knowing they exist and I’m very happy to see them available for use with free and open software. Is there any way we could start some testing for them for LiMe [especially the first one, which would make roaming inside the network even more seamless, since it’s one of the core advantages and of LiMe]? I read that 802.11r requires only one DHCP server to exist on the network and no separate subnets, but I assume that our replication of such a network with every node handing out the same leases on the same subnet perfectly simulates this behavior even in this respect, and the “trickery” works also for this requirement, is this correct?
Also, is there a good rule of thumb to figure out the right way of enabling features available in LuCi from the LiMe configuration in SDK? I’ve been trying to put all nodes on SSH port 42022 [I know, security by obscurity, but it’s better than nothing, and our keys are 4096, so there’s a solid base already ;] and disable password authentication for instance. Or adding hostnames, and so on. If there’s a quick way of figuring these things out, I won’t have to bother any of you for every single customization I need to make ;]
Thank you in advance
Nk
