Hi,I have a ReadyNAS 104 (and an older ReadyNAS Duo V1) and I wanted to change the MTU on the RN104 so it is the same as the rest of my network; 7936. However, every time I try to change the MTU on the RN104, it just hangs. The display on the front says "No IP address", which is "weird" to say the least as it is set at a fixed ip-adress. Trying to switch it off with the front power button fails as well (it sits there for hours happily stating powering down, goodbye) and only unplugging it from the mains helps. On reboot all is OK again, but the standard mtu of 1500 is back and not the desired 7936.Performance is OK with the standard 1500 MTU, just wanted to try and squeeze some extra performance out of it.Firmware is the 6.0.6Suggestions? Seems like a solid bug to me.

can you post the models of your router or switch?

I've just experienced the same thing with a new RN102 on 6.0.8.With a working fixed IP, I set mtu to 9000 and immediately could not talk to it, or shut it down gracefully by the power button.Initially it was connected to a Linksys E2400. But it still wouldn't work, even direct connected to a PC with same mtu, even after a reboot.This has to be a bug.

The switch is not the problem. My other network items all happily support and work with the higher mtu settings. I just tried again and changing MTU on the 104 with 6.0.8 opsys blocks all access to the unit and also like "res" states, it will not shutdown gracefully anymore using the power button. The display on the front states "no ip address", where it should state the fixed ip-address it is set up with (which it happily does when mtu is at 1500). I don't use DHCP in my network. All is setup using fixed ip-addresses (makes it oh so easy to work by setting up aliases in the hosts files ;-))So I agree with res., this is a bug and a nasty one at that.As an aside; a disk spindown option would be nice as well. Even my old Duo v1 supports that. ;-)

This should be incompatible issue not software nor hardware since we can set large MTU on our unit,maybe driver updating can be resolve this I guess.

what driver should be updated then? And do you have a fixed IP address on your unit? Both "res" and myself are on 6.0.8. and have fixed ip-addresses and both encounter the same problem. And if it is "incompatibilty" why on earth does the unit than lose its ipadres when trying to change the mtu? Does not really make sense.

Changing MTU hangs RN104 | NETGEAR Communities

12 Replies

Replies have been turned off for this discussion

de_niro
Guide
Jun 08, 2013
can you post the models of your router or switch?
res1
Aspirant
Jun 30, 2013
I've just experienced the same thing with a new RN102 on 6.0.8.

With a working fixed IP, I set mtu to 9000 and immediately could not talk to it, or shut it down gracefully by the power button.

Initially it was connected to a Linksys E2400. But it still wouldn't work, even direct connected to a PC with same mtu, even after a reboot.

This has to be a bug.
Jobber72
Aspirant
Jul 10, 2013
The switch is not the problem. My other network items all happily support and work with the higher mtu settings. I just tried again and changing MTU on the 104 with 6.0.8 opsys blocks all access to the unit and also like "res" states, it will not shutdown gracefully anymore using the power button. The display on the front states "no ip address", where it should state the fixed ip-address it is set up with (which it happily does when mtu is at 1500). I don't use DHCP in my network. All is setup using fixed ip-addresses (makes it oh so easy to work by setting up aliases in the hosts files ;-))

So I agree with res., this is a bug and a nasty one at that.

As an aside; a disk spindown option would be nice as well. Even my old Duo v1 supports that. ;-)
de_niro
Guide
Jul 11, 2013
This should be incompatible issue not software nor hardware since we can set large MTU on our unit,maybe driver updating can be resolve this I guess.
Jobber72
Aspirant
Jul 11, 2013
what driver should be updated then? And do you have a fixed IP address on your unit? Both "res" and myself are on 6.0.8. and have fixed ip-addresses and both encounter the same problem. And if it is "incompatibilty" why on earth does the unit than lose its ipadres when trying to change the mtu? Does not really make sense.
marcusp
Tutor
Feb 02, 2014
Same problem here with a RN102 (latest firmware), when I set the MTU to 9000, I lost the connection, raidar does not see it and it's impossible to shut it down !
StephenB
Guru - Experienced User
Feb 02, 2014
marcusp wrote:
Same problem here with a RN102 (latest firmware), when I set the MTU to 9000, I lost the connection, raidar does not see it and it's impossible to shut it down !
What switch/router are you using?

You can do an OS reinstall, which should reset the network settings (including changing over to DHCP), and will also reset the admin password back to "password".
marcusp
Tutor
Feb 03, 2014
I was using a WNDR 3700 which accepts jumbo frames in passthrough mode (no problem with my Pro 6) if I'm right. But what I don't understand is why the NAS was freezing and didn't want to shut down. I had to remove the power plug, and reset to default factory. Fortunately I was just trying several settings before using this NAS to backup my Pro 6.
I've bought a GS108T to use LAG with the Pro 6 and it officially support jumbo frames, so I'll see if it works...
StephenB
Guru - Experienced User
Feb 04, 2014
I have the GS108T, and the combination of JF and LAG does not work for me. The same is true with my GS724T. (That is with my Pro-6)

The router spec does not include JF, but there are some folks who report that they do in fact work.
marcusp
Tutor
Feb 04, 2014
it's a little off topic, but my Pro 6 already works with LAG + JF + GS108T v2 (with latest firmware) and today my Seagate ST2000DM001 (pathetic HD !) came back from RMA, so I'll try with the Readynas 102. Btw my network card is an Atheros AR8131 with 9K JF support.
For the router, it doesn't handle JF, but let them pass from what I see...and I've put a custom firmware (Gargoyle based on OpenWRT) on the WNDR3700v1. I know that's not a firmware problem, just the chipset which does not support theses kind of frames.