NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ronnycook
May 09, 2013Aspirant
SRX5308 - no IP routing with 4.x firmware
We've been running a Netgear SRX5308 using v3.7 firmware for some time. We've had some stability issues, so recently tried upgrading the firmware to one of the 4.2 or 4.3 revisions.
After doing this (and reconfiguring accordingly), we found that we could ping the Netgear, and the Netgear could ping either side of itself, but any traceroute would stop at the router. Essentially it appears that the device is not passing traffic through. (We're not seeing any inbound traffic either.)
Enabling packet logging did not show any entries in the system logs. Enabling IPv6 made no difference either way.
The unit is operating in Classic Routing mode; the firewall rulesets are configured to "Pass All". While the system originally had multiple network links and multiple internal gateways, a test configuration with a single network link and a single gateway showed the same symptoms, i.e. no traffic passing through the network, traceroute showing the last hop as being the SRX5308.
When we downgraded back to 3.7 function was restored. Upgrading to the 3.8 firmware also worked without any problems (and is the current configuration).
Can anyone suggest what may be going wrong? I can supply a copy of the backup of our configuration (3.x & 4.x) if that would help, but posting on a semi-public forum is something I would rather not do...
After doing this (and reconfiguring accordingly), we found that we could ping the Netgear, and the Netgear could ping either side of itself, but any traceroute would stop at the router. Essentially it appears that the device is not passing traffic through. (We're not seeing any inbound traffic either.)
Enabling packet logging did not show any entries in the system logs. Enabling IPv6 made no difference either way.
The unit is operating in Classic Routing mode; the firewall rulesets are configured to "Pass All". While the system originally had multiple network links and multiple internal gateways, a test configuration with a single network link and a single gateway showed the same symptoms, i.e. no traffic passing through the network, traceroute showing the last hop as being the SRX5308.
When we downgraded back to 3.7 function was restored. Upgrading to the 3.8 firmware also worked without any problems (and is the current configuration).
Can anyone suggest what may be going wrong? I can supply a copy of the backup of our configuration (3.x & 4.x) if that would help, but posting on a semi-public forum is something I would rather not do...
4 Replies
- jmizoguchiVirtuosoHard reset the router and manually configure it.
If still the same revert the firmware and report the issues to support at my.netgear.com - ronnycookAspirantA hard reset and complete reconfigure is a required part of the upgrade from 3.x to 4.x.
I wiped the system config, then uploaded the firmware and reconfigured from scratch.
So, I suppose it's talking to Netgear then... Fortunately we just bought a new router of the same model so can probably reproduce the issue on a unit that's still in warranty. - aditMentorDefault it after the upgrade, then manually reconfigure.
- AlexKaraAspirantHi!
In FireWall mode the rules from Protocol Binding overload all settings.
It Break work for "Routing" and Firewall "Inbound Services" (Outbound Services - isn't tested yet).
Try to remove all rules in Network Configuration -> Protocol Binding
IMHO: it is 100% - Incorrect logic of operation of the device.
In F|W 3... it was so:
1) routing rules
2) Firewall Services
3) Protocol Binding...
BUT in F|W 4... the first is Protocol Binding rules....not logically
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!