I saw that it depends on libpcap, it is the only way to listen for icmp
messages?
In this case i think it is not the case to use icmp protocol and instad would
be simpler and more performant just a simple udp multicast socket like bmx6 do
I have talked today with antonio (ordex) and really what they call backbon is
not the common sense of backbone, so we should add a vlan on top of ethernet
interfaces where client are accepted too if we want batman-adv to route traffic
accross ethernet too
Is p4u receiving mail from the mailing list or there is some problem ?
---------- Forwarded Message ----------
Subject: News in libremesh
Date: Wednesday 15 May 2013, 00:06:01
From: Pau <hakais(a)gmail.com>
To: NicoEchániz <nicoechaniz(a)altermundi.net>, Gioacchino Mazzurco
<gio(a)eigenlab.org>, Gui Iribarren <gui(a)altermundi.net>
Hi.
We are currently using the the repositories created in github. I see
Gio added the package for cracking the ath9k regdomain.
I added a dummy package named lime-system with some basic dependences.
If you clone the repository lime-build and type "make T=tl-703n J=2",
it should compile the system with the lime-system enabled and the
dependences.
For the moment only the targets tl-703n and tl-wdr4300 are supported,
but it is just a mather of adding the config files in the
configs/directory
To create them execute
- make T=NEW_TARGET menuconfig
- find the resulting config file in build/configs/NEW_TARGET
- diffconfig it with build/ar71xx/scripts/diffconfig (yes, it should
be added to the Makefile to do it automatically, please volunteeers!!)
- save it to configs/NEW_TARGET
Following this approach we can have kind of useful diferent profiles
for each target. So, some software can fit in devices such as wdr4300
and not in 703n.
I also have been thinking about the network architecture modes (NAM).
I think we should implement some of them and let the administrator
choose (can be different for each community).
- bmx6 + bat-adv in all nodes
- bat-adv in all nodes and bmx6 in the borders (autoloaded)
- bat-adv in all nodes and bmx6 only in the nodes designed by the
administrator
[1] https://github.com/libre-mesh
PS: Do we have mailing list?
--
./p4u
-----------------------------------------
Amici,
I converted Pau's Roadmap wiki entry into individual issues, so we can
have more complete information on each task: what is expected, who will
be in charge, etc.
I marked all issues with lime-alpha as target version just to have them
grouped.
It's here:
http://dev.libre-mesh.org/projects/libre-mesh/issues
And I updated the link in the wiki to point there. If we are all ok, we
can delete the Roadmap wiki page and keep using the issue system for
future tasks.
Cheers!
Nico
