NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Y0tsuya's avatar
Y0tsuya
Aspirant
Feb 10, 2012

SRX5308 secondary IP port forwarding

Just got a brand new SRX5308 to replace a dependable but somewhat underpowered FVS336g. I spent the past few days trying to get it to do simple port forwarding on a secondary IP. I tried 3.0.7-29 and 3.0.7-45, hard-resetting in between FW swaps. Each time I would manually setup the WAN IP (I have 2 but focus on WAN1) and a single inbound PING rule to a server, wait for it to stabilize and the access a ping tool such as one at network-tools.com. So I know the WAN is set up correctly and outbound works. But ping from WAN is never forwarded to the LAN server. I've opened a ticket with tech support. But in the meantime want to know if anyone has any idea what I can try

4 Replies

  • I have the same issue. I have a ticket in with Level 3 support. They took a packet capture and it shows the packets being malformed and coming back on the wrong interface. Its been almost two weeks and I haven't heard anything. You should contact support about it. I think the more complaints the quicker they get to fixing the issue.
  • I found the problem yesterday. I'm kind of guessing but the router and modem may need to announce to each other using ARP. Just swapping in the router without also rebooting the modem won't force ARP announcements. Imagine my chagrin when I rebooted both the modem and router and voila everything worked! It just hadn't occurred to me to reboot the modem since I've never had to. Also I'm guessing the "Secondary Address" thing works differently from FVS336g in that SRX5308 doesn't announce the new IP when I add it.
  • I found via level 2 support that if both IP's are on the same subnet, the second address just does not work... May want to confirm that when you call them if that is your case.
  • The documentation is a bit ambiguous on this matter. But I've added secondary IPs inside the same subnet as primary WAN IP. It works for me. I've managed to stump tech support for over a week with this issue. I was only able to solve this after spotting a pattern:

    Primary WAN IP port fowarding always works
    Secondary IP port forwarding does not work
    IP range port forwarding always forwards to WAN IP
    If I move the WAN IP to something else in the same subnet, Secondary IP port forwarding to the recently vacated IP works.

    Which got me to think that only the primary WAN IP will properly perform ARP with the modem. Just adding Secondary IP will not cause the modem to recognize it. Of course all this goes away after I reset both the modem and the router and force to repopulate their tables from scratch.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More