15 Jan
2015
15 Jan
'15
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 ;)