Firewall – Can Firewall Block Packets Visible in Wireshark?

Your tracer is coming back with input_ifc=outside, output_ifc=outside because it has no other routing information for the destination address, and your outside_access_in ACL has hit counts of 0 on both entries; ICMP is not working, at least, not via this ACL.

Definitely need to see that NAT rule (and the associated ACL if it's a policy NAT).

Is it using a dedicated address for this, or the firewall's interface address? It's not getting this far yet, but, we'll also want to confirm that the correct routing information is there to get traffic to the post-destination address, too; this will be automatic if the server's in the same subnet as the firewall's inside interface.

The NIC cannot happily send a packet to an unassigned IP address in the same subnet, since it would have no idea what hardware address to send it to. Since the address is in the same subnet, the router is not in the way. Routers route between subnets.

Update 1: I see you're thinking that the machine is "wired directly to the router", but this is confusing terminology. Your "router" has a built-in switch in addition to a router. This machine is in fact connected to the router's switch, as is the actual part of the router that routes.

Update 2: It seems wired devices cannot communicate with wireless devices on your LAN at all, since wired devices are not getting ARP replies from wireless devices. The next step in troubleshooting is to make sure wired and wireless machines are connected to the same router and that you don't have some other device in-between them.