[Interop-dev] RFC: add parameter link-type

Bastian Bittorf (spam-protected)
Thu Sep 3 11:16:26 CEST 2015


* Nemesis <(spam-protected)> [31.08.2015 09:06]:
> On 08/28/2015 02:04 PM, Bastian Bittorf wrote:
> > * Nemesis <(spam-protected)> [28.08.2015 13:49]:
> >>> this will not work, because one node can have different interfaces with
> >>> different types - how can i add that to properties?
> >> Link objects can have properties too!
> > oh - soooo easy?! thank you:
> > http://intercity-vpn.de/networks/giancarlo/meshrdf/netjson.html
> > (mixed wireless+ethernet)
> >
> > next week i will implement the subtypes. (frequency + channelwidth)
> 
> 
> Well I found out a few things to change in networkgraph to allow
> customizing colors more easily.
> 
> For the moment try this crappy hack:

ok, worked again on this issue (small net, dualradio-hardware 2.4/5 GHz mixed)
http://intercity-vpn.de/networks/giancarlo/meshrdf/netjson.html
http://intercity-vpn.de/networks/giancarlo/meshrdf/map.json

i introduced/hacked 3 new properties and modified your script:

link.carrier (e.g. ethernet|wireless)
link.frequency (e.g. 5180)
link.chanbw (e.g. 5)

now ethernet links have another color.
the next step would be:

change colors of the wireless links according to cost.
show speed of a link
show "nexthop" (but this is difficult, because the nexthop
can change when e.g. using source-specific-routing)

another thing: who feels responsible for this
javascript live-topology during battlemesh v6?
https://www.youtube.com/watch?v=MXFz6QdfgP8

bye, bastian




More information about the Interop-dev mailing list