>>> supply its own hostname for vis in my opinion. I think one possibility >>> to add this without breaking compatiblity would be adding a hostname >>> record after the neighbor entries in the vis packets. >> >> Flooding the network with arbitrary data like hostnames, service >> announcements, weather info, etc comes up from time to time but it often >> boils >> down to the question: Why does it have to be in the kernel ? There are >> several >> ways to implement this feature in user space today without changing the >> kernel >> code. >> >> Regards, >> Marek > > I see your point, but then one could also ask why the visualization has > to be in the kernel at all...
visualization just means collecting information batman is already handling. neighbour information is essential to normal working, and generating a "vd dot" just exports that info. hostnames, (ip addresses, etc) on the other hand, are not of interest to current code That said, I would also love to find a solution to this, since maintaining the /etc/bat-hosts in the nodes simply doesn't escalate in my opinion, and Marek' suggestion about "several ways to implement this feature in user space today" is not entirely clear to me: mDNS solutions like avahi translate between hostnames and ips, while batman visualization deals with MACs, and those cannot necessarily be obtained from IPs (in some cases, ARP will help, but won't work in interfaces without IPs) maybe i'm ignoring some MAC discovery protocol? Cheers, Guido
