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

status tab (Nearby Mesh Devices) #92

Closed
seamustuohy opened this issue Nov 19, 2013 · 8 comments
Closed

status tab (Nearby Mesh Devices) #92

seamustuohy opened this issue Nov 19, 2013 · 8 comments
Assignees

Comments

@seamustuohy
Copy link
Collaborator

This tab will be a recreation of the neighbors list that shows the following about nodes on the mesh
list header: Hostname
list header: Mesh IP-Address
list header:RX signal
help icon text: (STILL NEEDED)
list header:ETX value
help icon text: (STILL NEEDED)
list header: Gateway?
list-options: yes/
list header: Hops Away
help icon text: (STILL NEEDED)

@ghost ghost assigned areynold Dec 5, 2013
@critzo
Copy link

critzo commented Dec 6, 2013

Some of these items need to be deferred to 1.1: Hostname, Gateway, Hops Away

The rest should be added for 1.0.

ETX value help icon text:
Expected Transmission Count - the expected number of retransmission attempts that are required for a packet to travel to and from a destination.

RX Signal help text:
Data reception rate.

@areynold
Copy link
Collaborator

areynold commented Dec 6, 2013

I've sketched out the basics of the page, including a mostly functional implementation of the neighbors list.

A few notes:

  • Hostname will require us to add an olsrd plugin
  • As far as I can tell, RX signal will require some additional tooling to collect and correlate with olsr info. As critzo notes above, this can be moved to 1.1.
  • The neighbors list currently uses txtinfo, not jsoninfo.
  • Number of hops is available through both txtinfo and jsoninfo. We should decide on a plugin before implementing.
  • Gateway is available through txtinfo and jsoninfo. We should decide on a plugin before implementing.
  • This implementation is almost a direct copy of the existing olsr neighbors page, which is almost suitable for use as a module. A better long term implementation would be to rewrite olsr's neighbors page to accept different arguments.

Submitting a pull request of the partial implementation in order to minimize conflicts.

@areynold areynold mentioned this issue Dec 6, 2013
@seamustuohy
Copy link
Collaborator Author

@areynold Remind me to show you how I wrote the connected clients page with functions with enough encapsulation to allow us to re-implement the neighbours page in a matter of minutes once R1 comes out. :)

@seamustuohy
Copy link
Collaborator Author

Current implementation only shows IP Address and ETX Value. There is a hostname field but it always sits at ?. As such our implementation simply removes functionality from the existing version.

@areynold areynold closed this as completed Jan 8, 2014
@seamustuohy
Copy link
Collaborator Author

This page still has one broken column and incomplete functionality. As such, reopened.

@seamustuohy seamustuohy reopened this Jan 8, 2014
@areynold
Copy link
Collaborator

areynold commented Jan 8, 2014

Which column is still broken?
nearby-md-screenshot

@seamustuohy
Copy link
Collaborator Author

Did we add the olsrd-hostname plugin back in to the build? I thought we were keeping it out. I had not looked at the net status since it was fixed.

@georgiamoon
Copy link
Member

Can we re-open this for an upcoming milestone to add the rest of the values in? Or should that be a new issue?

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