You can say "I did everything right" but if you did, it would work.
Pictures are too large to see the whole thing but vlan 1 should be excluded on port 4, not tagged.Shouldn't cause any problems but not needed.
You say you have dhcp enabled but your picture says you have the pc set statically, which is it?If static, make sure the gateway is set correctly.
Do a packet capture on the vlan interface, do you see anything from the pc's IP?
ipconfg /release && ipconfig /renew
You need to apply the tag on port 48 ( trunk ) for all vlansPort 48 Tagged for vlan 1Port 48 tagged for Vlan 15Port 4 on vlan 15 un-tagged & exclided.Should fix it.
You don't want vlan1 Tagged as you found out already.The config's look good, are you sure there's nothing else configured on port 4 that may be interfering?Maybe add another port to vlan15 and try that.The packet capture doesn't show anything from vlan15 but it's just a small picture of it, did you see any 15 traffic?
Doubting it's a problem with opnsense, more likely something on the switch.That said, are you sure you applied all settings in opnsense?You can't just click save, after that a button appears at the top of the page to "apply settings".You didn't post pictures of the whole page so no way of knowing if they were applied but that was an issue with someone else not too long ago on here. If you see the "apply" button on any page, you didn't apply.
Other thing you can do, if you have a pc that can be tagged with a vlan, tag it with 15, plug directly into opnsense and you should get connectivity on vlan15. All intel nics support vlans if you install their Proset drivers.If you try that and it fails, it's a problem with the opnsense config for sure.
As for my motherboard, its an ASRock Rack D1541D4U-2T8R (https://www.asrockrack.com/general/productdetail.asp?Model=D1541D4U-2T8R#Specifications) with 2x Intel(R) 10GbE Network Adapters.
Wait a second, your pc should be receiving untagged traffic, you can't just statically set the ip and it will work with the traffic, the pc's is not looking at Tagged traffic, unless you tell it to look at that.
If you plug your pc into the port #4 and you get vlan 1 network then its not configured properly. If you want your pc' to see the tagged traffic for the other vlan you have to tell it to look at it. Follow this : http://woshub.com/configure-multiple-vlan-on-windows/
Quote from: jlab on November 11, 2022, 06:58:44 pmWait a second, your pc should be receiving untagged traffic, you can't just statically set the ip and it will work with the traffic, the pc's is not looking at Tagged traffic, unless you tell it to look at that.jlab, I'm not sure you're following the post correctly; when I'm testing with the switch, I'm trying to grab a 192.168.15.x address from VLAN 15's DHCP Server.I'm currently trying to test pinging the 192.168.15.1 gateway plugged directly into the OPNSense box's LAN NIC with the client's IP Address assigned at 192.168.15.11.Quote from: jlab on November 11, 2022, 06:58:44 pmIf you plug your pc into the port #4 and you get vlan 1 network then its not configured properly. If you want your pc' to see the tagged traffic for the other vlan you have to tell it to look at it. Follow this : http://woshub.com/configure-multiple-vlan-on-windows/Above I indicate that when I connect to Port 4 (Untagged VLAN 15 and Excluded VLAN 1), I'm pulling an APIPIA Address.