search

javitu / rt-n56u

Automatically exported from code.google.com/p/rt-n56u
0 stars 2 forks source link

Jumbo frames not working on AP mode #1359

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. ping -f -l 9000 192.168.0.5
* from machine connected directly on LAN port

What is the expected output? 
Reply from 192.168.0.5: bytes=1452 time<1ms TTL=64
What do you see instead?
Packet needs to be fragmented but DF set.

What version of the product are you using? On what operating system?
Firmware:   3.0.3.8-081

Please describe the problem as detailed as it's possible.

Basically, my RT-N56U is set as an AP and Jumbo frames dont seems to work at 
all. The result of two devices connected on the LAN ports cannot send frames 
larger the 1472 bytes. By looking a bit into it, I found that only the lo 
interface is set to a MTU of 16k bytes and all other are 1500 bytes (eth2, br0, 
etc).

Original issue reported on code.google.com by julioqc47 on 7 Nov 2014 at 11:20

GoogleCodeExporter commented 9 years ago 
Forgot to mention that of course, each PCs NIC is configured to accept jumbo 
frames of 9000bytes so I run my test by sending anything between 1500 and 9000 
bytes which all fail, whether IPv4 or IPv6

Original comment by julioqc47 on 7 Nov 2014 at 11:22

GoogleCodeExporter commented 9 years ago 
To to my issue, i've notice this line in the system log:

kernel: raeth: RX Ring 256, TX Ring 2*256. Max packet size 1536

Could it explain something?

Original comment by julioqc47 on 17 Jan 2015 at 3:20

GoogleCodeExporter commented 9 years ago 
Host always used max packet size 1536 bytes.

JF can accept only between switch LAN ports.

Original comment by andy.pad...@gmail.com on 12 Feb 2015 at 7:53