It is not my intention to jump to trunk, I think we should keep in the
stable version unless there is some important point for going trunk.
This lime-eb-ip-tables packet does not affect in any way to openwrt
stable, it just selects a set of dependencies which are right now
already selected. The good point here is that if someone wants to
compile lime in trunk, it will still works thanks to this legacy packet.
Using nftables instead of iptables can be a good point to include in the
future next release, however it will require some work. So for the
moment I would continue using iptables.
In the other side the bmx6-auto-gw-mode brings (IMO) a very needed
feature to lime, it automates the publication of Internet, so the user
does not need to execute shell commands for doing so, and if the
connection breaks in some moment, it turns off the bmx6 announcement and
uses some other mesh gateway.
On 14/01/15 17:30, Pau wrote:
I wrote and commited a couple of packets in the new
branch
feature/bmx6-auto-gw-mode
bmx6-auto-gw-mode: watchping module for bmx6, it automatically announces
an Internet access in the network if detected. I added it as dependency
packet for lime-full
lime-eb-ip-tables: a meta-packet which includes the ebtables/iptables
required modules. If not enabled there is no NAT nor Masquerade in last
openwrt trunk
Comments or complains?
https://github.com/libre-mesh/lime-packages/tree/feature/bmx6-auto-gw-mode
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
--
./p4u