1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Rv082 + sge2010p + wap4410n

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by gijs73, Jul 6, 2011.

  1. gijs73

    gijs73 LI Guru Member

    Hey,

    I'm trying to set up a simple network but the RV082 seems to stop me from doing what I want.

    I'm using 2 different VLANs in this setup, 1 and 2. The wireless access points are configured to have 2 WLANs, a "normal" (VLAN 1 untagged) and a Guest WLAN (VLAN 2 tagged), the ports on the SGE2010P connected to the access points are in VLAN 1U and 2T, the RV082 is connected by two wires, one in VLAN 1U and the other one in VLAN 2U. Sadly, only the normal WLAN can access the router and the internet. I can not ping the router from the Guest WLAN, but Guest client can ping each other. If I connect any other wired client to the switch in VLAN 2U I can ping them also. It doesn't matter whether I put the second wire in VLAN2 on the router side or VLAN1... I can't connect to the router or the internet from the Guest WLAN.

    Any ideas on why that might be the case?
     
  2. gijs73

    gijs73 LI Guru Member

    Okay, I just connected a device directly to the router VLAN2 port and everything worked, so somehow this must be related so switch configuration...
     
  3. elzix

    elzix Network Guru Member

    I will try to test it and follow up soon.
     
  4. Sfor

    Sfor Network Guru Member

    The RV082 does not support tagged 802.1q standard VLAN. All it can do is to use port based VLAN. So, RV082 VLAN will not work correctly with devices using tagged VLAN feature.
     
  5. gijs73

    gijs73 LI Guru Member

    Are you saying the RV082 is dropping/ignoring the packets because they are tagged? Because this seems to be the only explanation for me at the moment...
     
  6. Sfor

    Sfor Network Guru Member

    That's right. The packets have to be untagged, for RV082 to process them. I do not know if it will forward tagged packets to other LAN ports, but it should to.
     

Share This Page