Issues with VLAN configuration between Watchguard and Brocade networks
Issues with VLAN configuration between Watchguard and Brocade networks
Hello, it seems you're having trouble connecting to your VLANs and obtaining a DHCP lease. I've included your configuration files for both Watchguard and Brocade. Note that VLAN 1/5 aren't being used. Let me know if you need further assistance.
Sharing this with someone familiar about Watchguard gear. I’m new to configuring VLANs on devices other than the Unifi hardware.
My connection to the Watchguard uses port 1/1/1. Ports from 1/1/1 to 24 belong to VLAN 110. 1/1/1 operates in Dual Mod. Ports from 1/1/25 to 1/1/44 are assigned VLAN 120. After that, 1/1/45 to 1/1/48 are set to VLAN 100.
Attaching a device to port 1/1/45 prevents you from obtaining a lease. You can still access the gateway by statically assigning it within the 10.1.48.0/24 range. Note, I'm not very familiar with Dual mode—I think this is similar to a standard trunk/native setup.
On the watchguard interface VLAN configuration, remove VLAN 1. This setting prevents using VLAN 1 for tagged traffic, which is typically the default on most devices. While you can enable VLAN 1 on a VLAN interface, it’s usually not tagged, so the action you took is appropriate. To assign VLAN 1 as untagged, access the separate option labeled “Send and receive untagged traffic...” at the bottom of the interface window.
Dual mode is a feature exclusive to Brocade. It combines tagged and untagged data simultaneously. The port can handle traffic already marked as 110, and it will also transform untagged incoming traffic into 110.