RV130W no WAN connectivity for all Wifi clients (Neither internal nor external AP's)

[zk1234567]

RV130W configuration summary:

• VLAN1 (managment vlan 192.168.1.0/24) / DHCP: enabled / DNS: resolving that of ISP / mapped to SSID "billy" with WPA2 encryption
• VLAN3 (guest vlan 192.168.2.0/24 / DHCP: enabled / DNS: resolving that of ISP / mapped to SSID "Guest" with WPA2 encryption. 

Inter-VLAN routing: Enabled

Wired LAN working flawless on all clients. Yet....

ALL attempts to connect to a WAN IP (loading a website... etc...) for a Wifi client, I don't get any respons. 

That is: both the internal AP of the router as the WAP121 on the other side of the hallway connected trough an unmanaged SG100D-08 switch (no PoE)

I've tried static DNS server settings on both LAN an WAN... no change. I have the exact same configuration on a RV130 (without internal AP) and third party AP's on another location: Everything working flawless.

I've also tried different SSID's for the different AP's... same issue.

The only thing I could think of is a glitch in my routing table? But at this moment I'm starting to vote for a cisco firmware issue... since my problem is pretty similar as described in this threat: https://supportforums.cisco.com/discussion/11629371/rv220w-not-passing-dhcp-wireless-clients and the problem does not occur when I reboot the router and connect a device to one of the SSID's the first time I can get back websites, etc... (I had that same result with a Galaxy, an iMac and an iPhone) But when I switch SSID's... WAN connectivity is lost. Also when I connect back to this first SSID... no WAN connectivity.

Any suggestions? Many thanks in advance!

[cole.grim]

It sounds like you've done quite a bit of troubleshooting relating to DNS. Have you tried doing a ping/traceroute from one of the non-working wireless clients directly to an outside IP address (e.g. 4.2.2.2) and seeing if it makes it through the RV130? That could help narrow it down between DNS and some other issue. If the ping/traceroute doesn't go through the device, then it's probably something bigger.

The fact that it works the first time after restart, but not others makes me wonder if it's something related to NAT. 

In Networking > Routing, do you have it configured to Gateway or Router?

[zk1234567]

Dear cole.grim thank you for your reply.

Here a sequence of a few traceroutes you requested:

1 -- Connected over Ethernet Cable (Internet is working!) --

MacBook-Pro:~ billy$ traceroute 4.2.2.2

traceroute to 4.2.2.2 (4.2.2.2), 64 hops max, 52 byte packets

 1  192.168.1.1 (192.168.1.1)  0.681 ms  0.450 ms  0.329 ms

 2  10.239.0.1 (10.239.0.1)  6.036 ms  6.133 ms  6.139 ms

 3  weer-rc0002-cr101-xe-2-0-3-0.core.as9143.net (213.51.187.52)  6.847 ms  8.234 ms  7.952 ms

 4  asd-tr0042-cr101-ae4-0.core.as9143.net (213.51.160.214)  11.705 ms  51.198 ms  12.262 ms

 5  * lag-19.ear2.amsterdam1.level3.net (212.72.42.245)  14.352 ms  16.816 ms

 6  ae-4-90.edge6.frankfurt1.level3.net (4.69.154.202)  18.014 ms *  19.008 ms

 7  ae-4-90.edge6.frankfurt1.level3.net (4.69.154.202)  18.984 ms *

    ae-3-80.edge6.frankfurt1.level3.net (4.69.154.138)  17.556 ms

 8  b.resolvers.level3.net (4.2.2.2)  18.142 ms  18.378 ms  17.901 ms

2 -- Connected over Wifi / SSID: billy1 / VLAN1 / Internal AP / Channel 1 (Internet is working!) --

MacBook-Pro:~ billy$ traceroute 4.2.2.2

traceroute to 4.2.2.2 (4.2.2.2), 64 hops max, 52 byte packets

 1  192.168.1.1 (192.168.1.1)  3.852 ms  1.512 ms  1.318 ms

 2  10.239.0.1 (10.239.0.1)  11.498 ms  8.229 ms  11.886 ms

 3  weer-rc0002-cr101-xe-2-0-3-0.core.as9143.net (213.51.187.52)  9.285 ms  12.395 ms  8.455 ms

 4  asd-tr0042-cr101-ae4-0.core.as9143.net (213.51.160.214)  12.620 ms  39.976 ms  12.569 ms

 5  * lag-19.ear2.amsterdam1.level3.net (212.72.42.245)  126.050 ms *

 6  ae-2-70.edge6.frankfurt1.level3.net (4.69.154.74)  19.322 ms *  20.759 ms

 7  ae-2-70.edge6.frankfurt1.level3.net (4.69.154.74)  19.017 ms

    ae-3-80.edge6.frankfurt1.level3.net (4.69.154.138)  19.488 ms *

 8  b.resolvers.level3.net (4.2.2.2)  82.515 ms  22.481 ms  19.811 ms

3 -- Connected over Wifi / SSID: billy2 / VLAN1 / WAP121 / Channel 6 (Internet is NOT working!) --

MacBook-Pro:~ billy$ traceroute 4.2.2.2

traceroute to 4.2.2.2 (4.2.2.2), 64 hops max, 52 byte packets

 1  192.168.1.1 (192.168.1.1)  1.367 ms  1.386 ms  1.263 ms

 2  10.239.0.1 (10.239.0.1)  7.719 ms  8.504 ms  6.616 ms

 3  weer-rc0002-cr101-xe-2-0-3-0.core.as9143.net (213.51.187.52)  13.480 ms  12.834 ms  7.752 ms

 4  asd-tr0042-cr101-ae4-0.core.as9143.net (213.51.160.214)  15.753 ms  12.658 ms  10.541 ms

 5  lag-19.ear2.amsterdam1.level3.net (212.72.42.245)  21.088 ms  12.972 ms  13.155 ms

 6  ae-1-60.edge6.frankfurt1.level3.net (4.69.154.10)  24.156 ms  20.313 ms

    ae-4-90.edge6.frankfurt1.level3.net (4.69.154.202)  20.964 ms

 7  * ae-4-90.edge6.frankfurt1.level3.net (4.69.154.202)  26.136 ms

    ae-3-80.edge6.frankfurt1.level3.net (4.69.154.138)  19.251 ms

 8  b.resolvers.level3.net (4.2.2.2)  23.044 ms  23.432 ms  42.155 ms

4 -- Connected over Wifi / SSID: billy1 / VLAN1 / Internal AP / Channel 1 (Internet is NOT working!) -

MacBook-Pro:~ billy$ traceroute 4.2.2.2

traceroute to 4.2.2.2 (4.2.2.2), 64 hops max, 52 byte packets

 1  192.168.1.1 (192.168.1.1)  3.662 ms  4.066 ms  2.919 ms

 2  10.239.0.1 (10.239.0.1)  11.216 ms  28.354 ms  9.710 ms

 3  weer-rc0002-cr101-xe-2-0-3-0.core.as9143.net (213.51.187.52)  10.432 ms  10.186 ms  15.812 ms

 4  asd-tr0042-cr101-ae4-0.core.as9143.net (213.51.160.214)  13.885 ms  15.084 ms  15.352 ms

 5  * lag-19.ear2.amsterdam1.level3.net (212.72.42.245)  15.225 ms  21.163 ms

 6  ae-4-90.edge6.frankfurt1.level3.net (4.69.154.202)  22.764 ms

    ae-1-60.edge6.frankfurt1.level3.net (4.69.154.10)  26.688 ms  31.601 ms

 7  ae-1-60.edge6.frankfurt1.level3.net (4.69.154.10)  22.667 ms *

    ae-4-90.edge6.frankfurt1.level3.net (4.69.154.202)  50.932 ms

 8  b.resolvers.level3.net (4.2.2.2)  23.149 ms  25.928 ms  28.640 ms

The RV130W is configured as "Gateway". Hope that clears something up?

[cchamorr]

Hello, 

I'm sorry you are having issues with your device.

After reading your post, something caught my attention.

You said that you are using different VLANS for the wireless network on the RV130W as well as the WAP121, but you also mentioned that the WAP121 is connected to an un-managed switch (No Vlan Capable) on the other side of the hallway.

I'm not sure if this is support to work as the switch should only pass traffic on the untagged VLAN (by default VLAN 1). 

Before trying anything else I would like for you to connect the WAP directly to the router on any of the ports. Make sure the port is configured to pass both VLAN's; it should be untagged for VLAN 1 and tagged for VLAN 3 (check the attached screenshot) and see if it works then.

If it does, you will need a manged switch to configure both VLANS on and pass them to the WAP121. 

Also make sure the firmware on both devices is up to date:

1- Check the firmware on the RV130W. The latest version is 1.0.1.3. If you are running anything lower than that go ahead and upgrade the firmware. here is the link for the download page:

https://software.cisco.com/download/release.html?mdfid=285026142&softwareid=282465789&release=1.0.1.3&relind=AVAILABLE&rellifecycle=&reltype=latest

2- Do the same for the WAP121, the latest firmware is: 1.0.5.3. Here is the download page for this access point:

https://software.cisco.com/download/release.html?mdfid=284152657&catid=278875243&softwareid=282463166&release=1.0.5.3&relind=AVAILABLE&rellifecycle=&reltype=latest

Please let us know how the test goes.

[zk1234567]

Dear cchamorr, Thank you for your reply.

According to the SG100D-08 it's manual, the switch is configured to comply with 802.1p, VLAN tagged frames. Mapping of the two SSID's to VLAN1 and VLAN3 is taking place inside the WAP121. If the SG100D-08 would not pass the VLAN3-taged signals, the VLAN1 connectivity (trough it's own mapped SSID) should be working fine. Unfortunately it's not.

I did try to connect the WAP121 directly to the router (without the switch in between). Same issues.

For troubleshooting, I reconfigured All SSID's as follows:

RV130W Internal AP:

• billy1
• guest1

WAP121:

• billy2
• guest2

Firmware was updated to the latest versions as u described. 

Any more suggestions?

[cchamorr]

Hello, 

Thank you very much for the reply and following my recommended steps.

This sounds very familiar to the behavior of the RV180W when an access point is on the same network. The issue with the RV180W is the fact that it is not compatible with any other AP than itself (other RV180W on Access Point Mode). If you were to have another AP on the same network as the RV180W then your wireless internet traffic will be affected.

Now, I'm not sure this router is supposed to have the same behavior (but it wouldn't surprise me as the RV130W is the replacement for the RV180W which has been discontinued).

To check this, go ahead and disable the radio on the RV130W by going to Wireless - Basic Settings and removing the check mark next to Enable Radio. Then reboot both units and try to connect again to the wireless coming from the AP, if everything works as expected then you will have two options:

1- Use only the RV130W and no the access point.

2- Keep the radio from the Rv130W disabled and get another AP to increase your wireless range

Please let us know if you are able to do this tests and what are your results. 

Don't forget to mark and answer as correct if it was helpful to you so other can benefit from it.

Also don't hesitate to ask any other questions.

[zk1234567]

I can assure you that this "RV130W-Non-Radio" configuration works since I tested it before.

I'm not sure, but it seems like you belong yo the Cisco staff. If so, could you please tell me how I could possibly have known that using on-board wifi in combination with external AP's does not work?

• Or is it just an issue with the WAP121 in specific?
• Is there a work-around?
• Can you give me an example of a WAPxxx model that does work with the RV130W's radio ON? Or is it the RV130W that should be exchanged for an RV220W?

[cchamorr]

Hello,

I would like to answer your questions:

1- Yes, I'm an Engineer with the Cisco Small Business Support Center

2- I will try to replicate this settings on the lab as soon as I can, but the reason it doesn't work wouldn't be related to the AP but to the router itself.

3- The work arounds are what I suggested before.

4- Since I believe the issue is related to the router and no the AP, it would be a good idea to replace it with a router that does not have this limitation. The RV220 is a great choice, but I do have to mention that it has been discontinued already but it will still have hardware support until January 31st 2020.

Here is the link to the EOL notice.

http://www.cisco.com/c/en/us/products/collateral/routers/small-business-rv-series-routers/eos-eol-notice-c51-732974.html

Please let us know if you have any more questions

[zk1234567]

Thank you,

I'm going to exchange te RV130W with an RV130 and add a second WAP121 to configure te "main" and "guest" SSID for both AP's with the Single Point Setup feature.

[cchamorr]

Hello, 

I think that is a great idea, you will be able to accomplish what you were looking for and have more flexibility as you will be able to move the access points to different locations if needed.

Thank you for posting.