Good evening! Sorry for bad english
I have a task to change MTU on MikroTik ether1 interface from default 1500 bytes to 1700(for large packets through EoIP tunnel), i tuned it in interface settings and changed it on local switch(dlink dgs3620-28sc), but when i try to ping neighbor interface with no fragmentation it doesn’t work. After testing i saw, that i can ping only with ping packet size 1534 and below. Jumbo frames on local switch is enable. Now there is firmware v6.42.6 (stable), but i tried to upgrade. Besides i have an 951Ui model too and all works fine. Can you prompt me what can i do with that?
Which interface is “neighbor interface”? The switch itself or some other adjacent machine? The problem with setting larger MTU is that all devices in same L2 (broadcast) domain have to match the increased MTU size. Different L2 domains are not a problem because router should be able to adapt/fragment packets entering L2 domain with smaller MTU size.
I dont think that it works that way, because i have an Ui version with same mtu on bridge and it works well. And i cant change MTU on bridge for some reason. L2 MTU 1598 and L3 MTU 1500. Will try to change that 951G model on something else for test.
Is there any setting on the DGS management interface regarding MTU? Specs say it supports jumbo frames up to 13kB in size, but that’s probably switch chip capability. Management interface might have some other settings.
Personally I’d try to leave out the DGS when testing if larger frames work … so try to ping the L3 peer of your host. As I wrote before, next-hop router of RB should be able to deal with desired MTU size so it should be able to reply to pings.
I have a chain Cisco 4900M - Dlink DGS3620-28SC - Mikrotik RB951G. And i can ping from Cisco to Dlink’s address(from RB subnet) with 1700 and df-bit, so i don’t think that it is Dlink problem. Is it possible that in that RB installed old chip that doesn’t support some functions? CPU Ar9344 v3.33
Upgrade device to latest ROS, restart then also upgrade the “Firmware” in System—>Routerboard—>Upgrade, then restart again.
Check in same place if “Current Firmware” is the same as ROS version upgraded to. The reason I am suggesting this is that there were a couple of big changes / improvements in version 3.41 IIRC and seems you are still on firmware v3.33