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

Version 1.0 and 1.1 mesh connections not compatible #113

Closed
andygunn opened this issue Mar 6, 2014 · 5 comments
Closed

Version 1.0 and 1.1 mesh connections not compatible #113

andygunn opened this issue Mar 6, 2014 · 5 comments

Comments

@andygunn
Copy link

andygunn commented Mar 6, 2014

It seems that there are non-compatible (or non-OLSR visible / routable?) meshes created by Version 1.0 and Version 1.1. The result is that when using a Version 1.0 node, you cannot see Version 1.1 devices, and vice versa.

To replicate:

  • Install version 1, run through Setup sorcerer
  • Display OLSR neighbors / OLSR-vis to verify existing neighbors
  • Upgrade to Version 1.1, keep settings (or clear and setup with identical settings)
  • Display OLSR neighbors / OLSR-vis to verify different neighbors

Screenshots from Version 1.0:

version1-1 1 mesh compat 1

version1-1 1 mesh compat 2

Screenshots from Version 1.1:

version1-1 1 mesh compat 3

version1-1 1 mesh compat 4

@andygunn andygunn added this to the 1.1 milestone Mar 6, 2014
@andygunn
Copy link
Author

andygunn commented Mar 6, 2014

@jheretic - You were correct, it appears to be a BSSID bug in Version 1.0:

  • Version 1 BSSID: B4:21:C8:3D:00:05
  • Version 1.1 BSSID: 02:21:C8:3D:00:05 (post upgrade with "Keep Settings")
  • Version 1.1 BSSID: 02:21:C8:3D:00:05 (after reset to defaults and re-run of Setup sorcerer)

@areynold
Copy link
Collaborator

@andygunn Since this was a version 1.0 BSSID bug that is fixed in 1.1, what (if anything) needs to happen? Documentation? If so, where?

@andygunn
Copy link
Author

andygunn commented Apr 1, 2014

@areynold @jheretic I think documentation is all this needs.

My suggestion is to create a "Known bugs" page (or section on the downloads page) related to 1.0 ( @critzo I'm looking at you ) and post this and any other outstanding major issues with releases there. Once 1.1 is released these can be cleared, then updated as new bugs are found. That way we have a "rolling" update of any outstanding issues with current releases.

Does that make sense?

@jheretic
Copy link
Member

I'm marking this as purely a documentation issue in order to unblock it. If we can create a known bugs entry on the v1.0 page, we can close this out.

@critzo
Copy link

critzo commented Apr 16, 2014

Created commotion-docs issue #150.

@critzo critzo closed this as completed Apr 16, 2014
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