I understand the point about the B2 being a passive to some extent but that is not true for any device on a network.
The B2 does not initiate application level requests. DHCP and NTP (Network Time Protocol) are exceptions. There might be other Linux things too.
The point of this post is to show that both sides are active and equal partners from a network perspective in ANY communication. The B2 plays an active role in answering the requests.
OSI model
The WiFi is layers 1 to 3 and defines how data is passed machine to machine. Level 3 is where the B2 decides to use WiFi or ethernet. This is why you only want one of them connected at any point in time. It gets confusing when I have two pipes that go to exactly the same place, which one do I use? Most hosts/end user devices in your home have only one way to pass data. Though your phone could use cell signals or WiFi.
Layer 4 is how TCP/IP works and requires communications both ways (transmit and wait for receipt OR receive and send receipt). Blocks of data are numbered sequentially and if a block is missed, the receiver will ask for it to be retransmitted. Don't confuse the block size with the ethernet or WiFi packet size, they differ.
Layer 5 is the operating system keeping the connection alive for you. It does timeout if you don't do this. The operating system makes it so your application does not have to worry about it.
Layer 6 is mostly operating system where some error checking and encryption/decryption can take place. Remember that SSID password? This level will pass the data to your application.
Layer 7 - This is where the program (software written by Brennan, NAS, DHCP, HTTP, SSH, etc) uses the data.
All data passes between the end user device (hosts) to the router, router to router (if required, always for internet data), then the last router talks to the other end host. Sometimes like a home network there is no router to router connection required for internal (SONOS to B2) data.
Why do I say this? In order for any device to work it must receive and transmit without errors. In order for a SONOS to talk to a B2, the link between SONOS and the router might be great but if the connection from the router to the B2 is not working, SONOS can't work. The opposite is also true.
From a network perspective both devices are active and must be. Even at layer 7, the B2 sets it up to receive messages by making specific "listen" commands to TCP/IP. That allows someone wants to talk to it. It will then reply using the network.
I do understand that the B2 does not initiate communications but it does take an active role.