Cannot communicate between hosts when VLAN tagging is enabled on WA801ND
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Cannot communicate between hosts when VLAN tagging is enabled on WA801ND
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I have a WA801ND which I am currently trying to use to present 4 individual SSIDs. I am also using the functionality to TAG traffic comming in from these SSIDs. The traffic tagging itself is working fine and at a switch and router level I can process the tags, firewall appropriately, etc. However, I'm unable to communicate between devices on the same SSID. These devices are a mixture of Linux laptops, windows laptops, android and ios phones.
As can be seen, Client Isolation is currently disabled:
As soon as VLAN tagging is disable (and all hosts are on the same flat network), clients on the same SSID are able to communicate with no issues.
I also have a TL-SG108E switch which I configure trunk ports for the wireless access point and tag other ports so that I can have physical devices on the same logical VLANs. I am able to connect to devices (ping, ssh, etc) on the VLAN segments from a wired computer on the same VLAN segment without any issues, so it seems that all of the issues
are within the way the WA801ND is configuring VLAN tagging.
Does anyone have any ideas? :)
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I am not familiar with that switch or AP, but my only suggestion is to start small and move up incrementally. Get LAN working, then add a single VLAN and get tagged traffic to work. I'd dedicate a trunk port and use all tagged traffic and, if possible, keep the LAN port separate from VLAN. Also avoid VLAN 1 as that is usually default or management and would be a common attack vector for someone.
Not super helpful here, but baby steps is how to gain understanding. I recently implemented VLAN and it took a bit to get there since terminology changes (trunk means different things between Cisco, HP, etc.) and it can be hard to interpret online advice. Once it works it's great!
- Copy Link
- Report Inappropriate Content
Hi Stan,
I'm not sure if you're karma farming (or just stealing other peoples answers) but you've very lazily lifted this answer (almost verbatim) from a thread on reddit.
Heres your answer:
Heres where you stole it from:
(thats my thread on reddit, by the way)
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2616
Replies: 12
Voters 0
No one has voted for it yet.