Wireguard Road-Warrior setup can't ping internal networks[SOLVED]

[Tableflip]

Hello OPNsense forum,

As the title says.

Troubleshooting & Information
I can connect & also ping my Wireguard instance IP (10.10.10.1) from my client (10.10.10.2)

It seems that Im able to ping any directly connected interfaces on my OPNSense firewall, but not anything further

I've followed the Wireguard Road-warrior setup, and done all the steps important to have a running IPv4 client on Wireguard, including routing to the internet from the tunnel.

I am however able to approach the internet from my VPN tunnel, and it properly shows the Public IP of my OPNsense firewall

In the attachments is my firewall rules setup for LAN, wg0 (Wireguard interface), WAN

If there is anything i can provide information wise i'll gladly offer, im a cybersec student so some logs/commands might need an example for me to easily run.

Regardless, thank you for your time and attention to my problem ;D

28-09-2024 update: I was pinging a host that didn't exist, my setup was fine i was just being silly.....

Thank you everyone for your help who commented!

[tiermutter]

On Client side, does allowed addresses include those networks/ IPs you want to ping?

[Tableflip]

Yes, the AllowedIPs = 0.0.0.0/0

[Bob.Dig]

It seems that Im able to ping any directly connected interfaces on my OPNSense firewall, but not anything further

Windows?

[Tableflip]

Im running Fedora 40 on a framework, with networkmanager as the connection manager

[Tableflip]

Im an immense idiot.

I could ping my internal network, and any hosts within.

I was just constantly trying to ping an IP had i had previously removed from my network

thank you everyone who was willing to even lay an eye on my problem.....