Elmer
Maybe change the color of the connecting lines in the visualisation to bold-red when the traffic is not encrypted? Is this possible?
Additionally, it seems that the node (192.168.8.4 in the screenshot) is not recognised as a device at all. There is no mac address in the information, nor is it linked...
This is heavily related to #27 (i.e., this is the generalisation of #27)
We have to assess whether this is a SPIN issue, or a LEDE/OpenWRT issue. Suggestion: close if it's not our code causing this.
Seems a Valibox issue, or more likely OpenWRT. Removing Milestone.
For some reason, the reply is not shown either (i.e., only the DNS request is shown, not the reply). This is probably by design, but makes it difficult to merge...
@tjeb could the SPIN kernel module pass on information about which addresses are broadcast? Corner case: what if the netmask changes at some moment in time?
Seems to be difficult, we need more information about the network environment in order to reliably do this. Moving to SPIN 0.7.
From a client-perspective: resolving using ipv6 does not seem to work. As in: `$ dig -6 example.nl` produces a time-out only.
Something to consider: what if the user's DNS traffic is encrypted, and is not seen by SPIN. Out-of-scope, but if we implement DNS blocking, this should be made clear to...