Hi all!
I was preparing some pre-configured images for NinuxVerona [1,2] and
following the italian guide for compiling Libre-Mesh [3].
When I reached the point about menuconfig I got a doubt:
why should I deselect all those modules?
Could you explain me if it's always a good idea to deselect
* Base system/dnsmasq
* Base system/firewall
* Network/odhcpd
and if it's not, in which cases should I keep these?
Should I select some LiMe package to replace their functions?
For example I noticed lime-eb-ip-tables [4] which I guess is needed for
having masquerading even deselecting Base system/firewall?
Thanks,
Ilario
[1] https://github.com/VeronaWirelessCommunity/lime-packages
[2] http://verona.ninux.org/
[3] http://wiki.ninux.org/Libre-Mesh#Compilare
[4]
https://github.com/libre-mesh/lime-packages/blob/develop/packages/lime-eb-i…
--
Ilario Gelmetti
iochesonome(a)gmail.com
igelmetti(a)iciq.es
ilario.gelmetti(a)estudiants.urv.cat
Hi!
>From barcelona I am connecting to multiple librenet6 nodes and getting routes
from them but there is not 0::0/0 nor 2000::0/3 something happening to chato ?
Cheers!
running lime-config get follung error and faulst in config files (%M %N
parameters not set)
###
Chaos-calmer 15.05
LiMe 15.04 BigBang (15.04 rev.a1b8263 20150814_2143)
lime-config
Clearing wireless config...
Clearing network config...
Disabling odhcpd
sh: /etc/init.d/odhcpd: not found
Cleaning dnsmasq
Disabling 6relayd...
/usr/lib/lua/lime/network.lua:35: attempt to call field 'Hex' (a nil value)
stack traceback:
/usr/lib/lua/lime/network.lua:155: in function 'Hex'
/usr/lib/lua/lime/network.lua:35: in function 'generate_host'
/usr/lib/lua/lime/network.lua:65: in function 'primary_address'
/usr/lib/lua/lime/proto/lan.lua:9: in function 'configure'
/usr/lib/lua/lime/network.lua:154: in function
</usr/lib/lua/lime/networ k.lua:154>
[C]: in function 'xpcall'
/usr/lib/lua/lime/network.lua:154: in function
</usr/lib/lua/lime/networ k.lua:143>
[C]: in function 'xpcall'
/usr/bin/lime-config:48: in function 'main'
/usr/bin/lime-config:54: in main chunk
[C]: ?
Configuring system...
Let uhttpd listen on IPv4/IPv6
##
can somebody help me out where to look or what im missing perhaps
tnx
3zl
Hi!
I have just read
"as well as some Ubiquiti 5ghz bridges, connected by ethernet pigtails to the
TP-Link’s switch. All of the routing is done by Libre-Mesh running on the TP-
Links: The Ubiquitis are dumb wireless bridges."
http://blog.altermundi.net/article/libre-meshing-paravachasca-valley/
Are you using lime-hwd-ground-routing? I ask because it is done for this type
of things.
Cheers!
Hi, i (and some other lime enthusiasts i know) would like to have a
custom ssid in addition to the ap_ssid,
in some cases we want this additional wifi network protected (wpa2)
and/or on a separate subnet (not briged to bat0).
I would like to implement this in lime-system, do you agree or is it
better in a separate module? Do you have any advice?
Hi i would like to contribute to the documentation, i registered a
account (leonaard) but i am not able to login.
Can you activate my account and enable it to edit the lime firmware wiki?
thanks
lime
# option bmx6_over_batman false
# Disables Bmx6 meshing on top of batman
# option main_ipv4_address '192.0.2.0/24'
# Parametrizable with %Mn, %Nn
# option main_ipv6_address '2001:db8::%M5:%M6/64'
# Parametrizable with %Mn, %Nn
# list protocols adhoc
# List of protocols configured by LiMe
# list protocols lan
# list protocols anygw
# list protocols batadv:%N1
# Parametrizable with %Nn
# list protocols bmx6:13
# list resolvers 8.8.8.8
# DNS servers node will use
# list resolvers 2001:4860:4860::8844
### WiFi general options
#config lime wifi
# option channel_2ghz '11'
# option channel_5ghz '48'
# list modes 'ap'
# list modes 'adhoc'
# option ap_ssid 'LiMe'
# option adhoc_ssid 'libre-mesh'
# Parametrizable with %M, %H
# option adhoc_bssid 'ca:fe:00:c0:ff:ee'
# option adhoc_mcast_rate_2ghz '24000'
# option adhoc_mcast_rate_5ghz '6000'
# option mesh_mesh_fwding '0'
# option mesh_mesh_id 'LiMe'
### WiFi interface specific options ( override general option )
#config wifi radio11
# list modes 'adhoc'
# option channel_2ghz '1'
# option channel_5ghz '48'
# option adhoc_mcast_rate '6000'
# option adhoc_ssid 'libre-mesh'
# option adhoc_bssid 'ca:fe:00:c0:ff:ee'
#config wifi radio12
# list modes 'manual'
# If you use manual protocol you must not specify other protocol, or
your
configuration will be broken!
### Network interface specific options ( override general option )
### Available protocols: bmx6, batadv, wan, lan, manual
### proto:vlan_number works too ( something like bmx6:13 is supported )
### If you use manual do not specify other protocols, may result in an
unpredictable behavior/configuration (likely you loose connection to the
node)
#config net port5
# option linux_name 'eth1.5'
# list protocols 'manual'
### Ground routing specific sections
### One section for each ground routing link
#config hwd_gr link1
# option net_dev 'eth0'
#
Plain ethernet device on top of which 802.1q vlan will be constructed
# option vlan '5'
#
Vlan id to use for this ground routing link, use little one because
cheap
switch doesn't supports big ids, this will bi used also as 802.1q vid
# option switch_dev 'switch0'
#
If your ethernet device is connected to a switch chip you must specify
it
# option switch_cpu_port '0'
#
Refer to switch port map of your device on openwrt wiki to know CPU port
index
# list switch_ports '4'
####################
lime-defaults
# Beware this file is NOT supposed to be edited by the end user, modify
/etc/config/lime instead
# If the same configuration is contained in both /etc/config/lime and
lime-defaults file, the former will prevail
# Beware this file is not supposed to store specific configuration, like
"config net eth0"
config lime system
option hostname 'LiMeNode-%M4%M5%M6'
config lime network
option primary_interface eth0
option main_ipv4_address '192.0.2.0/24'
option main_ipv6_address '2001:db8::%M5:%M6/64'
list protocols adhoc
list protocols lan
list protocols anygw
list protocols batadv:%N1
list protocols bmx6:13
list resolvers 8.8.8.8
list resolvers 2001:4860:4860::8844
config lime wifi
option channel_2ghz '11'
option channel_5ghz '48'
list modes 'ap'
list modes 'adhoc'
option ap_ssid 'libre-mesh.org'
option adhoc_ssid '%H'
option adhoc_bssid 'ca:fe:00:c0:ff:ee'
option adhoc_mcast_rate_2ghz '24000'
option adhoc_mcast_rate_5ghz '6000'
option mesh_mesh_fwding '0'
option mesh_mesh_id 'LiMe'
#############
somthing worth to note :
%H and is not expanded in /config/wireless
/etc/config/network br-lan ip NOT set
##
hope somebody can help
#
sorry have to stay with CC-RC3 but didnt have any problems with luci/lua
until now
running build for AR71xx
greetings
Hi, i am willing to write an auto upgrading system for lime,
i saw the simple get->checksum->flash script from qmp [0] (thanks to
Ilario), but i am thinking of a more decentralized solution.
Something like:
* link to new release is annunced on the network (eg using alfred on
bat-adv networks)
* nodes share images via bittorrent
* each node checks the (pgp) image signature and flashes it
user can choose to trust the included signatures or to use its own pgp
trust chain
do you think this can be useful? comments?
[0]
http://dev.qmp.cat/projects/qmp/repository/revisions/master/entry/packages/…
Hi all!
During BattleMeshV8 we knew some community networks activists from
Greece, seems that there will be a talk about Libre-Mesh in the
"Athens Wireless Summit 2015" [1].
Due to the lack of documentation they had hard time trying to
understand/use LiMe.
Let's write some documentation, I think that Libre-Mesh is stable enough!!
(and, needless to say, the lack of documentation is damaging the project)
Ciao,
Ilario
[1] http://events.awmn.net/wp/?page_id=54&lang=en
---------- Forwarded message ----------
From: Joseph Bonicioli <nettraptor(a)awmn.net>
Date: 2015-08-06 22:12 GMT+02:00
Subject: [Battlemesh] Athens Wireless Summit 2015 - Call for
Participation / Talks
Athens Wireless Summit 2015
Call for Participation / Talks
Dear All,
If you are involved in a community network, if you have deployed
wireless or fiber technology for a community network, if you love the
commons, if you are from the academia running a wireless or community
related testbed, then this call is for you! We are pleased to
announce that Athens Wireless Metropolitan Network (AWMN) is
organizing a two day event titled «Athens Wireless Summit 2015». It
will take place during the weekend of the 19th and 20th of September
2015 at Impact Hub Athens Greece. It would be our pleasure to have you
there and we encourage you to participate with a talk or a workshop or
both.
What is it?
The Athens Wireless Summit 2015 is a two day event which aims to bring
people together, from the academia, the world of commons, open source
and wireless networks communities and all those involved or interested
in wireless network technologies, in order to meet with each other,
exchange views and experiences, explore possibilities for cooperation
and synergies and to promote the benefits of developing modern
telecommunication infrastructure as an enhancement factor for a
region.
We aspire to include presentations, discussions, workshops, social
events and exhibitions of wireless network technologies, the
development of network infrastructure and shared services, the
promotion of the social character on developing community networks by
citizens for citizens as well as developing networks of active people
around these; with examples like the cooperation structures that exist
or can be developed between these communities in Greece and abroad.
Where and When
The event will take place on Saturday the 19th and Sunday the 20th of
September 2015 at Impact Hub, Karaiskaki 28 in Athens. The entire
building of Impact Hub will be available for the two day event. This
gives us the opportunity to schedule both seminars and workshops in
parallel flows. For more information about Impact Hub, please visit
their site at: http://athens.impacthub.net
Format and content of the talks
We aspire to keep a balance between community networks, academia,
everyday real community applications and related technology subjects.
Subjects may be anything related to community networks ranging from
applications, wireless technology, mesh protocols, testbeds, other
routing protocols, social related subjects, IoT, related research
subjects and anything that will make those two days productive, fun
and beneficial to all. Related Talks or Workshops will be grouped
together and be placed on the schedule in order to have cohesion of
subjects and help participants choose their tracks. Finally we welcome
proposals of anything you think may be of interest to community
network enthusiasts. The format can be of any kind, for example a
presentation, talk, discussion, debate, practical workshop, or film
screening. The suggested duration for talks is 20 minutes where
workshops can be arranged to take anything up to 1 hour depending on
slot and space availability.
Lightening talks
Lightening talks are shorter talks which can be submitted after the
main workshops/talks deadline, to give everybody the opportunity to
present their project/idea. Each lightening talk will be 7 minutes
long, followed by 3 minutes of questions. Projector slides can be
submitted in EPS or PDF format to: aws-submissions(a)awmn.net
Proposed Draft of the Program
Presentations / Talks
Time
Saturday the 19th
Open Space - 1st Floor
Sunday the 20th
Open Space - 1st Floor
09:30 - 10:30
Arrival / Registrations / Coffee
Arrival / Registrations / Coffee
10:30 - 10:45
Welcome / Objectives of the day
Welcome / Objectives of the day
10:45 - 11:00
The schedule of the day (speakers, workshops, panels)
The schedule of the day (speakers, workshops, panels)
11:00 - 11:20
… (1st Presentation)
… (1st Presentation)
11:20 - 11:40
… (2nd Presentation)
… (2nd Presentation)
11:40 - 12:00
… (3rd Presentation)
… (3rd Presentation)
12:00 - 12:30
Discussion Panel (Subject?)
Discussion Panel (Subject?)
12:30 - 13:00
Coffee Break
Coffee Break
13:00 - 13:20
… (4th Presentation)
… (4th Presentation)
13:20 - 13:40
… (5th Presentation)
… (5th Presentation)
13:40 - 14:00
… (6th Presentation)
… (6th Presentation)
14:00 - 15:00
Break for Light Lunch
Break for Light Lunch
15:00 - 15:20
… (7th Presentation)
… (7th Presentation)
15:20 - 15:40
… (8th Presentation)
… (8th Presentation)
15:40 - 16:00
… (9th Presentation)
… (9th Presentation)
16:00 - 16:30
Discussion Panel (Subject?)
Discussion Panel (Subject?)
16:30 - 17:00
Coffee Break
Coffee Break
17:00 - 17:20
… (10th Presentation)
… (10th Presentation)
17:20 - 17:40
… (11th Presentation)
… (11th Presentation)
17:40 - 18:00
… (12th Presentation)
… (12th Presentation)
18:00 - 18:30
Discussion Panel (Subject?)
Conclusions - End of Day 1
Discussion Panel (Subject?)
Conclusions - End of Event
18:30 - till late
Social networking / Party
Social networking / Party
Suggested Workshops/ideas
WORKSHOPS
Time
Saturday the 19th
Open Space - Ground Floorr
Sunday the 20th
Open Space - GroundFloor
?
Wireless Node, Installation & Configuration
ΙοΤ applications
?
Operating Systems & their customization
Optical Links
?
Off the grid applications
Applications on Community Networks
?
Confine Platform
Research Infrastructures
?
..
..
EXHIBITIONS
Room
White Room
Photo Galleries of Wireless Community Network (CWN) Node facilities
throughout Greece/Europe/The world
...
Exhibition with Wireless Network Equipment used by CWNs
Your Exhibition!
Submissions
To allow an efficient handling of your proposal, please submit your
proposal utilizing this google form (http://goo.gl/forms/0GccRp8SaZ).
If you do not like Google forms, please provide the following
information and send them by email to the address below:
Your name
What format will it take (talk/workshop/panel discussion/lightening talk/…)
Your topic headline
Your topic description which can be brief (does not need to exceed a
couple of lines) but should provide a reasonable summary of your talk
The dates of your stay at the event and (optional) preferred day for your slot
The duration of the slot if you wish to do a workshop (all other slots
will be limited to one hour)
Any requirements you need, for example, a projector.
The email address you need to send the above info to is aws-submissions(a)awmn.net
Come and Join us!!!
We are convinced that your participation in the event will contribute
significantly to the agenda framework and the success of this event.
This event is a great opportunity to get together and share ideas
between people who have common interests on wireless community
networks and wireless networking technologies.
Should you have any questions, inquiries, comments along with
suggestions regarding the agenda, please feel free contact us using
the following mail address aws-organizers(a)awmn.net.
More info will be posted in the coming days and weeks on the event
site http://events.awmn.net. It is still under construction but it
will soon contain all the necessary info. We are looking forward to
your response and participation in this event.
Yours sincerely,
The organizing team of
Athens Wireless Summit 2015
_______________________________________________
Battlemesh mailing list
Battlemesh(a)ml.ninux.org
http://ml.ninux.org/mailman/listinfo/battlemesh
---------- Forwarded Message ----------
Subject: [Interop-dev] Battlemesh travel scholarships available
Date: Monday, June 22, 2015, 03:35:15 PM
From: Mitar <mitar(a)tnode.com>
To: interop-dev(a)lists.funkfeuer.at
Hi!
(Please spread the word to those you think might be interested in the
scholarship.)
We are opening a call for sponsored travel to attend Battlemesh for
anyone living outside Europe and would like to invite you to send your
application! Battlemesh is the annual conference/gathering/hack event on
community wireless networks and routing protocols will be between
3rd-9th August in Maribor, Slovenia. As Battlemesh is in the week before
the Chaos Communication Camp in Germany, this is an excellent
opportunity to be able to travel to both.
https://wlan-si.net/en/blog/2015/06/22/battlemesh-travel-scholarships-avail…
Event is free to attend and we still have organized accommodation
available at low cost.
Requirements
------------
Travel scholarships are open to people not living in Europe. To apply,
we would like to ask you to send a short video (not longer than two
minutes) to describe your situation:
- Where are you from?
- Why would you like to attend Battlemesh?
- What impact in your local environment do you expect from your
participation?
- Would you be able to attend without the travel scholarship?
- Will you continue to the Chaos Communication Camp? (Note that it is
not a problem if you also plan to go to the CC camp.)
Shoot a short video and upload it to one of the video sharing websites
and send us a link. Note that if it is private, we need a direct link
and/or password for it as well.
Contact
-------
E-mail your video to the local Battlemesh team at
<battlemeshv8(a)wlan-si.net>.
Deadline
--------
The deadline for applications is the 3rd of July. Decisions will be made
before 6th July.
What is Battlemesh?
-------------------
The Wireless Battle of the Mesh is an event that aims at bringing
together people from across Europe and beyond to test the performance of
different routing protocols for mesh networks, like Babel, B.A.T.M.A.N.,
BMX, IEEE 802.11s, OLSR. It is a tournament with a social character. If
you are a mesh networking enthusiast, community networking activist, or
have an interest in mesh networks and related technologies, come and attend.
The traditional goal of the event is to set-up hands-on testbed for each
available mesh routing protocol with a standard test procedure for the
different mesh networks. During the event, similar hardware and software
configuration will be used based on the OpenWrt and packages for each
protocol implementation. The event is also a great opportunity to
develop testing tools for PHY/MAC radio layers (drivers, scripts and PHY
analyzers). Alongside the testing of routing protocols, a number of
talks, workshops, and hackathons will be held on various mesh-related
topics, all from technology to community and social aspects of mesh
networks.
This years Battlemesh will take place from 3rd to 9th August 2015 in
Maribor, Slovenia.
Mitar
--
http://mitar.tnode.com/https://twitter.com/mitar_m
_______________________________________________
Interop-dev mailing list
Interop-dev(a)lists.funkfeuer.at
https://lists.funkfeuer.at/mailman/listinfo/interop-dev
-----------------------------------------
