netdiff doesn't work with b6m-jsonp

[sycophantic]

The recent addition for bmx6 parsing is using the old output, so it doesn't work with newer versions of bmx6.

Here is the output from b6m-jsonp: http://pastebin.com/KmfGnTs7

[gabri94]

Probably a NetJson output will be implemented directly in BMX6, let's wait for some updates. Otherwise i'll implement the new parser

[nemesifier]

Thanks for reporting @sycophantic.
@gabri94 having netjson support directly in bmx would be great. Remember that parsing stuff from existing infrastructure is easier than asking them to upgrade.

[alfinal]

@sycophantic : is not using the old output, is using the only JSON output that currently works, you can get that output in your new BMX6 from http://yourip/cgi-bin/luci/qmp/Mesh/topology and parse it.

If @sim6 develop it in next days you'll get a more complete JSON.

[sycophantic]

I was using the output from /cgi-bin/b6m-jsonp which doesn't require a luci login. The luci topology export appears to work for me.

[nemesifier]

I'm looking forward to see the BMX links in the nodeshot test instance! https://46.101.190.150/

[gabri94]

@sycophantic The problem of the b6m-jsonp output is that the nodes are not in a list of dictionaries. they are all in a single dictionary where each node is an attribute with the node name as key.
I don't really know how to parse it.

@nemesisdesign We are waiting for the implementation of netdiff in nodeshot!

[alfinal]

@sycophantic if you want to get JSON from http use curl -d "username=root&password=passwordf&submit=Login" --dump-header headers http://yourip/cgi-bin/luci/qmp/Mesh/topology and if you want updates put it in cron. That's a trick... we're waiting @sim6 answer or maybe we're going to try to fix and/or parse b6m-jsonp.

[sycophantic]

That will work for me for now. Gives me the data to create a graph.

[nemesifier]

Does this mean we don't have a issue anymore?

[sycophantic]

It can be closed.

[alfinal]

"netdiff doesn't worth with BMX6-0.1-alpha" rename to "netdiff doesn't work with b6m-jsonp" but it could be a b6m issue https://gitlab.com/b6m/b6m if it is accepted by b6m developer...

[nemesifier]

thanks @alfinal, renamed the issue