Has anyone had any experience with the RVS4000 and gettting them to be PCI compliant? I have several RVS4000's in place for credit card terminals. When the port scan is run everything passes but the test for UDP probes with a source port of 53 vs some other random port to specific ports on the RVS4000's end. Here is an example. UDP probe source port 53 to target port 111, result: 111 UDP closed. UDP probe source port 53566 to target port 111, result: 111 UDP open|filtered. This occurs with an ACL rule set to DENY all UDP traffic from ANY source. This rule is priority 1. Firmware is 1.3.1. I am assuming that there are other firewall rules for the DNS (port 53) that are "hidden" that are overriding my ACL rules. If anyone has any ideas about how to get around this, please let me know.
** After reading a thread regarding DNS and the IPS features, I tried disabling the IPS features. With IPS disabled, I ran the scan a few more times. This time it responded 111 UPD closed when probed from 53566. HOWEVER after a power cycle of the RVS4000 it responded 111 UDP open|filtered again. I tried to replicate the results, and I could but, it does not consistently do this.
Article ID:5748 Use TheGreenBow VPN Client to Connect with RV34x Series
Router Introduction A Virtual Private Network (VPN) connection allows
users to access, send, and receive data to and from a private network by
means of going through a public or share...
Article ID:5728 Configure a Teleworker VPN Client on the RV34x Series
Router Objective The Teleworker VPN Client feature minimizes the
configuration requirements at remote locations by allowing the device to
work as a Cisco VPN hardware client. When the T...
Article ID:5708 Configure the LAN and DHCP Settings on the RV34x Series
Router Objective A Local Area Network (LAN) is a network limited to an
area such as a home or small business that is used to interconnect
devices. LAN settings can be configured to li...