AV2000, EAP245 and VLANs... How to?
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
AV2000, EAP245 and VLANs... How to?
Model :
Hardware Version :
Firmware Version :
ISP :
Greetings! I have an EAP245, a pair of AV2000s and a Cisco 3750 as a "Core" switch. I am trying to make a separate VLAN for my "guest" wifi. This wifi will be a separate VLAN and subnet with it's own DHCP server (hence the need for the separate VLAN). I call it a "Guest" wifi, but really it will be routed differently though a software router instead of my normal internet router.
AT&T Router -> Cisco 3750 -> AV2000 Powerline (Basement) -> AV2000 Powerline (Livingroom, negotiates at 866 Mbps per the tpPLC software) -> EAP245. AV2000 is plugged into a Trunk port on the Cisco switch. Testing proves that things are working at my VM host and switch level no problem.
I have this working in a VM as a lab (no network traffic leaving the VM Host). But I can not make this work in my home and it seems to be pointing to my AV2000 that are blocking, stripping or ignoring the VLAN tagging. My new SSID is tagged with VLAN 500 at the EAP245 while all other traffic is untagged (default VLAN 1). I can see traffic reaching my switch but it all appears to be VLAN 1. I do not see any traffic from the new VLAN. Additionally, when I connect to the new SSID that is associated with the new VLAN, I do not get an IP from either network. It all seems to point to the AV2000. I looked through documentation and cant see anything that says anything about support for (or against) VLANS or 802.1q tagging.
Has anyone tried to do this before or know more about this? I would hate to have to get a 2nd AP and bypass the AV2000 just for this guest SSID project.
Hardware Version :
Firmware Version :
ISP :
Greetings! I have an EAP245, a pair of AV2000s and a Cisco 3750 as a "Core" switch. I am trying to make a separate VLAN for my "guest" wifi. This wifi will be a separate VLAN and subnet with it's own DHCP server (hence the need for the separate VLAN). I call it a "Guest" wifi, but really it will be routed differently though a software router instead of my normal internet router.
AT&T Router -> Cisco 3750 -> AV2000 Powerline (Basement) -> AV2000 Powerline (Livingroom, negotiates at 866 Mbps per the tpPLC software) -> EAP245. AV2000 is plugged into a Trunk port on the Cisco switch. Testing proves that things are working at my VM host and switch level no problem.
I have this working in a VM as a lab (no network traffic leaving the VM Host). But I can not make this work in my home and it seems to be pointing to my AV2000 that are blocking, stripping or ignoring the VLAN tagging. My new SSID is tagged with VLAN 500 at the EAP245 while all other traffic is untagged (default VLAN 1). I can see traffic reaching my switch but it all appears to be VLAN 1. I do not see any traffic from the new VLAN. Additionally, when I connect to the new SSID that is associated with the new VLAN, I do not get an IP from either network. It all seems to point to the AV2000. I looked through documentation and cant see anything that says anything about support for (or against) VLANS or 802.1q tagging.
Has anyone tried to do this before or know more about this? I would hate to have to get a 2nd AP and bypass the AV2000 just for this guest SSID project.
