I have an RV042 with a small office network behind it. The subnet for our LAN is 10.4.20.0/24 with the RV042’s Device IP Address set to 10.4.20.1 and the Subnet Mask of 255.255.255.0. Thus I can go to 10.4.20.1 and get the RV042’s login screen. This all works great. The problem is that I’d like to use Cloudflare’s new DNS service which uses the IP address 1.1.1.1. However whenever I enter that IP address into any of the browsers on my LAN, I get the RV042’s login screen (just like I do for 10.4.20.1). For some reason the RV042 is thinking that 1.1.1.1 is another IP address that it should be responding to. I’m not sure why. I’ve looked through all of the different configurations and setting for the router and I don’t have anything like that anywhere that I can find. Is the address 1.1.1.1 something that is hard wired into the RV042 firmware? Or am I missing a setting somewhere? Thanks. ... View more

I have a 6 month old RV042 with the newest firmware (v4.2.1.02). Over the weekend I configured the DMZ which after a lot of trial and error, was able to get working. Prior to configuring DMZ, I was able to log in with remote management. However now remote management no longer works. I've tried: - Rebooting the router - Turning the firewall off/on - Turning remote management off/on - Changing the remote management port The only step I haven't taken is resetting the router back to factory defaults and trying to reconfigure it all again. This router is so finicky I have no faith I'd be able to get my current functionality back again. Attached are screenshots of some relevant pages. Any idea what I'm doing wrong? ... View more

I'm tryig to put a computer into the DMZ and then access it from computers on the LAN using a local IP address. My reason for doing this is that I'd like my DMZ computer to be a locked down web server (just ports 80 and 443 open to the outside), but I need to be able to have more access to it from inside my LAN (e.g. I want to be able to SSH into it from the LAN). Thus far I've been able to get a computer set up in the DMZ and can access the Internet from the DMZ computer. And I can access the DMZ computer from the LAN computers using the public address for the DMZ computer. But I can't access the DMZ computer from the LAN computers using a private address for the DMZ computer. Please see the attached file for a diagram of our current settings. A few descriptions: - Verizon provides us with a number of static IP addresses, i.e. 71.123.123.10-12 (note these aren't actually the addresses, but representative). -- In the RV042, I have the following configurations made: - Setup > Network > LAN Setting - Device IP Address = 10.4.20.1 - Subnet Mask = 255.255.255.0 - Setup > Network > Edit WAN Connection - Specify WAN IP Address = 71.123.123.10 - Subnet Mask = 255.255.255.0 - Default Gateway Address = 71.123.123.1 - Setup > Network > Edit DMZ Connection - Interface = Range - IP Range for DMZ port = 71.123.123.11 to 71.123.123.11 - Setup > DMZ Host - DMZ Private IP Address = 10.4.20.71 (NOTE: I have no idea if this is necessary or correct) -- Computer network settings: - For computers on the LAN (i.e. computers A and B), I have the following set: - IP Address = 10.4.20.100 (for A) and 10.4.20.110 (for B) - Subnet Mask = 255.255.255.0 - Default Gateway Address = 10.4.20.1 - For the computer on the DMZ (i.e. computer C), I have the following set: - IP Address = 71.123.123.11 - Subnet Mask = 255.255.255.0 - Default Gateway Address = 71.123.123.1 As I mentioned above, this is all working great: - I can ping from A to B using the private address (i.e. ping 10.4.20.110) - I can ping from B to A using the private address (i.e. ping 10.4.20.100) - I can ping from A or B to any outside public address (e.g. google.com) - I can ping from A to C using the public address (i.e. ping 71.123.123.11) - I can ping from C to any outside public address (e.g. google.com) What I can't do: - I can't ping from C to A using the private address (i.e. ping 10.4.20.110) - I can't ping from C to the router using the private address (i.e. ping 10.4.20.1) - I can't ping from C to the router using the public address (i.e. ping 71.123.123.10) - I can't ping from A to C using the private address (i.e. ping 10.4.20.71) Is there a way to create a path so that I can connect from the LAN computers (A and B) to the DMZ computer (C) using just the private address? Once I figure this out, my next step is going to be locking down the firewall on the DMZ computer to just 80 and 443 from the public WAN (outside), but opening up some additional ports when connecting from the private LAN (inside). Thanks for any help you can provide. ... View more

I'm trying to set up a RV042 to do the following: 1) Block all WAN connections, except for: 2) Allow all port 80 connections, and forward to 10.4.20.60 3) Allow all port 443 connections, and forward to 10.4.20.60 4) Allow port 22 connections from specific IP addresses, and forward to 10.4.20.60 5) After a remote client has connected using Client to Gateway VPN, allow that remote client to access anything on the LAN I'm able to do #1-4 above, but I can't get #5 to work. Or I can get #5 to work, but can't implement the restrictions I need in #1-4. Attached are some relevant screenshots. I think the problem is that I have Forwarding rules set up that require me to have a firewall rule to Deny All Traffic from WAN1 (unless I'm specifically allowing it). In the Access Rules screenshot, rule #6 is the problem. If I enable it (thereby denying all WAN1 traffic), then VPN clinents can't access anything on the LAN. However if disable this rule, VPN clinents can access anything on the LAN, but the firewall also opens up all outside connections to SSH, since that's set up in the Forwarding rules. I would have thought that once a remote client is connected using client to gateway VPN, then that client is considered to be on the LAN, as far as the firewall is concerned. Thus a firewall rule (like #6) that is specified for WAN1 shouldn't effect remote VPN clients. What's the right way to set this up? ... View more

I have what I think should be a pretty simple question. I think I'm just not understanding how port forwarding works together with access rules. We have a computer (10.4.20.60) on our LAN that's running a web server (port 80), and I'd like to make it available to a single IP address (let's say 123.123.123.123) outside the LAN. I can set up Forwarding to forward port 80 to 10.4.20.60 and that works fine, but it's open to any outside IP address. So I then created a Firewall > Access Rule to restrict port 80 access to only the external IP address. However as soon as I do that, all access to port 80 is blocked. The access rule I set up was: Priority: 1 Policy Name: HTTP Enabled: X Action: Allow Service: HTTP[80] Source Interface: WAN1 Source: 123.123.123.123 ~ 123.123.123.123 (I'm actually using the correct IP) Destination: 10.4.20.60 Time: Always As I said, as soon as I added and enabled this access rule, everything to 80 is blocked. As a test, I modified the rule above to be open to all sources and destinations: Priority: 1 Policy Name: HTTP Enabled: X Action: Allow Service: HTTP[80] Source Interface: WAN1 Source: Any Destination: Any Time: Always Even with these settings access to port 80 is blocked from all outside IP addresses. Below is a screenshot of my current Access Rules page. What am I doing wrong? ... View more