14 Jan
2015
14 Jan
'15
4:30 p.m.
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
--
./p4u
14 Jan
14 Jan
5:18 p.m.
On Wednesday, January 14, 2015 05:30:49 PM 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?
Didn't had time to look at the code, i was just wondering is it a good idea to
switch already to openwrt trunk?
I would keep actual develop branch on top of the latest stable (that was
released some month ago) because we still miss a lime stable release, i do
prefer we do commit relative to openwrt trunk in a new branch
as for the iptables dependency i believe openwrt doesn't include it anymore
because of nftables that is the new recommended firewall for linux, so we
should discuss this i believe
5:40 p.m.
On 01/14/2015 06:18 PM, Gioacchino Mazzurco wrote:
On Wednesday, January 14, 2015 05:30:49 PM Pau wrote:
+1
If not enabled there is no NAT nor Masquerade in
last
openwrt trunk
i was just wondering is it a good idea to
switch already to openwrt trunk?
I would keep actual develop branch on top of the latest stable (that was
released some month ago) because we still miss a lime stable release, i do
prefer we do commit relative to openwrt trunk in a new branch
7:14 p.m.
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
7:23 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On January 14, 2015 4:14:02 PM GMT-03:00, Pau <pau(a)dabax.net> wrote:
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.
+1000, pau sprint for the win!
will test out your commits this week and prepare a release, at last!
(this bmx6 announcement was a LiMe showstopper bug all this time, thanks pau!)
cheerful gui \o/
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
>
-----BEGIN PGP SIGNATURE-----
Version: APG v1.1.1
iQJABAEBCgAqBQJUtsI4IxxHdWkgSXJpYmFycmVuIDxndWlAYWx0ZXJtdW5kaS5u
ZXQ+AAoJEIJqNBvBfxrI0hgQAIzSTNEiFrV7aFUn3Uoxw44Vp2mphAYqcGNOesfA
kQzFCqdwEtEw3PEi2aRslRGaBc9GxB4wxcPy7fdJZoBnM0S5oLOLrB+9ZJSUrFlf
Dw9xh7e143H93tcaFx3mMOXAX9a4dwENtSxg0qRbbIe8NKtb7KYn5U1nB4XbjIPU
F/bfQTDe9ubF0x8rZVaxRTXp16nAne5nrXePMRCDqk9Hj0A0aurpxCGhf0TKqr68
HTmf6ADRbfWRDPlLtKCBGdeZNMJ5Z0/yg6D1VzmA6gT9LuX4OHePq1JHGinCSScd
SIY7Zjvpc1B812Sr295GkwLJA+6MoTyVMbhvzwceP3EEiy4yMzvL1Rk5lr0nPG4t
+sa7+cRMjVFmGemMiMYPfYi/6AladH6R36a8tpGk1rvj3JHHx2w8UzlEQTUVzevB
U950YIEXzzHVt7TGdNVHPwBgGinxfyXEKG3cN2qvVFG3OlUrO0cLvMokBp0U3c9E
HyT2Vnv70VsP5iAXrdxBR1nOK7Yx/TXbCztmB5xEtevZPjdBuPTlz2Caksk1EYjV
P7mDv1yJHD4VpMt7Tly1F9NzhogjJyZ4j+1OZZ5E4kzYBKwHk624yzhu0l519C3V
j/mIXAePLa58PK2UCfvltzL+bt+0MSPB7pa8KSysgYtVf5IyvAiFzqjbYxsfM1K0
kdHG
=3xZO
-----END PGP SIGNATURE-----
8:14 p.m.
From a rapid review code seem ok to me, only missing
thing i spotted is the ip
depend for bmx6-auto-gw-mode it is used to get the output
interface
iface="$(ip route get 8.8.8.8 | awk '{print $5}' | tr -d
'\n')"
On Wednesday, January 14, 2015 08:14:02 PM Pau wrote:
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
8:15 p.m.
Good point!
On 14/01/15 21:14, Gioacchino Mazzurco wrote:
From a rapid review code seem ok to me, only missing
thing i spotted is the ip
depend for bmx6-auto-gw-mode it is used to get the output interface
iface="$(ip route get 8.8.8.8 | awk '{print $5}' | tr -d
'\n')"
On Wednesday, January 14, 2015 08:14:02 PM Pau wrote:
--
./p4u
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
8:32 p.m.
I have spotted another problematic line
https://github.com/libre-mesh/lime-packages/commit/1a068e3aa4fd4c6bbf4b4b5f…
This settings shouldn't be done in network.clean, but in proto-wan.configure as
it is already [0], I don't know if it break something right now but it break
the modules logic so it can cause unpredictable problems maybe bmx-auto-gw
shoud depends on lime-proto-wan too ?
[0]
https://github.com/libre-mesh/lime-packages/blob/develop/packages/lime-prot…
9:05 p.m.
In my test, lime-proto-wan is installed (since it is a dependency for
lime-full), however after running lime-config the wan interface is still
"none". I'm not sure if it is the normal behavior or there is some bug
here. However IMO the network.clean should leave the interfaces on its
default values (or remove them). In the case of wan it makes sense to
leave it as "dhcp".
If we can fix this lime-proto-wan issue, we can change it back to "none"
and add it as dependency for bmx6-auto-gw-mode
On 14/01/15 21:32, Gioacchino Mazzurco wrote:
I have spotted another problematic line
https://github.com/libre-mesh/lime-packages/commit/1a068e3aa4fd4c6bbf4b4b5f…
This settings shouldn't be done in network.clean, but in proto-wan.configure as
it is already [0], I don't know if it break something right now but it break
the modules logic so it can cause unpredictable problems maybe bmx-auto-gw
shoud depends on lime-proto-wan too ?
[0]
https://github.com/libre-mesh/lime-packages/blob/develop/packages/lime-prot…
--
./p4u
15 Jan
15 Jan
10:26 a.m.
Gui, can you please check and merge to develop this new watchping branch?
Add support for wifi interfaces or others which are not configured as
uci network.$interface.ifname, uci_get_state brings the exact OS ifname
(including br-lan or wlanX)
Add a new option (not mandatory) for watchping to specify the hook name
(by default hookname=interface)
Remove redundant check of ifname (it is already checked in the init.d
script)
https://github.com/libre-mesh/lime-packages/commit/d5abf5dce299460d78b034cd…
On 14/01/15 22:05, Pau wrote:
In my test, lime-proto-wan is installed (since it is a
dependency for
lime-full), however after running lime-config the wan interface is still
"none". I'm not sure if it is the normal behavior or there is some bug
here. However IMO the network.clean should leave the interfaces on its
default values (or remove them). In the case of wan it makes sense to
leave it as "dhcp".
If we can fix this lime-proto-wan issue, we can change it back to "none"
and add it as dependency for bmx6-auto-gw-mode
On 14/01/15 21:32, Gioacchino Mazzurco wrote:
--
./p4u
I have spotted another problematic line
https://github.com/libre-mesh/lime-packages/commit/1a068e3aa4fd4c6bbf4b4b5f…
This settings shouldn't be done in network.clean, but in proto-wan.configure as
it is already [0], I don't know if it break something right now but it break
the modules logic so it can cause unpredictable problems maybe bmx-auto-gw
shoud depends on lime-proto-wan too ?
[0]
https://github.com/libre-mesh/lime-packages/blob/develop/packages/lime-prot…
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
28 Jan
28 Jan
9:43 a.m.
I created the new branch "merge_develop" where we may put the changes we
want to merge into develop.
I've tested it in my routers and works fine, can someone else take a
look (test it if possible) and merge it to develop?
It includes the watchping-improved and bmx6-auto-gw-mode in addition to
the firewall/ebtables fix.
Cheers.
On 15/01/15 11:26, Pau wrote:
Gui, can you please check and merge to develop this
new watchping branch?
Add support for wifi interfaces or others which are not configured as
uci network.$interface.ifname, uci_get_state brings the exact OS ifname
(including br-lan or wlanX)
Add a new option (not mandatory) for watchping to specify the hook name
(by default hookname=interface)
Remove redundant check of ifname (it is already checked in the init.d
script)
https://github.com/libre-mesh/lime-packages/commit/d5abf5dce299460d78b034cd…
On 14/01/15 22:05, Pau wrote:
--
./p4u
In my test, lime-proto-wan is installed (since it
is a dependency for
lime-full), however after running lime-config the wan interface is still
"none". I'm not sure if it is the normal behavior or there is some bug
here. However IMO the network.clean should leave the interfaces on its
default values (or remove them). In the case of wan it makes sense to
leave it as "dhcp".
If we can fix this lime-proto-wan issue, we can change it back to "none"
and add it as dependency for bmx6-auto-gw-mode
On 14/01/15 21:32, Gioacchino Mazzurco wrote:
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
I have spotted another problematic line
https://github.com/libre-mesh/lime-packages/commit/1a068e3aa4fd4c6bbf4b4b5f…
This settings shouldn't be done in network.clean, but in proto-wan.configure as
it is already [0], I don't know if it break something right now but it break
the modules logic so it can cause unpredictable problems maybe bmx-auto-gw
shoud depends on lime-proto-wan too ?
[0]
https://github.com/libre-mesh/lime-packages/blob/develop/packages/lime-prot…
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
15 Jan
15 Jan
11:33 a.m.
On Wednesday, January 14, 2015 10:05:47 PM Pau wrote:
In my test, lime-proto-wan is installed (since it is a
dependency for
lime-full), however after running lime-config the wan interface is still
"none". I'm not sure if it is the normal behavior or there is some bug
here. However IMO the network.clean should leave the interfaces on its
default values (or remove them). In the case of wan it makes sense to
leave it as "dhcp".
No because this break some setups, lime-proto-wan is not mandatory so this way
we avoid an hard depends on it, it is not in the list of protocols by default
(it is not included in lime system), because the user or some hardware
detection module like lime-hwd-openwrt-wan have to specify on which interface
should proto wan operate, i believe lime-full should depends both on lime-hwd-
openwrt-wan and lime-proto-wan so the blue port get configured as wan by
default, can you repeat your test with both packages installed? If they were
already both installed it mean there is a bug somewhere, but we should not put
dhcp nor delete wan interface on clean (would break interface scanning on some
hardware)
If we can fix this lime-proto-wan issue, we can change
it back to "none"
and add it as dependency for bmx6-auto-gw-mode
As said before I believe this should already work if lime-hwd-openwrt-wan and
lime-proto-wan, if not we have to look for a bug on one of those two packages
;)
3:04 p.m.
It seems there is a bug in proto-wan as it should set wan interface proto as
dhcp in the case you illustrated in private (lime-hwd-openwrt-wan + lime-
proto-wan)
On Thursday, January 15, 2015 12:33:04 PM Gioacchino Mazzurco wrote:
On Wednesday, January 14, 2015 10:05:47 PM Pau wrote:
In my test, lime-proto-wan is installed (since it
is a dependency for
lime-full), however after running lime-config the wan interface is still
"none". I'm not sure if it is the normal behavior or there is some bug
here. However IMO the network.clean should leave the interfaces on its
default values (or remove them). In the case of wan it makes sense to
leave it as "dhcp".
No because this break some setups, lime-proto-wan is not mandatory so this
way we avoid an hard depends on it, it is not in the list of protocols by
default (it is not included in lime system), because the user or some
hardware detection module like lime-hwd-openwrt-wan have to specify on
which interface should proto wan operate, i believe lime-full should
depends both on lime-hwd- openwrt-wan and lime-proto-wan so the blue port
get configured as wan by default, can you repeat your test with both
packages installed? If they were already both installed it mean there is a
bug somewhere, but we should not put dhcp nor delete wan interface on clean
(would break interface scanning on some hardware)
If we can fix this lime-proto-wan issue, we can
change it back to "none"
and add it as dependency for bmx6-auto-gw-mode
As said before I believe this should already work if lime-hwd-openwrt-wan
and lime-proto-wan, if not we have to look for a bug on one of those two
packages ;)
5:17 p.m.
On Thursday, January 15, 2015 04:04:30 PM Gioacchino Mazzurco wrote:
It seems there is a bug in proto-wan as it should set
wan interface proto as
dhcp in the case you illustrated in private (lime-hwd-openwrt-wan + lime-
proto-wan)
Just pushed a couple of commits that fix the bug you discovered ;)
7:49 p.m.
Thanks!
On 15/01/15 18:17, Gioacchino Mazzurco wrote:
On Thursday, January 15, 2015 04:04:30 PM Gioacchino
Mazzurco wrote:
--
./p4u
It seems there is a bug in proto-wan as it should
set wan interface proto as
dhcp in the case you illustrated in private (lime-hwd-openwrt-wan + lime-
proto-wan)
Just pushed a couple of commits that fix the bug you discovered ;)
3615
days inactive
3629
days old
14 comments
4 participants
participants (4)
-
Gioacchino Mazzurco -
Gui Iribarren -
Ilario GELMETTI -
Pau