Hello,
I am new to DLink Smart Switches, and I have read through the manual. I'm using my switch to front a pfSense Router with three VLANS on one port:
VLAN 0 (no VLAN) - Main Office LAN
VLAN 10 - Guest network
VLAN 20 - IoT Network
The Guest and IoT network are offered only on Wi-Fi, via Unifi AP/AC Pro units. This configuration is currently working on an older pfSense box which has a built-in Marvel 4-port switch. The newer pfSense box I am now using has no such switch, hence the acquisition of the 1100-16v2,
The problem I am having is with eth1, which is configured as the trunk line that goes back to pfSense. It is configured to have VLAN1 untagged and VLANS 10 & 20 tagged. I have saved the config files as XML (and in the Web GUI before I unplug the switch to move it from my test bench to production).
Every time I unplug it, eth1 reverts to TAGGED for VLAN1, which means it no longer removes the VLAN 1 tag from outbound packets, and pfSense drops those because there is no VLAN 1. There are many devices hanging off of the Main Office LAN that do not know about VLANs, so I do not have the option of setting VLAN 1 for the Main Office LAN. FWIW, the Unifi APs also strip VLAN packets off before sending off over their radios, and add them before sending through their ethernet ports back to the switch / router.
To test that I'd saved the right config on HTTP backup, I reset eth1/VLAN1 to untagged, Saved in the GUI, exported the config via HTTP and did ran a diff on this new backup vs. the one I made just before unplugging the switch to move it to production. They are identical.
Here are some images of my configuration, with eth1 set properly:
802.1q VLANs
Management VLAN Setting
I tried setting this to ENABLED for VLAN 1, but that did not work either.VLAN 1 Details
VLAN 10 Details
VLAN 20 Details
QUESTION: What am I doing wrong; do I need to turn off the management VLAN setting; is that what is forcing eth1 to Tag VLAN 1 on rebooting?
Thanks!