Check if the VLANs on the switches are configured properly.
Check if the VLANs on the switches are configured properly.
i'm dealing with this micronet switch: micronet sp6108ws. when i configure egress to be tagged for my up-link native vlan traffic, it doesn't pass. if i set egress untagged on the switch's uplink tagged traffic, it also doesn't pass. i've created a vlan (vlan 50) for my guest network. the issue seems to be whether the switch is passing vlan 50 traffic or not—otherwise, untagged traffic isn't reaching it. i've set up a pvid table like this: only vlan 50 traffic should be allowed to pass, which means port 5 should get a dhcp address and connect to the internet plus my guest network on vlan 50. however, other ports are losing access—like port 2 can only ping the switch if i manually assign an ip. if i use a pvid table that way, native vlan traffic works but vlan 50 is blocked. i've noticed something in the manual: if the table looks this way, it should behave normally. when i connect my ap directly to pfsense's lan, both guest and home wifi get ip and internet access. this suggests the problem isn't with my ap's configuration but with the switch itself. i've tested various configurations without success, so i'm confirming it's a hardware issue. thanks for the info—my lan is 192.168.0.0, vlan 50 is 192.168.50.0, and the switch ip is 192.168.0.4. ap is running openwrt on xiaomi r3.
This interface has a poor user interface. You should assign ports as needed for VLAN 50. The examples shown aren't usual behavior on switches. If a frame arrives untagged on a native VLAN, it stays untagged. This switch seems to expect all tags. - For the trunk port (Port 8), make it a tagged port with PVID 1. - Keep other ports untagged unless the AP has 802.1Q enabled. - Assign VLAN 50 and PVId 50 to all guest networks. - On PFsense, create subinterfaces for tagging; if VLAN 1 causes issues, switch PVID and VID to VLAN 10. This device is very problematic and violates IEEE standards.
this would be the second image... the issue with labeling the trunk is that native VLAN traffic isn't functioning anymore... (if you set port 8 egress to tagged none, no ports receive traffic except port5 which is on VLAN 50) which is the odd thing for me and makes me rethink everything... as I mentioned, I'm confident in pfSense and AP configuration since they connect directly, but it's puzzling... i just wanted to confirm I'm not crazy and it must be a switch problem.