Home
Help
Search
Login
Register
OPNsense Forum
»
Archive
»
23.7 Legacy Series
»
Opnsense not sending packets to destination?
« previous
next »
Print
Pages: [
1
]
Author
Topic: Opnsense not sending packets to destination? (Read 519 times)
Twitchiz
Newbie
Posts: 14
Karma: 0
Opnsense not sending packets to destination?
«
on:
September 04, 2023, 02:17:38 am »
So this is a strange one to me. I have a VPS that I have multiple public IPs on. It's connected to my local opnsense with wireguard. It's used to expose certain VMs on a subnet to the internet and have a separate way out than my normal LAN. I have succeeded in routing outwards, such as updating the VMs on the network and traceroute shows it takes the correct way out, but things coming in aren't making sense. I've done tons of packet captures. My current situation is this: Pinging the front end VPS IP that is forwarded to a certain VM guest, shows with packet captures, that it makes it through the server and at the very least, to the wireguard interface on Opnsense. It shows in the firewall logs it passed the rule that allows it to come OUT of the proper interface that the VM sits on, however, the VM shows nothing ever reaching it in it's packet capture (tcpdump). Also, nothing shows on the VMs firewall denied log. The opnsense packet capture, however, only shows that the packets arrived on the WAN and Wireguard interface, but never exited the interface on which the VM sits (using HTTPS). When I ping out however, I see the reply come back on the WAN, Wireguard AND the interface on which the VM sits. Any ideas? I've beat my head against this for over 20 hours over the past few weeks and I feel like I'm really close, but not all the way there.
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
Archive
»
23.7 Legacy Series
»
Opnsense not sending packets to destination?