summaryrefslogtreecommitdiffhomepage
path: root/pkg/atomicbitops
diff options
context:
space:
mode:
authorChris Kuiper <ckuiper@google.com>2019-10-03 19:30:01 -0700
committergVisor bot <gvisor-bot@google.com>2019-10-03 19:31:35 -0700
commit48745251611b5c152b1a2b66a0f2f30dd4dc1ed9 (patch)
tree38f4113e257a3b97d0d1da5ff49d25ce015f56c9 /pkg/atomicbitops
parent135aadb5179c94972504910e66e9e2540c09d489 (diff)
Implement proper local broadcast behavior
The behavior for sending and receiving local broadcast (255.255.255.255) traffic is as follows: Outgoing -------- * A broadcast packet sent on a socket that is bound to an interface goes out that interface * A broadcast packet sent on an unbound socket follows the route table to select the outgoing interface + if an explicit route entry exists for 255.255.255.255/32, use that one + else use the default route * Broadcast packets are looped back and delivered following the rules for incoming packets (see next). This is the same behavior as for multicast packets, except that it cannot be disabled via sockopt. Incoming -------- * Sockets wishing to receive broadcast packets must bind to either INADDR_ANY (0.0.0.0) or INADDR_BROADCAST (255.255.255.255). No other socket receives broadcast packets. * Broadcast packets are multiplexed to all sockets matching it. This is the same behavior as for multicast packets. * A socket can bind to 255.255.255.255:<port> and then receive its own broadcast packets sent to 255.255.255.255:<port> In addition, this change implicitly fixes an issue with multicast reception. If two sockets want to receive a given multicast stream and one is bound to ANY while the other is bound to the multicast address, only one of them will receive the traffic. PiperOrigin-RevId: 272792377
Diffstat (limited to 'pkg/atomicbitops')
0 files changed, 0 insertions, 0 deletions