Hi, everyone,
This may be the wrong sub-forum for this, so if it needs to be moved, I apologize. We have a mixture of 2.4 GHz and 5.8 GHz nodes set up (as we're migrating our system from the 2.4 to 5.8 band) and want to look at the routing tables. My understanding (or misunderstanding) is that in the newer releases, we're not able to view the OLSR information. And, I remember seeing that you were moving the routing system from OLSR to BATMAN. My questions are:
Has the move been made to BATMAN?
Are we able to view the routing information at all (even using SSH and something similar to route -n or other Linux commands to view the routing table)?
If we aren't able to view the OLSR Information, will that be re-implemented in some fashion?
If I'm misunderstanding this, how can we view the OLSR information on our individual nodes?
Thanks and have a great afternoon. :)
Patrick.
This may be the wrong sub-forum for this, so if it needs to be moved, I apologize. We have a mixture of 2.4 GHz and 5.8 GHz nodes set up (as we're migrating our system from the 2.4 to 5.8 band) and want to look at the routing tables. My understanding (or misunderstanding) is that in the newer releases, we're not able to view the OLSR information. And, I remember seeing that you were moving the routing system from OLSR to BATMAN. My questions are:
Has the move been made to BATMAN?
Are we able to view the routing information at all (even using SSH and something similar to route -n or other Linux commands to view the routing table)?
If we aren't able to view the OLSR Information, will that be re-implemented in some fashion?
If I'm misunderstanding this, how can we view the OLSR information on our individual nodes?
Thanks and have a great afternoon. :)
Patrick.
No info on manually reading the OLSR data.
I can tell you that a route -n does work in you are SSHed in.
Pretty much every node for the last several releases has the ability to spit out its olsr/topology in json format. You might give this a try to see if it contains the information you're interested in: http://localnode.local.mesh:9090/topology