[lime] Highlights from the list of issues

このメッセージを削除

このメッセージに返信
著者: Ilario
日付:  
To: LibreMesh
題目: [lime] Highlights from the list of issues
Hi all!
I checked the list of the open issues on the lime-packages repository on
Github.
I personally think that we should make a release by the end of 2024
(simply so that we don't need to change the name to 2025 XD), so here
you are a list of the issues that I consider relevant for the release
and easy to fix (relevant = it would be nice to fix these before the
final release, but we can make the release anyway).
Any help fixing them is appreciated!

You can see them online here (the ones that have 2024.1 as a milestone):
https://github.com/orgs/libremesh/projects/3

Or you can read a short description of them here:

This one makes deferable-reboot much more reasonable (currently,
deferable-reboot reboots the router every 27 hours, very annoying):
"Include auto-defer mechanism in deferable-reboot"
https://github.com/libremesh/lime-packages/issues/1023

Here a package (ip) needs to be added to the list of dependencies for
installing another package (ubus-lime-utils):
"ubus call lime-utils get_node_status problem in some dsa routers"
https://github.com/libremesh/lime-packages/issues/1137

I am not sure I understood this one. Seems that we must modify a bit the
release process splitting some repositories and indicating the new
location in the list of repositories:
"shared-state-async nohttps://github.com/orgs/libremesh/projects/3t
syncing bat-hosts"
https://github.com/libremesh/lime-packages/issues/1135

This problem happens when connecting two LibreMesh nodes via cable. An
easy mitigation is to document very well the need for specific
configuration in this case (in the future I hope it will be configurable
also via lime-app!!???). Unless we find a proper solution, the
documentation can be written also after the release...
"Problems with ethernet connections between routers in default
configuration"
https://github.com/libremesh/lime-packages/issues/1121

Here there is a dependency missing. In the same issue, there is also the
indication for an "if" missing. This "if" should check for the presence
of an interface before using it:
"ubus-lime-utils uses watchping but does not depend on it and should
check for client-wwan before running"
https://github.com/libremesh/lime-packages/issues/956

This is just a very useful feature, that needs to be confirmed and
documented. Both with the copy_asset or simply creating the needed file.
"Avoid IP collisions with servers' static IP in the mesh"
https://github.com/libremesh/lime-packages/issues/864

A check should be added to a line of code that is used for adding a line
to a file unless that line is already present:
"unique_append should check if /etc/crontabs/root file exist before
appending"
https://github.com/libremesh/lime-packages/issues/949

An error has been observed in the logs, and seems very easy to fix:
"hotplug-initd-observer error"
https://github.com/libremesh/lime-packages/issues/1064

This is easy to solve as SAn already wrote the code that should fix.
Still, some testing is needed to make sure the proposed solution is
useful. We can leave this for the next release.
"lime.wireless validate that the radios are working"
https://github.com/libremesh/lime-packages/issues/878

This one is for dealing for the situation that G10h4ck mentioned in the
discussions about the GSoC project "Cable purpose autodetection" (one
commercial router injecting wrong DHCP offers in the mesh):
"Filter DHCP offers from other nodes on LAN"
https://github.com/libremesh/lime-packages/issues/658
the firewall rules proposed by Henrique in the comments should be added
to lime-proto-anygw. Maybe better to leave this for the next release.

Ciao!
Ilario


--
Ilario
iochesonome@???
ilario@???

Correct

Basic

Close

Missing comma

Possible missing comma found.

solve,Ignore