You can run a packet capture directly from the Meraki Dashboard.
Use this filter:
host 192.168.10.5 and host 192.168.20.5
Unfortunately, the MX doesn’t expose detailed flow/session tables like traditional firewalls, but you can use Security & SD-WAN > Security Center to show top clients, applications, and threats. It’s not granular by flow, but it does provide visibility into traffic patterns.
You can also use Network > Clients and filter by IP or MAC to see recent traffic, application usage, and destination IPs.
For me, Packet Capture is the best tool for real-time, low-level visibility because it can be run on MXs, switches, or APs and supports filters and live viewing.
As a best practice, you can do a ping test from a client or by using Dashboard > Tools > Ping on the MX. Run a Packet Capture, check Firewall Rules, use the client page to verify that both devices are visible and active, and use the client's traceroute or MX tools to view the path.
If you are not using a syslog server, consider enabling webhooks or API polling to log events externally for future analysis.
I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.
Please, if this post was useful, leave your kudos and mark it as solved.