DHCP / VLAN Issues

[Demusman]

I plugged in a Windows 10 host and set the NIC to pull an address from the default LAN, that worked without issue; I was able to ping the 192.168.1.1 default gateway. When I manually set the host's IP to the 192.168.15.x subnet (192.168.15.11 in this case), I'm unable to ping the 192.168.15.1 gateway. I did run a packet capture while doing all of this and there is activity on the VLAN 1 NIC but there was no activity captured on VLAN 15.

You missed a very important part, you have to tag your pc's nic with 15 in order to plug directly into opnsense.
Without tagging it, it will only ever get your LAN traffic.

[CruseOPNsense]

You missed a very important part, you have to tag your pc's nic with 15 in order to plug directly into opnsense.
Without tagging it, it will only ever get your LAN traffic.

Pardon my ignorance, but does manually setting an IP under the 192.168.15.x subnet count as 'tagging' the NIC? If you can provide a guide or an explanation on how to do that with a Windows 10 machine, that would be greatly appreciated. I'm trying to search "Windows 10 NIC Tagging" but I'm not finding what you're referring to.

[Demusman]

No, that's just setting an IP address, has nothing to do with a vlan.

What kind of nic is in the pc?
As I said earlier, if it's an intel nic, download their ProSet driver. It allows tagging.
If it's not an intel, you'll have to find out from the manufacturer.

Go into the nic's properties, then click configure.
Do you see a vlan tab?

[vico1959]

So Demusman is correct, you have to tag the traffic from your NIC in order to access that VLAN 15 network and hence reach the DHCP server and receive an address. As stated, this can be tricky at the PC. It is usually done in the switch as you have done already.

I would venture a guess that you might be having some blockages with the DHCP server being trusted and passing through in the switch or the DHCP firewall rules in the OPNsense. I did not research your switch directly but I have dealt with these kinds of issues with some TP-Link switches in the past where the DHCP server for the VLAN was not configured as trusted in the switch and it was blocking it. Look into this and see if that could be your issue.

[jlab]

No, that's just setting an IP address, has nothing to do with a vlan.

What kind of nic is in the pc?
As I said earlier, if it's an intel nic, download their ProSet driver. It allows tagging.
If it's not an intel, you'll have to find out from the manufacturer.

Go into the nic's properties, then click configure.
Do you see a vlan tab?

Thats why i posted the link in the post 2 before this he has to tell the pc to look at vlan tag He he !