RV220W - losing connectivity between clients, reboot needed

Unanswered Question
Sep 11th, 2012

Hi,

I'm losing network connectivity to other network clients (wired/wireless) every other day. Ping and lookup is still possible. But Windows file sharing, TimeMachine and AirPlay are somehow blocked.

Only rebooting the router helps.

I'm affected by this behavior from the beginning (since purchasing the router). But with older firmwares (pre 1.0.4.17), only wired clients were affected (connectivity between wired and wirelss clients is broken). Since this bug wasn't solved, the router became my home router. Now, with firmware 1.0.4.17, also wireless clients are affected (connectivity between wireless clients is broken). This bug/defect makes this router quite useless even for a home router.

I tried to track down the problem by resetting settings to default values one by one, but I failed. I also disabled Attack-Prevention funtionality. Nothing really helped.

Anybody? Any Idea what could be the problem?

Thanks in advance for any help!

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 5 (1 ratings)
Hakiru-84 Wed, 09/12/2012 - 01:04

Unfortunately, I can not help you, I can only add that I have a similar problem but not the same .. because in my case, that my clients VPN suddenly lose access to the tunnel (no changes are made on the router) - are not able to connect with QuickVPN and only restart helps.

BTW.

Did you check that the logs do not give you any additional informations? 

Tom Watts Wed, 09/12/2012 - 09:37

Hi both, to my knowledge there is only a very few isolated instances where the RV220W doesn't supply basic connectivity. If you can enable the local log and also set up an external syslog, it may reveal what is going on with the router. You can also use the diagnostic packet captures for the LAN to see if there are any weird packets or packet errors. Other than that, you may want to try a different RV220W. If the same issue persists, I'd say there could be some kind of bug but if the issue goes away, it is just an isolated incident.

-Tom
Please rate helpful posts

jensjanssen Wed, 09/12/2012 - 13:15

OK, just setted up a splunk server. Any suggestions what logging information is needed?

SeveritySystemKernelWirelessProtectLink
Emergency
Alert
Critical
Error
Warning
Notification
Information
Debugging
Tom Watts Wed, 09/12/2012 - 13:28

All should be fine. This should give ample details if any problems persist. When you're experiencing connectivity issues, is it possible to run a LAN packet capture from the Diagnostics of the router?

Also, do you lose the ability to remote manage the router over the WAN?

-Tom
Please rate helpful posts

jensjanssen Wed, 09/12/2012 - 13:38

OK, I will try to capture packets. I will also enable remote management.

Thanks for your assistance!

jensjanssen Sat, 09/15/2012 - 09:59

hope I got it! :-)

This is the only occurrence... exactly when the connection broke up.

Sep 15 12:30:29 192.168.1.1 Sep 15 11:30:23 rv220w FIREWALL [System] Disabling Firewall Rule for MSS packet marking

Sep 15 12:30:29 192.168.1.1 Sep 15 11:30:23 rv220w FIREWALL [System] fwPPTPGenericRules.c: inet_aton failed

Sep 15 12:30:29 192.168.1.1 Sep 15 11:30:23 rv220w FIREWALL [System] Enabling Inter VLAN routing.

Sep 15 12:30:27 192.168.1.1 Sep 15 11:30:22 rv220w FIREWALL [System] Enabling DOS Attacks

Sep 15 12:30:27 192.168.1.1 Sep 15 11:30:22 rv220w FIREWALL [System] Restarting Source MAC Address Policy

Sep 15 12:30:27 192.168.1.1 Sep 15 11:30:22 rv220w FIREWALL [System] Adding MAC Filter Policy for Block & Permit Rest

Sep 15 12:30:27 192.168.1.1 Sep 15 11:30:22 rv220w FIREWALL [System] Disabling Source MAC Filtering

Sep 15 12:30:27 192.168.1.1 Sep 15 11:30:22 rv220w FIREWALL [System] Enabling Management Access from Internet to port 443

Sep 15 12:29:48 192.168.1.1 Sep 15 11:29:43 rv220w NIMF [System] nimfNetIfaceTblHandler: unable to get LedPinId

Sep 15 12:29:48 192.168.1.1 Sep 15 11:29:43 rv220w NIMF [System] Setting LED [0]:[1] For WAN1

Sep 15 12:29:48 192.168.1.1 Sep 15 11:29:43 rv220w FIREWALL [System] Restarting Firewall [0]:[1] For WAN1

Sep 15 12:29:40 192.168.1.1 Sep 15 11:29:34 rv220w FIREWALL [System] Restarting Firewall For WAN1 Address Update from 0.0.0.0:95.XXX.XXX.165

Sep 15 12:29:35 192.168.1.1 Sep 15 11:29:30 rv220w KERNEL [Kernel] eth1: no IPv6 routers present

Sep 15 12:29:34 192.168.1.1 Sep 15 11:29:28 rv220w FIREWALL [System] Restarting Firewall [0]:[1] For WAN1

Sep 15 12:29:25 192.168.1.1 Sep 15 11:29:20 rv220w KERNEL [Kernel] IPsec: device down: eth1

Sep 15 12:29:24 192.168.1.1 Sep 15 11:29:19 rv220w FIREWALL [System] ____/pfrm2.0/bin/iptables -t nat -D POSTROUTING -o eth1 -j SNAT --to-source 95.XXX.XXX.165___

Sep 15 12:28:58 192.168.1.1 Jan 01 01:02:42 rv220w FIREWALL [System] Disabling Firewall Rule for MSS packet marking

Sep 15 12:28:58 192.168.1.1 Jan 01 01:02:42 rv220w FIREWALL [System] fwPPTPGenericRules.c: inet_aton failed

Sep 15 12:28:58 192.168.1.1 Jan 01 01:02:42 rv220w FIREWALL [System] Enabling Inter VLAN routing.

Sep 15 12:28:57 192.168.1.1 Jan 01 01:02:41 rv220w FIREWALL [System] Enabling DOS Attacks

Sep 15 12:28:57 192.168.1.1 Jan 01 01:02:40 rv220w FIREWALL [System] Restarting Source MAC Address Policy

It seems that parts of the system got restarted. During this process, wireless connection was very unstable.

Remote Webif is still accessible.

Hakiru-84 Mon, 11/26/2012 - 04:49

My problem manifests itself notoriously every 3-4 days. I have to do reset to connect with QuickVPN.

2012-11-26 14:20:48: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=80f1f2dd37522b58:123fc4cc5c3b558a.
2012-11-26 14:20:48: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=e728a1b036ccdb32:76014c353c9099fe.
2012-11-26 14:20:48: [rv220w][IKE] WARNING:  no phase2 found for "m-test"
2012-11-26 14:20:48: [rv220w][IKE] INFO:  IPSec configuration with identifier "m-test" deleted sucessfully
2012-11-26 14:20:49: [rv220w][IKE] ERROR:  sainfo identifier not found ("m-test")
2012-11-26 14:20:49: [rv220w][IKE] ERROR:  Failed to Delete the IPSec configuration with identifier "m-test"
2012-11-26 14:20:49: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 46.28.241.202[4500]-93.154.129.33[4500] with spi:80f1f2dd37522b58:123fc4cc5c3b558a
2012-11-26 14:20:49: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 46.28.241.202[4500]-93.154.129.33[4500] with spi:e728a1b036ccdb32:76014c353c9099fe
2012-11-26 14:20:49: [rv220w][IKE] ERROR:  remote identifier not found ("")
2012-11-26 14:20:49: [rv220w][IKE] ERROR:  Failed to Delete the IKE configuration with identifier ""
2012-11-26 14:24:52: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
2012-11-26 14:24:52: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
2012-11-26 14:25:00: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
2012-11-26 14:25:00: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
2012-11-26 14:25:01: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
2012-11-26 14:25:01: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
2012-11-26 14:25:02: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
2012-11-26 14:25:02: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
2012-11-26 14:25:05: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
2012-11-26 14:25:05: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
2012-11-26 14:25:08: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
2012-11-26 14:25:08: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
2012-11-26 14:25:11: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
2012-11-26 14:25:11: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
2012-11-26 14:25:14: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
2012-11-26 14:25:14: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
2012-11-26 14:25:17: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
2012-11-26 14:25:17: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
2012-11-26 14:25:21: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
2012-11-26 14:25:21: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
2012-11-26 14:25:24: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
2012-11-26 14:25:24: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
2012-11-26 14:25:27: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
2012-11-26 14:25:27: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
2012-11-26 14:25:30: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
2012-11-26 14:25:30: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
2012-11-26 14:25:33: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
2012-11-26 14:25:33: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
2012-11-26 14:25:36: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
2012-11-26 14:25:36: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
2012-11-26 14:25:39: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
2012-11-26 14:25:39: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
2012-11-26 14:25:42: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
2012-11-26 14:25:42: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
2012-11-26 14:25:45: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
2012-11-26 14:25:45: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]

I'm so tired of the continuous reset the router...

Edited by: Thomas Michalski

jensjanssen Sat, 09/15/2012 - 01:08

Thomas,

do you have DynDNS running? Just guessing...

The last thing I did: I disabled DynDNS. So far the router is running fine.

False Alarm, just had a few disconnects on my laptop. After that I wasn't able to connect my server. Wireless-to-Wireless is still working.

So, still weird behaviour observed. All router settings are basically set to default values.

In the last 3 days I collected nearly 40,000 (sic!) syslog messages from the router. I need more time to filter them.

Actions

Login or Register to take actions

This Discussion

Posted September 11, 2012 at 3:39 PM
Stats:
Replies:8 Avg. Rating:5
Views:1106 Votes:0
Shares:0

Related Content

Discussions Leaderboard