-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make router profile aware #8
Comments
I think it is not implemneted... but it is actually a good idea to embed something like a 'fingerprint' of the config so it can be identified. |
May a possible solution:
|
updates on this? It's not a must feature as config files should be saved on sysupgrade anyway |
Maybe this is something you need to ask for in the lime-sdk project |
Not only lime-sdk but the imagebuilder as well can "handle" network profiles... |
Solution would be to use the packages produced here: |
I would include this information (network profile) to /etc/lime_release The packages generated with your script might include, by default, an uci-defaults script to add an extra line to this file containing the network-profile information on first boot Also lime-sdk (cooker) might be modified to write this uci-defaults scripts in case a --community is specified |
@p4u if installed via package the network-profile is withn the packagelist and would be automatically requested on sysupgrade. That solves the issue already for me. Introducing a new parameter to lime_release makes it less "conform" with regular LEDE, in future I'd like to see all lime-packages move to official LEDE packages so not introduce to many special modifications. unify all the stuff! |
All solved I think via this http://repo.libremesh.org/network-profiles/ |
in addition to #7 it could be useful to make the routers aware of the used network-profile so it can ask a possible update server to include the profile.
Is this already implemented and I'm missing something?
The text was updated successfully, but these errors were encountered: