NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
karl_w_w
Jan 23, 2018Aspirant
RN104 becomes unresponsive when changing MTU
I'm trying to change MTU on my RN104 (from 1500 to 1492), when I click apply the spinning wheel comes up for a few seconds, then the page with the loading bar appears as if the NAS has gone for a restart, but it never restarts, it just completely stops responding. Even the buttons on the NAS do nothing, I have to pull the plug to get it working again. When I start it back up the MTU is still 1500. Is this a known problem/is there a workaround?
Firmware is 6.9.1
6 Replies
Replies have been turned off for this discussion
- StephenBGuru - Experienced User
My RN102 (also running 6.9.1) will let me change the MTU to 1492.
It takes a few seconds, and the settings box dismisses itself (instead of simply showing the new MTU). But it does accept the setting, and when I go back into the settings wheel, it is still there.
Are you using NIC bonding?
Also, have you confirmed that you need to set the MTU to 1492?
- karl_w_wAspirant
No NIC bonding, just a single NIC connected to my router. I'm pretty sure I do need to change the MTU, I changed it in Windows to fix an unrelated problem and since then accessing the NAS has been sluggish.
- StephenBGuru - Experienced User
karl_w_w wrote:
I'm pretty sure I do need to change the MTU, I changed it in Windows to fix an unrelated problem and since then accessing the NAS has been sluggish.
If your router->ISP link uses PPPoE then you probably do need this MTU size. If it doesn't use PPPoE then the normal MTU should work fine.
So you might want to double-check that the Windows change was actually needed. One way is to set the Windows MTU back to 1500, and then use ping to measure the MTU needed by your ISP.
For instance, open CMD and then enter ping www.google.com -f -l 1472 If that returns a normal status, then the path MTU is 1500.
If it fails, then try ping www.google.com -f -l 1464 That should work if the path MTU is 1492 (the -l parameter is 28 bytes smaller than the full packet size).
However, setting the MTU to 1492 on the NAS should still work (and does on my ReadyNAS), so that issue is unexplained. Perhaps try setting it again while the PC is set to MTU 1500???
- karl_w_wAspirant
After the new update to 6.9.2 I can change the MTU with no issue, so all good I guess.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!