I noticed about strange behaviors in the last binaries compiled for
14.08 branch. The packets to Internet were duplicated and things were
weird in general.
I found the problem, since the ebtables rules for preventing the anycast
IP propagation were put to the user.firewall directory, if the firewall
is not installed they are not executed. So, we have two solutions to
this problem:
1. Add the firewall as dependency for LiMe
2. Execute these rules (and others which may be needed) separately by
some lime process.
What do you think?
--
./p4u
Hi!
Pre 1: As a regular guifi.net speaker I know about how much important is
the map for empower the idea of community networks. In a speech people
understand community networks and the power they have in moment when
they see guifi.net maps like:
http://guifi.net/en/node/2413/view/map
or, nicer for normal people:
http://guifi.net/en/guifi/menu/stats/growthmap
("Init" | "Play")
Pre 2:
If you take a look to "site:libre-mesh.org" in a search engine (that is
something a lot of people do in order to understand a website) we can
see there http://map.libre-mesh.org/ which is working with a lot of nodes.
We know more or less that we are not using that map, so it is not fully
updated.
Content:
Let's do some official in http://map.libre-mesh.org/ or, at least, let's
plan it.
Salut!
The OTI is funding projects for mesh network deployment, here is the call:
https://commotionwireless.net/blog/2014/10/08/call-for-proposals-small-gran…
It looks like they expect the people who apply to use Commotion, but
maybe I'm wrong. If someone here has more information it would be
appreciated.
Cheers.
--
./p4u
Hi!
This commit b7cf9e84106ee1aadd028aa526ac12ea82ba3a7e [0] break vlan creation (
vlan are not created anymore ) because @logical_name is not supported in
device sections, moreover in most cases like @lm_eth0 logical name refer to a
nonexistent logical interface, if netifd suffer race conditions on boot then
the problem is inside netifd and cannot be worked around this way, in fact we
don't get the race condition anymore but because the device is just not
created anymore, we should fix netifd submitting patch to openwrt-devel/Felix
if we wanna race conditions solved not break our meta-firmware ;)
[0] https://github.com/libre-mesh/lime-packages/commit/b7cf9e84106ee1aadd028aa5…
---------- Forwarded Message ----------
Subject: [OpenWrt-Devel] Barrier Breaker 14.07 Final
Date: Thursday 02 October 2014, 14:59:08
From: Steven Barth <cyrus(a)openwrt.org>
To: openwrt-devel(a)lists.openwrt.org
The OpenWrt developers are proud to announce the final release
of OpenWrt Barrier Breaker.
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
BARRIER BREAKER (14.07)
-----------------------------------------------------
* 1/2 oz Galliano Pour all ingredients into
* 4 oz cold Coffee an irish coffee mug filled
* 1 1/2 oz Dark Rum with crushed ice. Stir.
* 2 tsp. Creme de Cacao
-----------------------------------------------------
http://downloads.openwrt.org/barrier_breaker/14.07/
Important changes since RC3
* various ath9k related fixes
* a few board related fixes
* fixes for packages depdending on curl
* per feed download folders
Important changes since RC2
* NAT & firewall throughput improvements
* Security updates for OpenSSL & PolarSSL
* Minor fixes in DHCP & DHCPv6 handling
* Configuration support for GRE tunnels
* Various other fixes
Important changes since RC1
* fix a long standing ath9k deadlock bug
* all feeds are now built
* image builder now works and RC2 contains all board specific images
* various board/stability fixes
** Highlights since Attitude Adjustment **
Default configuration and images
* Linux kernel updated to version 3.10
* Procd: new preinit, init, hotplug and event system written in C
* Native IPv6-support
- RA & DHCPv6+PD client and server
- Local prefix allocation & source-restricted routes
(multihoming)
* Filesystem improvements
- Added support for sysupgrade on NAND-flash
- Added support for filesystem snapshot and rollback
- Rewritten mounting system in C for rootfs and block devices
* UCI configuration improvements
- Support for testing configuration and rollback to working
last working state
- Unified change trigger system to restart services on-demand
- Added a data validation layer
* Networking improvements
- Netifd now handles setup and configuration reload of
wireless interfaces
- Added reworked event support to allow obsoleting network
hotplug-scripts
- Added support for dynamic firewall rules and zones
- Added support for transparent multicast to unicast
translation for bridges
- Various other fixes and improvements
Additional highlights selectable in the package feeds or SDK
* Extended IPv6-support
- Added DS-Lite support and improved 6to4, 6in4 and 6rd-support
- Experimental support for Lightweight 4over6, MAP-E and MAP-T
- Draft-support for self-managing home networks (HNCP)
* rpcd: new JSONRPC over HTTP-frontend for remote access to ubus
* mdns: new lightweight mdns daemon (work in progress)
* Initial support for the musl C standard library
* Support for QMI-based 3g/4g modems
* Support for DNSSEC validation
* Added architecture for package signing and SHA256 hashing
* ... and many more cool things
Package feed reorganization
For quite a while already we are not very satisfied with the quality
of the packages-feed. To address this, we decided to do a fresh start
on GitHub. The new feed https://github.com/openwrt/packages should be
used from now on and package maintainers are asked to move their
packages there. For the final release we will still build the old
packages feed but it will be necessary to enable it manually in the
opkg package list to be usable.
Additionally we would like to give a big thank you to all of our
package
maintainers working on our various feeds.
New build servers
We would like to express our gratitude to Imagination Technology for
funding the 2 build servers that we used for the release.
Whats next ?
We aim at releasing Chaos Calmer (CC) before the end of the year. The
CC release will use 3.14 or a newer LTS kernel as baseline.
Have fun!
The OpenWrt developer team
_______________________________________________
openwrt-devel mailing list
openwrt-devel(a)lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
-----------------------------------------
Hi, is there a way to configure dhcp static leases in libre-mesh firmware?
Which is the right dnsmasq setup?
Thanks
LP
--
luca.postregna.name
twitter.com/lucapost
Hi.
As some of you already know, the last days I have been testing the
possibility of use 802.11s as link layer instead of adhoc.
By default 11s comes with a kind of layer2 routing (same as bat-adv
does) by using HWMP (hybrid wireless mesh protocol) which in general is
quite shitty compared to other well known solutions.
However, if the option mesh_fwding is set to 0, this l2 routing layer is
disabled and 11s can be used just as layer1 protocol in the same level
of Ad-Hoc or AP/Infrastructure.
From OpenWRt these are the needed options to enable 11s as link layer:
uci set wireless.mesh0.mode=mesh
uci set wireless.mesh0.mesh_id=wibed
uci set wireless.mesh0.mesh_fwding=0
Using 11s instead of adhoc for deploying our mesh networks can bring
some interesting features, among others:
1. Better support for 11n
2. Better compatibility with drivers (probably even ath_htc works fine)
3. You can bridge it to another interface if necessary.
4. It does NOT try to synchronize the TSF counter of your wifi card thus
you can create up to 8 11s VAP mixed with adhoc, AP, client, etc...
5. I don't know deeply 11s but it probably has better design for
deploying mesh networks
I've been testing it in a 12 nodes mesh network mixing it with bmx6 and
it worked as a charm. No more "strange" problems coming from the adhoc
layer.
Yesterday Gio the great added support for 11s in libre-mesh [1]. So now
we only need to test it a bit more with our already crazy network
architecture, so it may became even a bit more crazy for traditional
mesh folks (bmx6+bat-adv+11s, never done something like that!).
Opinion? Concerns? Ideas?
[1] https://github.com/libre-mesh/lime-packages/tree/feature/80211s
--
./p4u
