Hi Tom, thanks for your reply. Perhaps a little more detail concerning my configuration would help. The public IPs are ficticious, of course. RV042G LAN: 192.168.10.0/24 Public IPs: - 22.214.171.124/29 - 126.96.36.199/29 RV042 WAN1 Assigned to: 188.8.131.52, gateway .129 RV042 WAN2 Not used 1:1 NAT Needed: 184.108.40.206-134 translated to: 192.168.10.131-134 1:1 NAT Needed: 220.127.116.11-230 translated to: 192.168.10.228-230 The 207 and 204 public networks are routed to the RV042G from the outside, so I know traffic is getting to the RV042G. When I set up the two 1:1: NATs shown above, only the first NAT (131-134) works consistently and with stability. The second 1:1 NAT works for about 10 or 15 minutes, and then inexplicably stops working without any errors showing up in any of the logs. If I do anything that involves clicking a Save button on the RV042G web configuration interface, the second 1:1 NAT starts working again for another 10 or 15 minutes, then dies again. For example, if I go to the DHCP section and enable (or disable) DHCP, the second 1:1 NAT starts working normally. If I replace all of the NATs with individual mappings (131->131, 132->132, 133->133, etc) all of the mappings that lie in the routers primary public subnet (18.104.22.168/29) work flawlessly in mapping to the LAN network. But any public IP that is outside of the primary public subnet only maps properly to the LAN for 10 or 15 minutes, then stops working. I have tried assigning the WAN2 connection to the second public IP (22.214.171.124/29), but it does nothing to improve the situation. Is it possible that I need to segment the local LAN into two separate subnets for this to work? That is the only thing I really haven't tried yet. Or is this another bug in the firmware?
... View more
Apparently, there wasn't sufficient demand. I NEED this feature to work, but the latest firmware (4.2.2.08) STILL doesn't fix this problem. 1 to 1 NAT on a separate subnet (separate from the LAN subnet) only works temporarily (10 or 15 minutes), then it dies without complaint. If I do anything to the router like saving the configuration, it starts working again for 10 or 15 more minutes, then dies. Not cool.
... View more