So here is a strong opinion that is weakly held. I would like for us to discuss this in detail.
I believe that auraed should only start by exposing gRPC server a unix domain socket, as well as a server bound to the special loopback interface lo man. Additionally I think auraed should reserve TCP port 57 for its default port.
- /var/aurae/aurae.sock
- 127.0.0.1
- ::1
Additional Network Devices
I believe we should be able to start auraed and pass configuration to the daemon at runtime to provision gRPC servers attached to various devices.
Some syntax such as this.
sudo -E auraed --listen="lo:127.0.0.1:57" --listen="lo:::1:57" --listen="eth0:10.0.0.100:57"
However we expose the network devices should be uniform and there should be no different between configuring a network device via the command line, or via the gRPC server APIs.
So here is a strong opinion that is weakly held. I would like for us to discuss this in detail.
I believe that
auraedshould only start by exposing gRPC server a unix domain socket, as well as a server bound to the special loopback interfaceloman. Additionally I thinkauraedshould reserve TCP port 57 for its default port.Additional Network Devices
I believe we should be able to start
auraedand pass configuration to the daemon at runtime to provision gRPC servers attached to various devices.Some syntax such as this.
However we expose the network devices should be uniform and there should be no different between configuring a network device via the command line, or via the gRPC server APIs.