VLAN AP Assignment

Hi Joe,

you do not need to configure the AP to use a VLAN because you are connecting it as a ordinary network device. The assumption being you have connected the AP to a untagged port in the VLAN 22 group.

Ian

The AP I am using allows for this... wondering if that's the issue?

Hi Joe,

my apologies, I thought you were using a Sophos AP.

To make that work you would need to have the port it is connects to as tagged for each VLAN.

Ian

No reason to apologize!

So I have the port on the switch set to be Tagged for VLAN22 but for some reason the XG isn't dishing out an IP so the device ends up with a 169.54.... IP.  I'm just trying to figure out if the problem exists on the XG and if so, where.

Is the XG end also tagged, but what is the actual management interface on the AP set as? Does the XG actually see the AP?

Ian

On the AP, the mgmt VLAN is set to 1, the SSID is set to VLAN22.

On the XG:

The XG does see the AP bc if I look in the DHCP lease list, it's there.

Joe,

you need to change port 1 physical IP address from the 10.0.0.x/24 to something like 10.10.0.0/24.

Ian

OK - gimme a sec to do that.

Dumb question then, to access the XG interface, what do I need to configure to still access the XG from the 10.0.0.0/24 net?

Hi Joe,

you should be able to access the XG GUI from any of your networks, through untagged ports on your switch and they can be on VLAN 1 which is the default XG VLAN.

Ian

So I just changed Port 1 to 10.10.0.0/24 leaving the VLANs on 10.0.0.0./24 and 10.0.11.00/24.  As soon as I did that, all of the devices on my network lose connection to the internet and they fail to get a valid IP on the VLAN from DHCP.