I read the article, I mean how they decided to stimulate brain activity for making a choice by.. choosing colored balloons?
And they were surprised the subjects brains responded almost exactly the same? That means.. nothing. Everything that comes after is speculation and pseudoscience.
Thanks, that's a great write up. One thing I didn't ubderstand however is in your Docker macvlan, you set the parent to br0.10 and br0.20, where are those parents defined?
Maybe I misunderstood the macvlan documents but what I did was defining a vlan in server netplan vlan0.100 and set the macvlan parent to that vlan0.100. Is that not how it's supposed to be?
I will post it when I get my hands on it, but basically I made a macvlan which is using the server vlan, and then in the compose I set the network to that macvlan, which seems to be functional at least
That is my gut feeling too, but as I mentioned in another comment all physical devices work fine in their respective subnet. This is happening before I move the containers to a new subnet, and before these changes everything was working fine.
They released the vulnerability without disclosing it to the vendors first? Am I understanding this right?