Skip to content
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

Closed
aparcar opened this issue Jun 17, 2017 · 9 comments
Closed

make router profile aware #8

aparcar opened this issue Jun 17, 2017 · 9 comments

Comments

@aparcar
Copy link
Member

aparcar commented Jun 17, 2017

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?

@nicopace
Copy link
Member

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.
I think @p4u has been looking on this... (do you see a pattern here? ... :) ).

@aparcar
Copy link
Member Author

aparcar commented Jun 18, 2017

May a possible solution:

  • Generate the packages mentioned in create network-profile packages #7 so a opkg list would already supply the information
    or
  • Add a simple txt/yaml file /etc/network-profile containing the network-profile name
    • Auto created via cooker/update-server
    • Put in the repository, may filled with additional information about the profile

@aparcar
Copy link
Member Author

aparcar commented Jul 25, 2017

updates on this? It's not a must feature as config files should be saved on sysupgrade anyway

@nicopace
Copy link
Member

nicopace commented Aug 1, 2017

Maybe this is something you need to ask for in the lime-sdk project

@aparcar
Copy link
Member Author

aparcar commented Aug 2, 2017

Not only lime-sdk but the imagebuilder as well can "handle" network profiles...

@aparcar
Copy link
Member Author

aparcar commented Nov 4, 2017

Solution would be to use the packages produced here:
#7

@p4u
Copy link
Member

p4u commented Nov 7, 2017

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

@aparcar
Copy link
Member Author

aparcar commented Nov 7, 2017

@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!

@aparcar
Copy link
Member Author

aparcar commented Nov 12, 2017

All solved I think via this http://repo.libremesh.org/network-profiles/

@aparcar aparcar closed this as completed Nov 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants