I noticed funky behavioral differences between clients connected via WiFi and clients connected view a hard wire (ethernet).

If the client is on Wired, I can access other wired clients. If the client is on WiFi, it does not even have a route to the other wired clients. I run a local server that is wired as well as several Raspberry Pis (wireless and wired).

To summarize what I've tested:

• A Wireless client can connect to a wireless Raspberry Pi
• A Wired Client can connect to a wireless Raspberry Pi
• A Wireless client cannot connect to a wired Raspberry Pi

Setup:

Windows Desktop (also happens on macOS)

Windows 10 1803

Wireless Client to Wired Server:

C:\Users\nate>tracert 192.168.7.16

Tracing route to 192.168.7.16 over a maximum of 30 hops

  1  Chouji [192.168.7.96]  reports: Destination host unreachable.

Trace complete.

Wired Client to Wired Server:

C:\Users\nate>tracert 192.168.7.16

Tracing route to 192.168.7.16 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.7.16

Trace complete.

The test for tracerts were done on the same box (A Windows machine with both Wired and Wireless available).