Getting started - WAN Internet Connectivity Issues

[CursedGravity]

I deployed the latest version of OPNSense to a box.  It is a simple setup so far.  There is a wan and a lan.  The WAN was able to pull a public IP address.  But from the OPNSense box, ping does not seem to work.  I attempt to ping in the web ui and in the terminal, and it fails.  When I look in the packet capture, I see a echo reply.  I've attached my WAN firewall rules. 
https://ibb.co/sgSwZc1

[cookiemonster]

Pinging from the OPN shell and UI to where please? The default rules will allow you to ping from it to clients on LAN. Maybe the client hasn't got an IP from OPN yet?

[CursedGravity]

From the device, I attempt to ping the ISP GW as well as a public DNS server's IP. 

[cookiemonster]

putting aside the apparent ping failure,do you have a working setup ? Some destinations disable ping although public dns servers normally don't.

[CursedGravity]

I am able to confirm that 9.9.9.9 does respond to ping from a working computer.
Please define "working setup"?  I am not actively using it, because the clients have no connectivity, but that's another issue, and I want to be able to resolve the issue with the OPNSense device not able to connect out onto the internet.

[cookiemonster]

I am assuming you can tell us that. There are so many things a router/firewall like OPN can do but nobody needs to use them all.
So as a basis and assuming this is a residential setup, I'm referring to having your LAN clients being able to get out to the internet browsing public websites.
If you can, then a spurious ping can be a nothing or all sign.
It's quite hard to tell the level of networking understanding from people on forums. I have someone at home that will just tell "the internet is down" or at work who would say "there's no connectivity". This last one is a bugbear, mostly from developers/testers that should know better. Once you start asking for what they can/not do, you realise it could be DNS problem, a DHCP problem, etc.
Long way to say, have you set everying up as per docs., have clients getting an ip address and dns server setup on OPN & clients getting those settings.
Chances are when all this is working, you can move to understanding what's happening with this ping thing.

[CursedGravity]

I've been using pfsense up until now.  I would say I'm pretty knowledgeable, including dhcp, dns, and ports, as well as firewall rules. 
Yes, this is a residential setup.
Let me know if there are any other screenshots of settings you'd like to see. 

[cookiemonster]

for now just describe your overall network setup and what diagnostic have you done, what works ?
Very broad request, right ? We need to narrow down what is the problem. Give us a sense of things.

[CursedGravity]

I'm not sure what else to describe.  I think ping is one of the most basic tests.  If I can't get out/ping, then it's not worth it to go any further.

[passeri]

for now just describe your overall network setup and what diagnostic have you done.

I think ping is one of the most basic tests.  If I can't get out/ping, then it's not worth it to go any further.

As an "overall network setup", that 'description' is somewhat incomplete. Instead, you provide a single symptom:
"Doc, it hurts.
"Where does it hurt?"
"It hurts".

I notice that your original firewall rules link is also now defunct.

Your problem will be solvable. The basic information requested is needed to do so.

[CursedGravity]

Internet -> Modem -> opnsense box -> switch -> end client machine.

[passeri]

Thank you. Your description gleaned from posts is:

Opnsense gets a public IP (modem is invisible, does not translate IP).
You can ping 9.9.9.9 from a computer but not from Opnsense
When you ping from Opnsense you get an echo packet, but no display?
No statement on whether a client computer can access the internet, aside from that earlier comment about successful ping.

There seem to be some inconsistencies there, or a need for clarification of the statements (contexts).

Is your Opnsense bare silicon or in a VM?

What is the form of your internet connection please? Does Opnsense replace another box or did your modem formerly carry routing?

I am not expert in Opnsense but my configuration looks like yours except that I have FTTP, no modem. I have no special setup yet from Opnsense I can ping things freely should the mood take me, out of the box. The issue is to track down what is different.

[CursedGravity]

I pinged 9.9.9.9 from my phone, connected to a cell tower, to confirm that it responds to ping.  That was not a client on my network.
I get no response.  But when I do packet capture, I see echo replies.
Client computers can not access the internet.  My opnsense box also has issues (ie checking for updates, fails).  Something like name resolution.
My box is an old desktop.
It is a placeholder for my current pfsense box.  I didn't wanna wipe my pfsense box till I was 100% sure I got the config right, and secured.
I will post the firewall rules for lan and wan.
https://ibb.co/kMfYcs5
https://ibb.co/rMMqzhR

[cookiemonster]

my guess from the thread is that the installation is either a VM alongside another of pfsense or another installation or as described "another box", that said "box" is downstream from pfsense i.e. the current firewall. Therefore the WAN ip is a private one in the LAN range of the clients. If this is the case, then the required adjustments for a "router behind a router" are missing.

[CursedGravity]

No, opnsense box has replaced the pfsense device.  I switch between the devices until I can get this working.