On 11/06/17 12:43, Daniel Golle wrote:
On Mon, Jun 05, 2017 at 03:08:34PM +0200, Pau wrote:
On 05/06/17 14:07, Daniel Golle wrote:
Hi!
Hi Daniel.
I finally got to the point to test the results of
running 802.11s on
plain LEDE and want to switch to the upcoming LiMe release and help
testing. As most of the folders on the release download server are
still empty I liberated enough free space on my SSD to build the SDK
and IB from scratch myself. The good part: Congratulations for
switching to the IB+SDK and starting a more productive colaboration
with the upstream projects! It's great to see that the Libremesh
fishtank has finally poured into the open sea :)
In the next week I'll be working on a test-deployment which will be
based on the upcoming LiMe release and hence LEDE-17.01.2(-pre) on a
Lantiq XRX200 device providing a VDSL gateway plus a bunch of ar71xx
devices providing the mesh+APs. I hope that we can then annouce to have
sucessfully overcome the boundaries of only using only one hardware
platform. And make the switch to 11s (which I'll be using there as
well)
Good! I think we are going in the good direction.
Initial testing went quite ok, I only run into minor and easy to fix
Can you add your comments regarding 11s to this issue?
https://github.com/libremesh/lime-packages/issues/129
So we can have track of them.
problems:
* cooker de-facto blacklisted a bunch of packages:
```
# Not flavors but common set of packages
_lime_common="-ppp -dnsmasq -ppp-mod-pppoe -6relayd -odhcp6c -odhcpd
-firewall"
```
While this does make sense for dnsmasq (in order to use dnsmasq-ipv6)
it makes it impossible to configure a lime node to act as a PPPoE
gateway and have a reasonale WAN firewall.
I've moved those package-removals into the shrinked-down flavors of
lime, so lime-default (which has already grown beyond the 4MB mark)
can be used as a gateway on typical commercial ISP lines.
You right, probably it would make more sense to add the removal on the
specific flavors instead of a common set. Lime-default can include the
PPP related stuff. I'd accept a PR regarding this.
Note that this for now solves only IPv4 routing -- I
have IPv6 in mind
and am about to make another round about
https://github.com/libremesh/lime-packages/pull/71
(ie. getting upstream prefix changes via ubus, maybe use odhcpd for
alfred lease-sharing)
* I've noticed that lime_mini removes opkg, however, opkg is used in a
couple of lime-proto-* handlers to detect the presence of the default
fw3 firewall. Did you test if luci.model.ipkg works even without
opkg installed?
This was already fixed:
https://github.com/libremesh/lime-packages/commit/7f66e5a5f7dd39caae4b14f55…
https://github.com/libremesh/lime-packages/commit/178e21bc65f0fadb544ca8864…
* The IB was also using locally built packages even if
they are part
of the binary release. This caused checksum errors on non-reproducible
packages. I added a filter to the repository.conf generation to make
sure only the packages we have to build locally are being included from
the local SDK.
Great, can you share this filter?
The GsOC from
Marcos (Luci2 on LibreMesh) and these days at the WBM in
Vienna will change the course of lime-ui, for sure.
I'm wondering how things went for lime-related affairs in this years
WBM. Especially:
* any news in terms of bmx6/7 IPv6 gateway prefix propagation?
Axel might comment about this. But what I understood is that it is not
yet implemented in a stable and complete way.
An interesting new regarding bmx6/7 is that it seems we found a solution
for the bmx ipv6 tunnels MTU issue which has been creating unexpected
behaviors on lime since long ago.
* any news on the batman-adv front in terms of the BLA
race condition
we were discussing during last year's event?
* any news on ath9k-deafness and possible work-arounds?
* what was is your conclusion in terms of air-time-fairness scheduling?
(the graphs are a bit misleading imho as the scale is not the same)
No news from my side regarding this. Maybe someone else can comment.
Another topics regarding WBM and LiMe:
Marcos and Jow talked about Luci2 and LiMe. It looks like we will work
together in the same direction. So the work done for lime web interface
will be also probably used for LEDE.
We made a meeting with the Gluon team, it looks like we will try to join
some efforts. Not to migrate/converge our projects (we have different
scope) but share things that can be used in both sides.
Cheers!
Cheers
Daniel
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev
--
./p4u