Messages

I was able to fix this by:

• Switching virtual box network for the vm from NAT to Bridged
• Setting a static ip in opnsense for the new connection
• Adjusting other software to use the new ip

I have a computer 192.168.1.5 that has a virtual box VM running and inside that it has an outbound connection to a wireguard VPN. I'm seeing that the firewall is blocking all traffic thats trying to come back in over the VPN connection.

See attached for whats being blocked. The real issue is I don't know for sure what that vpn ip is going to be each time I connect.

I have also enabled the upnp plugin with no luck. It is working as I see some services have created ports in the status page.

Wow. I. Am. Dumb.

It was working the whole time and it was just chrome complaining about the self signed certificate. Once I allowed that it works fine.

I'm trying to figure out why wireguard is ok with all other ip's on my lan 192.168.1.7 for example but I cant go to 192.168.1.1 which is the router ip?

I followed this tutorial https://www.wundertech.net/how-to-set-up-wireguard-in-opnsense/ and went with a full tunnel rather than split.

I have also noticed I can't get the roku apps audio to work when connected to wireguard.

Ok so I disabled adguard but still left it as the dns server and everything works fine when trying hostname.local addresses. So now I need to find out why adguard is blocking .local

I also tried going unbound -> adguard rather than adguard -> unbound but get the same behavior.

DHCP Reservation as far as I can tell. The screenshot I have attached shows where I can see them listed out in opnsense. You can also see how the requests are coming into AdGuard.

I do have it setup with adguard as the primary dns and then its upstream is set to 192.168.1.1 so maybe the order has something to do with it?

Is there anyway to get mdns working with static ip's assigned by the opnsense dns server?

Right now mdns works fine so long as it gets its ip from the dns pool. If I assign it a static ip via opnsense it wont resolve the mdns and the network shares are all reporting as hostnamehere.local