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
0.13.0 and 0.14.1 not interworking #10
Comments
Is there any other debug info helpful for this thing being improved/fixed? |
Unfortunately I have yet to find time to look into this... one of the major issues fixed with 0.14 was a bug in the packet generator... I am not sure this is related, but I would advise not to stay on 0.13.x because its defective. |
I suppose this is fixed as of 0.14.1-16 |
I will tag a new version on Sunday. |
HRogge
added a commit
that referenced
this issue
Jul 6, 2018
…net-command-to-manipulate-layer2-data to develop * commit 'c33d680ed56e3cecfd2fd85e3869448acb773bb8': Add LID capability to oonf_layer2 and l2config subsystem
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm running several nodes with version v0.13.0-30-g34afbf3 and wanted to upgrade to v0.14.1-g46d80a9.
Unfortunatelly, the nodes on version v0.13.0 do not forward the broadcast of v0.14.1.
v0.13-Nodes see the upgraded node on the table "olsrv2info-node" with negative node_vtime and node_virtual=true
One of the nodes running v0.13.0-30-g34afbf3:
2a02:61:0:ff:822a:a8ff:fe5d:fa9e, 78.41.113.166
http://78.41.113.166:8000/telnet/olsrv2info%20node
--> originator of 2a02:61:0:ff:46d9:e7ff:fe50:30e2 is shown as "virtual" with negative node_vtime
The node running v0.14.1-1-g46d80a9
2a02:61:0:ff:46d9:e7ff:fe50:30e2 78.41.113.155
http://78.41.113.155:8000/telnet/olsrv2info%20node
The text was updated successfully, but these errors were encountered: