NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
krylon
Mar 10, 2013Aspirant
Enable Jumbo Frames Causes External Hostname Problem
I use my ReadyNAS to host my web page. If I enable jumbo frames on my NAS and my PC then I can no longer access my web page using my external hostname (dyndns.org address) while on the LAN. I have to use the internal IP address of the ReadyNAS. When I disable jumbo frames on either my PC or ReadyNAS then I can suddenly use the external hostname while on the LAN. This happens on all jumbo frame capable machines on my LAN. The external hostname always works when outside of the LAN, when at work for example, regardless of jumbo frames. Shares always work as well, regardless of jumbo frames settings. I also ran a test by hosting a temporary web server on another computer in my LAN with jumbo frames and this problem doesn't happen, so I think it is the ReadyNAS but I am not sure how to fix it.
24 Replies
Replies have been turned off for this discussion
- chirpaLuminaryRouters tend to do a loopback mode when talking to external IP that is really on the same LAN. I'd chalk it up to something on the router.
I've seen others in the past have issues with external access to internal jumbo frame box. - krylonAspirant
chirpa wrote: Routers tend to do a loopback mode when talking to external IP that is really on the same LAN. I'd chalk it up to something on the router.
I've seen others in the past have issues with external access to internal jumbo frame box.
But I can host a web server on a PC with jumbo frames enabled and this problem doesn't exist, so the router is configured okay I would think - chirpaLuminaryAnd from another PC (not itself) you can also hit the dyndns address from the LAN and get it okay?
- chirpaLuminaryAlso, which model NAS do you have? x86 should be fine, but Sparc doesn't have true jumbo, its receive only, not send.
- krylonAspirant
chirpa wrote: Also, which model NAS do you have? x86 should be fine, but Sparc doesn't have true jumbo, its receive only, not send.
Pro Business x86
To clarify, I can access Readynas shares with jumbo frames on. I can also access the /www on the Readynas with jumbo frames on but only if typing the IP address of the ReadyNas in the address bar of the browser. - krylonAspirantStill struggling with this issue
- StephenBGuru - Experienced UserTry confirming the MTU with ping from the PC.
You do this by opening a command shell from Windows.
Then type
ping NASIP -f -l xxxx
Start with xxxx = FrameSize-28 (where FrameSize is the jumbo frame size you configured in Frontview).
If you get "Packet needs to be fragmented but DF set" then lower xxxx until that message goes away. - krylonAspirantJumbo frames seems to work for file transfers and shares but I can't hit the external hostname that points to the NAS, unless I disable Jumbo.
MTU is hard coded at 9000 for Jumbo frames on RAIDiator 4.2.22 x86, at least it appears that way:
ping 192.168.1.17 -f -l 8972
Pinging 192.168.1.17 with 8972 bytes of data:
Reply from 192.168.1.17: bytes=8972 time<1ms TTL=64
Reply from 192.168.1.17: bytes=8972 time<1ms TTL=64
Reply from 192.168.1.17: bytes=8972 time<1ms TTL=64
Reply from 192.168.1.17: bytes=8972 time<1ms TTL=64
Ping statistics for 192.168.1.17:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms - StephenBGuru - Experienced User
krylon wrote: Jumbo frames seems to work for file transfers and shares but I can't hit the external hostname that points to the NAS, unless I disable Jumbo.
Are you disabling jumbo on the NAS or the PC?
Also, is the "external hostname" your ddns name? If so, the issue may be in your router. - krylonAspirant
StephenB wrote: krylon wrote: Jumbo frames seems to work for file transfers and shares but I can't hit the external hostname that points to the NAS, unless I disable Jumbo.
Are you disabling jumbo on the NAS or the PC?
Also, is the "external hostname" your ddns name? If so, the issue may be in your router.
If I disable it on one or the other (client or NAS), then it works. I can host a webserver on my spare computer with Jumbo frames and I don't have a problem accessing the ddns name from my main PC when I set the router to point to it. However, neither my spare computer nor my main PC can access the ddns on the NAS webserver with jumbo frames when the router points to it. This makes me believe there is something wrong with the ReadyNAS.
Related Content
- Mar 14, 2019Retired_Member
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!