I have not tested that deeply but some people told me that their
computer (HNA) is missing on the graf...

2011/7/12 Linus Lüssing <[email protected]>:
> On Wed, Jul 06, 2011 at 12:27:28AM +0200, Sven Eckelmann wrote:
>> On Tuesday 05 July 2011 23:29:07 Gioacchino Mazzurco wrote:
>> > Good job, but what we are trying to fix is the topology visualization
>> > we need that at moment
>>
>> Just looked with one eye at the stuff and it seems that the data which comes
>> from the kernel module is not what you expect. For example 00:15:6d:fc:72:0b
>> isn't marked as primary or secondary.
>
> We don't mark secondary interfaces explicitly in the raw output, a
> raw row output of a primary interface contains all the
> information, both that it is a primary interface and also
> optionally which other secondary interfaces belong to it.
>
> Gioacchino:
> Are the interfaces 00:15:6d:fc:72:0b, 06:15:6d:7c:09:d8 and
> 06:15:6d:fc:71:ce primary or secondary ones?
> (a primary one is the one listed in the first line of 'batctl o',
> the MainIf)
>
> And those are actually the specific ones where no
> subgraph-dot-thingy has been added and no box was drawn and where
> the error lies, right? Or are there more issues we missed so far
> (like links, HNA entries or interfaces missing completely in the list and/or
> graph for instance)?
>
>>
>> It looks like one vis_if_list
>>
>> So you can't use the module from 2.6.38 and expect that we fix it with 
>> batctl.
>> And the correct people to ask here are:
>>  * Simon Wunderlich (author of the vis stuff)
>>  * Linus Luessing (the person which added the subgraph stuff)
>>  * Andrew Lunn (he introduced the format "vis raw" which is used in vis_data)
>>
>> I don't want to touch it because it may explode in my hand. But you can also
>> try whether you are lucky and check vis_seq_print_text. It is currently 
>> overly
>> complex without any reason. It could easily use seq_file and don't do the
>> precalculation (which was necessary in /sys).... I forgot the topic.
>>
>> Kind regards,
>>       Sven
>

Reply via email to