RV220W DMZ not working and protocol 41 packets not forwarded

[Joergen Thomsen]

After fighting a brand new RV220W for hours I am just about giving up on it.

It does not forward anything the to the DMZ server including the IP protocol 41 packets needed for our IPv6 6in4 tunnel.

Nor does it send protocol 41 packets to the WAN.

TCP and UDP packets are only forwarded to the DMZ server if specifically done by a firewall rule.

CISCO support was not able to solve the problem after half an hour on the phone.

Factory resets and absolutely minimal configuration changes have been tried to no avail.

Firmware is 1.0.1.0.

The hairpinning problem as well as the weird time problem cause by ticking the daylight savings box has been observed as well.

Should I return this thing having learned that CISCO quality is a thing of the past ?

The Netgear WNDR3700 it was supposed to replace, due to the SNMP support found in this router, happily forwards packets at half the price.

[Joergen Thomsen]

Manually creating a firewall rule with protocol 41 in the backup config file and restoring it makes no difference.
(A new checksum for the configuration file may be generated by md5sum when the checksum line has been deleted)

Default should be to route all IP packets regardless of protocol number to the DMZ server, when DMZ is enabled. Now the router returns a ICMP port unreachable message to the WAN sender.

Update:

The problem is only present when the dual stack IPv4/IPv6 feature is enabled, so after all it may be a bug and not a design decision. Waiting for Cisco support to verify/advice on this.

BTW it is unbelievable, that the configuration file (plain text) saved by the backup function in the router cannot be read / used by Cisco suppport. They can only handle something which can be displayed in a browser (sic!)

Update 2:

Further testing has shown, that the option of forwarding of protocol 41 packets for 6in4 tunnels in any mode (IPv4 only or IPv4/IPv6) is randomly enabled. Sometimes suddenly working after 30 minutes. At other times not at all even after a reboot. Occasionally it has been working in both modes.

I have provided information about this to CISCO.

Cisco support has recognized this to be a problem of the current software 1.0.1.0 and is issuing a refund of the router.

[Joergen Thomsen]

It would be interesting to know, now that CISCO has recognized the problem, which time frame there is for solving the problem ? The RV220W does have some nice features.

After submitting data to CISCO there has been only silence. ( case 618111043 )

[streaves]

Please see Setting Up 6to4 on RV220W, prepared by Small Business Router Engineering Team.

Thanks,

Stephanie Reaves

Cisco Small Business

[Joergen Thomsen]

Thank you, but this is totally out of scope.

We are not connecting two sites with our own IPv6 tunnel.

We are connecting to the global IPv6 network using a 6in4 tunnel provided by tunnelbroker.net, which is acting as the gateway to the IPv6 global network. We have no way of controlling the routers at tunnelbroker.net.

As it is now, this is not possible to do reliably with the RV220W firmware 1.0.1.0

[Joergen Thomsen]

After flashing beta firmware 1.0.2.1 nothing changed.

Even if the GUI now allows you explicitly to set the IP protocol number, then the routing engine does not handle it.

I  have spent several hours on this and submitted documentation to CISCO,  but the support will not even disclose, whether this documentation is  being used, whether the issue is being worked upon or any time frame  for the release of a new firmware.

This is really how you turn an after all positive customer into a dissatified one

There is more in support than polite phrases.

[streaves]

Hello Joergen -- Please see this Tech Note developed by Small Business Engineering. Let us know if it is helpful.

Connecting RV220W to an IPv6 Tunnel Broker

Thanks,

Stephanie Reaves

Cisco Small Business

[Joergen Thomsen]

Thank you for the instructions.

It really seems to require some difficult tweaking, but now the 6in4 tunnel is working from the DMZ server   (beta firmware 1.0.2.1)

Fortunately I have been able to delete the section previously published in this comment about problems with a Windows XP workstation.

With networking one should always remember to do frequent reboots of both routers and work stations when changing parameters.