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

[docs] Some possible improvements #62

Closed
EdgeKing810 opened this issue Nov 2, 2018 · 2 comments
Closed

[docs] Some possible improvements #62

EdgeKing810 opened this issue Nov 2, 2018 · 2 comments

Comments

@EdgeKing810
Copy link
Contributor

EdgeKing810 commented Nov 2, 2018

So I had a task where I had to a vm with OpenWRT and connect it to OpenWISP locally. There were some challenges that I faced and here's a list of what can be improved so that other students/people don't get confused and know exactly what to do.

1.) I couldn't get the network to work in my OpenWRT vm.
refer to: https://openwrt.org/docs/guide-user/virtualization/virtualbox-vm
For the second adapter, it wasn't mention what to use. I was using the PCInet-III or something instead of the Intel Pro (82540EM)
I thought it would be good to let you know so that future individuals don't face this problem.

2.) Oh and for the allocation of , it would be better that on this tutorial if it was set to 192.168.56.3 (more than 192.168.56.2 as it is used for the OpenWISP Server).

3.) After setting up everything, I found out that no devices were being created on the local OpenWISP website.
I had the message "openwisp: OpenWISP config agent started" but there was nothing on the website.
I later found out (thanks to reza) how to fix all that. Some info on: http://openwisp.io/docs/user/configure-device.html need to be improved as there is some confusion. Firstly lines "option uuid" and "option key" should be commented I think, secondly it would be great if it was mentionned that if we had our OpenWISP server locally (e.g 192.168.56.2), then the "option url" would be 'https://192.168.56.2'. That is more beginner-friendly as they know what to write, if should be mentioned and if whether ".../admin" should be written or not.

Otherwise everything is great! I am not saying that anything was bad. On the contrary, the tutorial is really awesome! I am just suggesting how it would better, that's all!

@hispanico hispanico added this to To do (general) in OpenWISP Contributor's Board via automation Nov 2, 2018
@hispanico hispanico changed the title Some possible improvements [docs] Some possible improvements Nov 2, 2018
@hispanico hispanico moved this from To do (general) to To do (documentation) in OpenWISP Contributor's Board Nov 2, 2018
@atb00ker
Copy link
Member

atb00ker commented Nov 2, 2018

Firstly lines "option uuid" and "option key" should be commented I think

I only need to confirm this line, the rest looks good to me! 👍

@ppabcd
Copy link
Contributor

ppabcd commented Nov 8, 2018

nice 😂

OpenWISP Contributor's Board automation moved this from To do (documentation) to Done Nov 12, 2018
nemesifier added a commit that referenced this issue Nov 12, 2018
[user/configure-device.rst] Made it more beginner-friendly! #62
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants