Messages

So I am running opnsense and for some reason can't get airvpn to tell me I have properly opened my port for qbitorrent. I've successfully done so with mullvad in the past, but that was also with another torrent program I think. I'm using the same port as recommended for qbitorrent though opnsense into airvpn. The only hiccup might be that I have my torrent client on a separate vlan. I seem to recall opnsense having an issue with the rules for port forwarding not properly generating when adding a port forward to a non-lan interface.

Anyone know anything?

Thanks!

So it was something with adguard home dns. I killed that and just added google dns servers to the DHCP interfaces and it worked. Still strange that it worked for a VM on the same subnet via proxmox but not machines networked through the same managed switch on the same VLAN...

Port forwards are for adguard home that I have set up.

I have the outbound NAT. A proxmox VM on the vlan CAN get internet access, but I just tried tagging an ethernet connection at my managed switch and it was able to get a DHCP assignment from the vlan but didn't get internet access.

So what might be different about a VM VLAN tag and a physical ethernet connection tagged with the same VLAN?

So I'm scratching my head about this one:

I have a few vlans and they work fine with my ethernet connected machines. I can't seem to get internet connectivity through my Unifi AP on the exact same vlans! I've checked rules and dns and all those gotcha places. I'm running adguard home on opnsense and so unbound dns is pointed to that for DNS. My phone when connected to these vlans on wifi shows up in DHCP leases, so it's getting an ip address from opnsense. But it still doesn't get out to the open internet.

Wifi and hardwire works perfectly on the regular lan, it's the vlans that seem to have this issue.

Any ideas?

So I have a truenas VM installed on proxmox in a separate vlan from my other devices.

This is an IP range of 192.168.3.1

I have adguard home set up as a DNS filter on my router.

Now, I'm able to ping 8.8.8.8 on truenas, but cannot ping google.com or anything else.

My other VM's on the same subnet are able to access the internet perfectly fine.

I've tried any permutation of the network settings I can think of, putting my actual router ip address in for the default gateway and dns, as well as 192.168.3.1 (the subnet version). This all seems fine with the ubuntu VM I have on the same network. But nothing for the truenas install. I also saw I was adding the default dns of my router outside the subnet in my DHCP settings, I changed that to 192.168.3.1 since I got some message about an unexpected dns result when I used the dig command with google.com. Dunno if that did anything or not. I see the requests for dns coming from truenas in the adguard home logs. But I guess it's not responding maybe?

Anyone got any ideas? Thanks!


Edit: Randomly started working properly. But now I'm getting no network connection on an ubuntu vm...  ::)