[Solved] Issues communicating on VLANs with Firewalla Gold
Hi,
I purchased a TP-Link SG1016PE switch (hardware version 3.20). Updated to latest firmware.
I spent the weekend configuring VLANs on the Firewalla and switch. Had some issues, so I rolled everything back to unmanaged VLAN1 and deleted the VLANs on Firewalla.
For my testing, I had untagged VLAN1 which is my default from before, 192.168.1.0/24 (connect to port 1 on the Firewalla)
I created an additional VLAN2 tagged, 192.168.2.0/24 and (connected to port 2 of the Firewalla).
I picked a port of a device (Nvidia shield in this instance) that I could test on, and tagged it to VLAN2, and removed it's membership from any other VLANs. I rebooted the device, and even unplugged/plugged back in the ethernet cable. The device was unable to get an IP address. I even tried setting a static IP address and it could not communicate on the network.
Any suggestions what's going wrong?
edit: adding configs. note, the end device is connected to port 7 on the switch. the firewalla is connect from its port 1 to port 16 on the switch
LAN1:
VLAN2:
Switch
VLAN1
VLAN2
-
Hi @Joshua, Have you set your PVID correctly? Have a look at the TP-Link documentation.
https://www.manua.ls/tp-link/tl-sg1016pe/manual?p=42 -
Hi,
Yes, I made the VLAN a trunk (tagged port) on the Firewalla port.
I made the end device an access port (untagged) on the same VLAN as the trunk port I tagged.
The end device was unable to get an IP address. I also tried giving it a static IP and it still couldn't communicate on the network.
I created another VLAN for my docker server which is trunk as the docker tags the VLAN for the server, and it was able to get an IP address fine.
For some reason the untagged network was not able communicate on the newly created VLAN.
Please sign in to leave a comment.
Comments
7 comments