Public IP used internally on RV220W

[NeonNero1]

Hi,

I've finally set up our RV220W to serve our office network, using the following environment:

The WAN is set to a public IP (static configuration), while the internal network consists of two VLANs.

VLAN 1 is connected to the cabled network and one wireless SSID, where DHCP is served by our Windows SBS server (192.168.15.x), and this VLAN is used only for our own office. VLAN 2 is connected to a second wireless SSID, where DHCP is served by the RV220W itself (192.168.17.x), and this VLAN is used for guests and visitors to our office.

On a regular basis, we need to use a mobile device to access a test page from a development server on VLAN 1, and the router is configured to redirect connections on a specific port on the public IP to our development server.

For VLAN 1, I solved this by overriding DNS for the hostname of this test page to use the local IP for the development server.

However, for VLAN 2, there is no way to access this test page.

Is there any way I can configure the router to either redirect these connections, or override the internal DNS so the test page on the development server can be reached also from VLAN 2 (the guest/visitor network)?

Thank you for any help.

[Tom Watts]

Hi Kim,  it sounds like you're trying to hairpin. When you use the public IP from the internal VLAN 2, are you able to meet the test page?

-Tom
Please rate helpful posts

[NeonNero1]

Hi Tom,

When I open the public IP (213.x.x.x) from VLAN 2 (192.168.17.x) in my browser, I get to the router's web based administration interface. Opening the public IP on port 8088 (which should be redirected to the test server from the outside using the router's NAT) simply gives a timeout.

-Kim

[Tom Watts · Accepted solution]

Hi Kim, what version firmware are you using? Can you load the latest

http://www.cisco.com/cisco/software/release.html?mdfid=283118607&flowid=&softwareid=282487380&os=null&release=1.0.4.17&relind=null&rellifecycle=null&reltype=null

On earlier releases there were some hairpin issues but most have been resolved on the last 2 releases.

-Tom
Please rate helpful posts

[NeonNero1]

Hi Tom,

I figured that I probably should have the latest firmware, so I had upgraded the firmware a few hours before your latest response. Firmware installed is now 1.0.4.17 (confirmed from the router's Status/Dashboard page).

I've now even disabled remote management (Administration/Remote Management), in case this might have something to do with it.

Is there something I need to configure specially to allow for hairpin connections?

-Kim

[NeonNero1]

Yay! Progress!

After searching around for a bit on the issue of rv220w hairpinning, I followed the suggestion found here:

https://supportforums.cisco.com/message/3422102#3422102

After editing and saving each rule found under Firewall -> Access Rules, I tried opening https://213.x.x.x/, where I got a 404 error (since the browser probably had cached a redirect to /scgi-bin/platform, which is the router admin). Following a hunch, I opened https://213.x.x.x/owa, which got me to the Outlook Web App for Exchange 2010. Meaning, my connection was redirected via DNAT back to the SBS2011 server on our local network.

I'd also have to admit, until your first reply in this thread, I had never heard of the term "hairpin"/"hairpinning" - thanks for introducing me to the term, which in turn helped me get a major step closer to solving this.

-Kim