I'm using self-cooked version of latest development LiMe, and I run across
quite baffling problem. Routing through AP works fine, I can access
internet normally and everything works - HOWEVER, if I log in to router and
try accessing internet from router shell, using ssh/wget/opkg/whatever -
nope, nothing works. Even ping does not work, although if I use workstation
connected to AP and ping from there, without loggin into router, everything
works as expected.
What am I missing here?
Harri
Hi there,
thanks for libremesh! My goal is to add another client wifi network. The
two from the 'standard' configuration are running and the mesh on 5 ghz
also, but if i try to add a third one, running lime-config gives me an
error.
In my etc/config/lime besides the other config options:
config wifi 'radio1'
list modes 'ieee80211s'
option htmode_5ghz 'HT40'
option ieee80211s_encryption 'psk2/aes'
option ieee80211s_key 'password'
option ieee80211s_mesh_id 'LiMe'
option ieee80211s_mesh_fwding '0'
option channel_5ghz '48'
option distance '100'
config wifi 'radio0'
list modes 'ap'
list modes 'apname'
option apname_ssid 'LibreMesh.org/%H'
option apname_key 'mypassword'
option apname_encryption 'psk2'
option ap_ssid 'IoT'
option ap_key 'mypassword'
option ap_encryption 'psk2'
option channel_2ghz '1'
option distance '100'
That is working. If i add another block in radio0 like this:
list modes 'ap2name'
option ap_ssid 'thirdSSID'
option ap_key 'mypassword'
option ap_encryption 'psk2'
I'am getting an error on the command line:
/usr/lib/lua/lime/wireless.lua:117: module 'lime.mode.ap2name' not
found: ...
Does some of you has an example of adding more SSID's via the
"lime-config-system" for me?
Regards
Julius
I see DSL modem-router combo devices on OpenWrt... Any experience using them with LibreMesh? Are all the necessary config options accessible, either though GUI or CLI?
The public ISP here has just informed is that after all it may be impossible for them to sell us a fiber optic connection in the town we have line of sight to, so we're looking for ways to improve our DSL quickly whole we figure out our longer-term strategy.
~ Pato
Has anyone modified a router that had non-removable antennas to add an
attachment for a removable antenna?
I imagine it would require:
- acquire male RP-SMA connector.
- open the router, cut a hole somewhere in the casing, and mount the
male RP-SMA connector there.
- disconnect the wire of a stock antenna and put a wire from that part
of the board to the RP-SMA male.
- close the router.
Doing this, the router keeps its stock antenna(s), but one of them is
disconnected.
I guess there's a question about how much power the radio puts out, to
know what sort of antenna will work... I don't yet know much about those
calculations.
~ P
Anyone have experience with LB-Link routers? I haven't found info about
what chipset they have, but here in Ecuador there are various models for
sale, and none are in WikiDevi or OpenWrt ToH:
ROUTER LB-LINK 150MBPS WR1100 1 ANTENA $21.21 incluido iva
ROUTER WR2000 300MBPS 2.4GHZ 2 ANTENAS $26.70 INCLUIDO IVA
ROUTER 4 ANTENAS BL-W1210M DUAL BAND 2.4 / 5 GHZ 1200 MBPS 10/100/1000
$91.11 INCLUIDO IVA
~ Pato
hello
This list a bit quiet, so here is a question for the experts: how difficult
it is to port libremesh to the wrt54g? I see there is a openwrt version,
but no libremesh. The chipset is not in the target list.
Boa Vista de Acará network, near Belem in northern Brazil, got 10 of these
routers from FreiFunk. I understand they used to run Tomato firmware in
them.
Thanks!
Bruno
--
bruno(a)pobox.com ▀─█▄██▄▀▄
http://brunovianna.net ─█▄██▄▀█▀█▄
skype: randomico▀─█▄██▄▀█▀█▄▌██─█▌█▌
Hello World!
My name is Hiure, I am a member of coolab ( coolab.org). This is the
first time I write to this list , I am a beginner on administrate
networks and configure equipments.
By initiative from COOLAB we are starting a few community networks
around Brazil. One of them is where I live , in a rural community in
the city of Monteiro Lobato, State of São Paulo. Here we start since the
creation of a association to formalize the communitary network and
create a model to guide on the other COOLAB installations.
We arre using the last version of libremesh , cooking it in the cooker.
As we still in a test phase we have only six nodes , the gateway is a
tplink wdr3500. With a captive portal, we are running this adapt version
to nodogsplash (http://wiki.coolab.org/index.). This system is
fundamental to keep the network sustainable, without it we can not
finance the connection and technical support for the network.
The problem is, in the last months some people found a way to hack this
system. What I understood so far: There is a cellphone app that create
tunnels for diferent ports and instead of swap packages DNS it tunell
all the packages by there. I know just a few things about how firewall,
iptables, ebtables, etc, i have been studying it in the last months ,
but it seens much more complicated because it look that in libremesh,
with so many interfaces, its get hard to understand and to execute a
rule that can solve this problem.
If someone can help me with some tips on t do it , or sending some
material where I can study to understand better this questions, it
would be great
bests
Hiure
Hi all!
We are just around the corner on having the LibreRouter with us!
In order to prepare for the imminent arrival, we prepared a report to
have you informed on how it will be and how you will be able to use it.
https://librerouter.org/media/librerouter-datasheet.pdf
We have also prepared a video to explain you how you can use it in your
communities: http://gg.gg/LR-video
Last but not least, we also want to ask you a few questions about how
you plan to use them in your communities. Please help us collect this
information, that will enable us to prepare for the public release of
the LibreRouter: http://gg.gg/LibreRouter-whowantsone
This same article can be found here: http://gg.gg/LR-whowantsone-article
Have I told you that is Open Source Software and Hardware?
You can check out the source at: http://github.com/libremesh/librerouter
That is all for now.
Don't hesitate on reaching out on any question that you might ask.
Regards,
--
Nicolás Pace
AlterMundi.net
We now have a space on TranslateWiki.net to translate various parts of
the LibreMesh project!!! Please share this invitation with anyone you
know who might want to translate.
You do not need to know how to program. If you are familiar with wiki
software, you will learn quickly how to use translatewiki.net. The only
requirements are a good command of languages, a web browser and an open
mind.
*How to start*
1. Get an account -- https://translatewiki.net/ -- and set up your profile.
2. Do the test translations that it asks you to do, in order to verify
that you know both languages and earn the translator permission.
3. Go to https://translatewiki.net/wiki/Translating:LibreMesh and click
on "Translate this project" (in your chosen language) at the top of the
page.
Any questions, reply here.
More details below, including the option of offline translation and how
to see multiple languages when translating.
Currently only software interface strings are translatable, but soon
we'll add other parts of the LibreMesh project to translate.
onward with translations!!
~ Pato
(Most of this email is copied and modified from various pages on
TranslateWiki.net.)
*MORE DETAILS*
To get started, the first thing you need is a user account on
translatewiki.net. Creating an account is done in less than a minute and
is used to keep track of what you have worked on. It will give you
access to translate any of the projects on TranslateWiki.
When creating an account you go through some test translations to make
sure that you have a basic understanding of the languages. These
translations are not live but are instead compared to older translations
by trusted users before giving you the rights to start translating live
messages. That means that the messages you translate will be used in the
next update of the program/website!
*Start translating*
After you have been given permission to translate, your entry point is
most likely going to be the translation tool. It lists all the available
groups of messages that we have. Most of the translations happen using
this tool, see the tutorial,
https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Extension:Translate/…
For more info about how to use TranslateWiki.net:
https://translatewiki.net/wiki/Translating:Introhttps://translatewiki.net/wiki/FAQhttps://translatewiki.net/wiki/Project:About
*Offline translating*
https://translatewiki.net/wiki/Translating:Offline
*How to view translations of a message into other languages*
If you are a translator you can choose to display messages on the edit
screen in other languages, as well as English and your own language.
These assistant languages are set in the 'Edit' tab of 'My preferences'.
Anybody can see all the translations of a message by clicking on 'In
other languages' in the navigation bar when viewing a message in any
language. This takes you to the special page All translations.
For example, if you speak Brasilian Portuguese, Spanish, and English,
then you can set up "assistant languages" so that you see both English
and Spanish translations as you translate into Brasilian Portuguese.
*If your language isn't available*
https://translatewiki.net/wiki/Translatewiki.net_languages
*Improving the English source message*
If you spot a spelling or grammar error in the original English message,
or you would like to suggest a better way of expressing the message,
then please do not change the English message but instead put a message
on the talk page of the project concerned (or submit a pull request on
GitHub). You should explain why you think there is a problem with the
current message and propose your alternative. The proposed change will
then be discussed in the usual way and, if agreed, then one of the
developers at the project concerned will change the message in the
source code (kept, for instance, on sourceforge.net, or wherever...) on
that project. A bot run by translatewiki.net will then detect the change
in the source code and import the new message to translatewiki.net. The
amended message is usually brought to the attention of translators by
placing the !!FUZZY!! mark in existing translations (it is all
automatic; the FUZZY mark is also added by the bot detecting the change).
Why can't one edit English-language messages on here? Because changing a
message in English may impact all translations. Software developers own
the source strings. If you want to propose that a message is changed,
please use the button "Ask question" in the translation editor and write
your proposal or concern.
Continuing the conversation from
https://github.com/libremesh/lime-packages/issues/257#issuecomment-365522564
, including @Nikerabbit, part of the TranslateWiki team:
@Nikerabbit wrote:
> Translate extension supports translating wiki pages (any kind of pain
text is okay), so you could copy the markdown readme on the wiki and
make it translatable using that feature. Practically, that would mean
that future changes should be done to the translatable page and exported
back to the repository (or doing changes twice, but overwriting the wiki
version with a fresh copy from the repository won't work).
>
> We have one project using that approach:
https://translatewiki.net/wiki/Translating:Lib.reviews/FAQ
> One significant issue here is though that exports from translatable
pages to the repository are not automated yet.
Within LibreMesh, I see four types of text to translate (besides
software interfaces):
- web sites
- software README files
- instructional booklets
- subtitles
# WEB SITES
The web pages of www.libremesh.org are here:
https://github.com/libremesh/lime-web/tree/master/docs . We talked about
changing from Jekyll to a website engine that has more elegant
multilanguage functionality (such as Nikola
http://nikola.readthedocs.io/en/latest/manual/#multilingual-posts), but
for now we're still on Jekyll. Our conversation about this is at
https://github.com/libremesh/lime-web/issues/22 . There are two
language-specific issues open for the website:
https://github.com/libremesh/lime-web/issues/35 Italian and
https://github.com/libremesh/lime-web/issues/33 Brasilian Portuguese.
One group used Zanata to translate a few pages.
I'm tempted to move libremesh.org to a platform that allows translation
of the site content on the site, so that all translation can happen
on-site instead of pasting it into TranslateWiki, translating, and
copying the translation back to the website (or back to a file on GitHub).
The www.librerouter.org website runs CyclopeCMS, which has [kind of
awkward, admin-dependent] multilingual capabilities, however the site
will be moved to WordPress, which has various multilingual options. We
welcome and recommendations of WordPress multilingual and translation tools.
# README FILES
For some software, we want to translate the README but not the software,
mostly for command line programs. These include:
- lime-sdk https://github.com/libremesh/lime-sdk/blob/develop/README.md
- LibreNet6 http://docs.altermundi.net/LibreNet6/Setup
I imagine this is the same workflow as for text pages: paste into TW,
translate, copy to the appropriate place in a file or web page.
# INSTRUCTIONAL BOOKLETS
The booklets aren't published yet, but we've already translated some of
the drafts by using online pads (EtherPad) and offline OmegaT+. The
booklet formats and workflow can be changed if necessary. Currently, the
translation happens with TXT files, with a PDF of the original (in
Spanish) to give visual context (there are images in the booklets). The
booklet creators then paste the translated text and publish a PDF in the
target language. There are no plans at the moment to publish the
booklets as web pages, though this is a possibility, and might be a good
idea.
# SUBTITLES
There are instructional videos that will be narrated in Spanish or
English, and then we'll create subtitle files, and then translate the
subtitles. In the past I've used SubtitleEditor on my computer, and
www.dotsub.com. If we can put the SRT or other format in a GitHub repo
and translate them on TranslateWiki, great.
~ Pato