Hello everyone i want to thank everyone for being so helpful. I know I've spent many hours searching the this helpful forum getting my equipment setup.
The issue i am having is that i have setup several Vlans and now would like my Grandstream GWN7665 AP to broadcast 3 different SSIDs which have their own VLAN. VLAN100, 200, and 300 respectively. At this point I have only tried to get VLAN 100 to work with no success. A wireless client will not connect to the AP with a VLAN of 100. If i change the SSID's VLAN to the management VLAN of 99 the wireless clients connects, gets a IP address, and will have access to the internet. Is something in my configuration of the router or switch not letting the wireless client get an IP address?
VLANS
99-management 192.168.99.0/24
100-Home (for all other trusted devices) 192.168.10.0/24
200-IOT 192.168.20.0/24
300-Guest 192.168.30.0/24
400-IP_Cameras (unused) 192.168.40.0/24
500-Server (unused) 192.168.50.0/24
Currently i have an my old router providing the internet connection to my Mikrotik router on port 7. The old router has a route for the Management and Home VLAN to the mikrotik for internet connectivity. This is temporary until i have the AP setup figured out. The SPF port is the trunk that provides connectivity to the mikrotik switch. The switch is the connected to the AP's on ether 24, 23, 22, and 21. My PC is currently connected on ether 20.
switchconfig.rsc (3.9 KB)
routerconfig.rsc (5.2 KB)
If any other information is needed to help please let me know.
I haven't looked through the configs in detail, but at least part of the problem I think is down to this section in your switchconfig.rsc:
/interface bridge vlan
add bridge=Switch_Bridge comment=WLAN tagged=\
Switch_Bridge,ether24,sfp-sfpplus1 untagged=ether21,ether22,ether23 \
vlan-ids=100,200,300
There's a specific warning in the RouterOS manuals about this type of misconfiguration:
danger
The vlan-ids parameter can specify a set or range of VLANs, but this should only be used for tagged ports configurations. When multiple VLANs are specified for access ports configurations, tagged packets may be sent as untagged packets through the wrong access port, regardless of the PVID value.
[from Bridging and Switching | RouterOS Manual ]
You should only set the tagged vlan-ids in this manner; the untagged will be automatically added to the Bridge VLAN Table by the assignment of a pvid in the bridge port setting.
Ok when I get home I will remove the untagged interfaces and see what that does.
I'm sure there are other stupid things I have done in the configuration trying to rectify this problem as well
Make sure to also set PVID=100 on the bridge ports the AP's are on.
If I do that won't the AP get the home VLAN? I the AP itself is currently getting an IP from the management network which is what I would like. I don't not want the management network accessible via a wireless connection
I thought that's what the AP's were on . . . (nothing else makes sense to me . . .) The key is to set the PVID to what you want them on, and those ports will present that tonthe AP's untagged. (And I don't see mention of what/if the bridge runs untagged)
VampireTap
I have deleted the untagged ports on both the switch and router and that didnt change anything.
tadawson
I changed the pvid on ether 24 to 100 and can see that the AP gets a IP in the correct VLAN. When i try to connect with a wireless device to SSID that is assigned VLAN 100 its like it cant see the DHCP server. It gets an IP of 169.254.32.202 subnet 255.255.0.0 and no gateway address. I will try and remake my DHCP servers and see if that helps.
169.* . . . That's not a DHCP assignment - that's Whinders crap.
You do have a DHCP server assigned to that VLAN, right? And with a suitable IP block? What if you connect your PC to the physical port the AP is on - does it get an address? And what if you put an appropriate static address on the wireless client?
And, are you running the AP as an actual AP, or as a NAT device (Router)? If the latter, it won't pass DHCP through . . . If it has both a WAN port as well as other ports, try connecting via something OTHER than the WAN port, since on most, that makes it a router, notman actual AP.
It looks like it is working for now. First, A few of the DHCP servers were not configured correctly since i didnt use the wizard for them. Second I deleted the untagged ports in the bridge VLAN. Third and I'm not sure if this is correct or not but it seems like the only way i can get it to work is to change the port configuration to allow all frame types on the AP ports.
Now the physical AP gets an Ip from the management DHCP. While the SSID get an IP from their tagged VLAN DHCP.
Please share latest config to get some help.