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

seperate extender node firmware build into a different branch and/or tag a seperate release #130

Closed
paidforby opened this issue Apr 9, 2018 · 2 comments

Comments

@paidforby
Copy link

Related to sudomesh/bugs#26 and sudomesh/bugs#27

I think it would be useful to separate the extender node firmware into a different branch, or at least tag a different release once it has been tested as working with certain antennas.

This would be a cleaner way of dealing with extender node configs and make it easier for people to contribute to extender node development.

@paidforby
Copy link
Author

After more thought, it looks like we are moving away from maintaining separate extender node firmware. Furthermore, I would suggest that if someone does revisit the extender node firmware idea, that they should attempt to make extender nodes "full nodes", that is they would have their own range of mesh IPs, run tunneldigger and be able to dig tunnels to an exit node. If some does work on this, they should open a new issue specific to their work.

@paidforby
Copy link
Author

for posterity, I created an extender-node directory in the repo to hold legacy info regarding extender nodes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant