nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

my R510 AP cannot used on the default VLAN but ok on other VLANs, how can i fix that?

unknown

Find more posts tagged with

Accepted answers

All comments

unknown

Untag the VLAN on that switch port or change the VLAN on the SSID to VLAN 1

unknown

That's most likely a switch config issue. On a trunked port, plug a laptop in. Does it work?
On a trunked port you should be able to set a default or native VLAN that is not tagged. And that is what the AP could use. Test with the laptop.

unknown

The ssid set to run on VLAN1 (default) & the switch port untagged on VLAN1, it does not work.

But change the switch port to other VLAN then it works, strange!!

unknown

If the switch interface is set to a single VLAN (access mode), then it really does not matter what VLAN is set on the port, it will be untagged. It is exactly the same for the AP.
If VLAN 1 doesn't work, but VLAN 20 does, then the VLAN1 is not setup properly on the switch, or DHCP doesn't work on it, etc. Again, test it with a laptop.

If the port is set as trunk (802.1q), then multiple VLANs are set on the interface, usually one of them as default, or untagged, usually VLAN 1. When you plug a laptop into it, the laptop will use untagged traffic, VLAN 1. If it works, then the switch is good. The AP has a setting for what VLAN to use for management and what to use for different SSIDs. The management has to be set to VLAN 1. You can verify, by plugging the AP directly into a laptop nic. If you are running Windows, turn on Internet sharing on its WIFI card. This will turn on a DHC{ server in the laptop and the AP will be offered an IP. Verify that you can reach the AP. If yes, then your AP is set correctly to use untagged traffic for management.

But from what you are saying, it looks like the switch port is set to access mode with a single VLAN on it. The AP has no way of knowing what VLAN is set on the switch interface, since the traffic is untagged.

unknown

Thx for yr reply, Victor.
I think both the switch & the specific port are functioning. I plugged in a laptop as suggested. It got an IP from VLAN1 if I configured the port on VLAN1, got IP from VLAN2 if configured as VLAN2. Internet connection works perfectly.

The AP ssid is on VLAN1, if switch port on VLAN1 it does not work, but if on VLAN2, it works!!

Then if both AP & port on VLAN2, it does not work either.

Really can't explain!!

unknown

Can we get the switch config for that port?

unknown

port 28

Image_ images_messages_5f91c44a135b77e247a081b0_ce37314a9ddcb9ea71346a6e36317445_RackMultipart201909131041891h7-1bfb181e-a3ba-4d94-9a37-91b0f7a7a9bf-627671557.jpg1568358921

Image_ images_messages_5f91c44a135b77e247a081b0_5139ed9326a782ef1122cf174d686e01_RackMultipart2019091360723loml-d6161feb-4a35-4851-ad85-bd844f72ae1a-1730075024.jpg1568358949

unknown

port 28

unknown

Great! The VLAN 2 assigned to interface 28 is not tagged. Thus it really doesn't matter what VLAN that is. There are no tags. At this point, the AP will probably work set on VLAN 1, if that's set as untagged on it. When you switch the AP to VLAN 2, it thinks it has to tag the traffic with VLAN 2... tags, or vlan-id. But the switch is only accepted untagged traffic, therefore the packets from the AP are dropped.

unknown

The AP is on VLAN1 !!!
The only combination that works is AP on VLAN1, while the port 28 on other VLAN (2,3, ..) but 1.

unknown

it works but we dont want to assign IPs under VLAN2 to the mobile devices accessing this AP. We want to assign IPs under VLAN1.