NSA325-v2 becomes unresponsive after a while




I have a NSA325-v2 which I'm in general happy with. But recently I have noticed that after a while (like a week or so, haven't measured), I can't access it neither via web UI (I get "connection refused" error message), nor via SMB (tried both on macOS and Windows), nor can I access videos and photos on NAS via my TV. This model has no support anymore so I can't update firmware to see if that solves the issue. I haven't seen any setting that might affect it either (unless Wake on LAN can be buggy?). Has anyone experienced this issue and knows of any solution?
All Replies
-
This is reproducible I suppose? I have seen similar behaviour on my 325. Further investigation showed that somehow the IP stack was damaged, it was no longer possible to create new connections. (Existing connections survived, I found this using an ssh connection which I left open for more than a week).
Unfortunately I couldn't find what triggered this behaviour. As nothing changed on the NAS, it must be something in the network. My theory is that there is a memory leak or something like that in the IP stack, which is triggered by some recieved IP packet. When accumulated above some level, bang. My remedy was to create a cronjob to reboot the box at night, as the problem never occurred within 24 hours.
Did you change anything in your network prior to the problem started?
0 -
I don't remember if I had changed anything in the network tbh. But I will probably do the same with periodic reboots.
0
Categories
- All Categories
- 426 Beta Program
- 2.6K Nebula
- 163 Nebula Ideas
- 112 Nebula Status and Incidents
- 5.9K Security
- 343 USG FLEX H Series
- 288 Security Ideas
- 1.5K Switch
- 78 Switch Ideas
- 1.2K Wireless
- 42 Wireless Ideas
- 6.6K Consumer Product
- 261 Service & License
- 404 News and Release
- 86 Security Advisories
- 31 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.8K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 85 About Community
- 82 Security Highlight